New
#11
I'm running driver verifier as pointed by the tutorial.
No BSOD until now (~ 2 hours running)
I'll keep you posted.
I'm running driver verifier as pointed by the tutorial.
No BSOD until now (~ 2 hours running)
I'll keep you posted.
Driver verifier did not find any issue, no BSOD during the verify.
During yesterday afternoon though, I had another BSOD.
Attachment 69170
If I wanted to change memory I'd like to by 2x8GB of DDR3 1600 (they fit well with the CPU).
According to the memory table on ASRock site (ASRock > H77 Pro4/MVP), I found only two type of memory:
- DDR3 1600 8GB Kingston KHX16C9P1K2/16
- DDR3 1600 8GB Kingston KHX16C10B1K2/16X
If I search for those module I can't find anything, I found otherwise this Kingston model searching for KHX16C9P1K2 or KHX16C10B1K2 -> Kingston HyperX Fury Kit Memorie DDR-III da 16 GB, 2x8 GB, PC 1600, Nero: Amazon.it: Informatica
Do you think these memories will work properly?
Hello deggesim.
The BSOD that occurred yesterday was a 0x109 and here are the most probable causes:
And I would be very careful when buying RAM, I would try to find modules that match 100% to the ones on the ASRock page.Cause There are generally three different causes for this bug check:
- A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.
- A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.
- A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
Cheers, Boris :)
I uploaded memory dump on my Google Drive -> MEMORY.7z - Google Drive
Just a quick post to let you know that I found the issue. It was actually the RAM
I bought a kit of Corsair Vengeance (2x8GB) and had no more BSOD since then.