BSODs while gaming ?
BSODs while gaming ?
I think you're mistaken there. The dump shows us the clock speed of your RAM (this is the first dump)...
Rich (BB code):
[Memory Device (Type 17) - Length 92 - Handle 003dh]
Memory Error Info Handle [Not Provided]
Total Width 64 bits
Data Width 64 bits
Size 16384MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator DDR5-A2
Bank Locator BANK 0
Memory Type 22h - DDR5
Type Detail 0080h - Synchronous
Speed 5600MHz
Manufacturer Patriot Memory (PDP Systems)
Serial Number
Asset Tag Number
Part Number 5600 Series
Attributes 2
Extended Size 0
Configured Memory Speed 5600
Minimum Voltage 1000
Maximum Voltage 1100
Configured Voltage 1100
Memory Technology 3
Memory Operating Mode Capability 8
Firmware Version 0
Module Manufacturer Id 645
Module Product Id 0
Memory Subsystem Controller Manufacturer Id 0
Memory Subsystem Controller Product Id 0
Non-Volatile Size 0
Volatile Size 0
Cache Size 0
Logical Size 0
Extended Speed 0
Extended Configured Memory Speed 0
In the second dump it's now running at 4800MHz, so you must have disabled the XMP overclock to do that....
Code:
[Memory Device (Type 17) - Length 92 - Handle 003dh]
Memory Error Info Handle [Not Provided]
Total Width 64 bits
Data Width 64 bits
Size 16384MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator DDR5-A2
Bank Locator BANK 0
Memory Type 22h - DDR5
Type Detail 0080h - Synchronous
Speed 5600MHz
Manufacturer Patriot Memory (PDP Systems)
Serial Number
Asset Tag Number
Part Number 5600 Series
Attributes 2
Extended Size 0
Configured Memory Speed 4800
Minimum Voltage 1000
Maximum Voltage 1100
Configured Voltage 1100
Memory Technology 3
Memory Operating Mode Capability 8
Firmware Version 0
Module Manufacturer Id 645
Module Product Id 0
Memory Subsystem Controller Manufacturer Id 0
Memory Subsystem Controller Product Id 0
Non-Volatile Size 0
Volatile Size 0
Cache Size 0
Logical Size 0
Extended Speed 0
Extended Configured Memory Speed 0
Interestingly we have a different bugcheck code in this dump, it's an ATTEMPTED_WRITE_TO_READONLY_MEMORY, which means what it says. However, in this case it also looks like a RAM issue because it's a Microsoft lock bts instruction that fails...
Rich (BB code):
0: kd> .trap fffff08db48c7440;knL
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff960000000000 rbx=0000000000000000 rcx=ffff960160439400
rdx=ffff960000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803d8575a4a rsp=fffff08db48c75d0 rbp=fffff08db48c7839
r8=000000000756bdc0 r9=0000000000000000 r10=0000000000000009
r11=fffff803d9039878 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiAcquirePageListLock+0x14a:
fffff803`d8575a4a f0480fba69183f lock bts qword ptr [rcx+18h],3Fh ds:ffff9601`60439418=0000000000000000
Note the LOCK BTS instructions that fails, it's operating on a lockword (a serialisation method) with a Bit Test and Set instruction. This tests whether the lock is free (zero) and sets it if it is in one single instruction, the lockword (pointed to by the RCX register here - plus 18h bytes) must be in writeable storage since the BTS instruction will need to write to the lockword to set it.
Looking through the full call stack, which shows all the function calls leading up to the bugcheck, there are no third-party drivers called, only Microsoft functions are called. This means that the bugcheck was not caused by a driver messing up, because the Microsoft functions are all known to be good, but by the RAM holding the lockword being faulty.
You have two 16GB sticks so I'd suggest you leave the clock speed at 4800MHz (because the CPU is guaranteed to support that) and remove one stick - check the manual to ensure you leave the one stick in the correct slot. Run on one RAM stick for a day or several, or until you get a BSOD. Then swap sticks and run on the other stick for a few days, or until you get a BSOD.
BTW. I don't see your RAM part number in the dump, so I looked up
your motherboard QVL
for Patriot RAM and no 5600MHz Patriot RAM is listed, only 4800MHz and 6200MHz. That means that the RAM you have has not been tested and verified with this board, that's always a worry where potential RAM issues are involved.
Hello, confirming the first part of your message.
I did not disable XMP as it was already off, but I adjusted the system memory multiplier setting from AUTO to 4800 MHz.
Concerning the possible incompatibility issue... I'll wait next week to reach out to the technician who assembled my PC and inform them about this.
Appreciate the valuable feedback.
This driver is for MyPortIO_x64.sys. It was installed on June 22, 2015. The issue arose during memory compression by Microsoft, where old drivers could alter memory contents without realizing Windows was using a compression algorithm. This caused the program to write uncompressed data over compressed memory, leading to incorrect memory addresses and triggering a bugcheck. The suggestion was to uninstall the driver, enable virtual memory, and turn it back on. It may help to disable Windows memory compression if necessary.
This driver appears questionable:
It is old and not widely used, which raises concerns. You might want to enable verifier testing to detect memory corruption issues. If needed, download Microsoft Autoruns64.exe. Try disabling the driver and rebooting to see if the bugcheck still appears. (I would also disable virtual memory temporarily and restore it afterward to clear any related files.)
You can find more info here: https://learn.microsoft.com/en-us/sysint...s/autoruns
Thank you so much, next week I'll be home to try it. You have been a great hand
I would remove one RAM stick at a time, as it's the most dependable method for identifying RAM issues.
just fyi:
there appears to be an error message:
: kd> !error 0xc00002c4
Error code: (NTSTATUS) 0xc00002c4 (3221226180) - The system file %1 has become corrupt and has been replaced.