Several BSOD - Windows 10 Home x64

Page 2 of 2 FirstFirst 12

  1. Posts : 10
    Windows 10 Home 64bit
    Thread Starter
       #11

    I'm running driver verifier as pointed by the tutorial.
    No BSOD until now (~ 2 hours running)
    I'll keep you posted.
      My Computer


  2. Posts : 10
    Windows 10 Home 64bit
    Thread Starter
       #12

    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?
      My Computer


  3. Posts : 382
    Windows 10 Home
       #13

    Hello deggesim.

    The BSOD that occurred yesterday was a 0x109 and here are the most probable causes:

    Cause There are generally three different causes for this bug check:


    1. 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.
    2. 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.

    3. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
    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.

    Cheers, Boris :)
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #14

    @deggesim, could you upload a kernel dump / memory dump from %systemroot%, you'll need a 3rd party uploader to upload it and share the link. I want to verify something but I can't, probably due to limited data with minidumps.
      My Computers


  5. Posts : 10
    Windows 10 Home 64bit
    Thread Starter
       #15

    I uploaded memory dump on my Google Drive -> MEMORY.7z - Google Drive
      My Computer


  6. Posts : 14,901
    Windows 10 Pro
       #16

    Ok, I can verify it is the memory (although pretty clear with driver verifier)
      My Computers


  7. Posts : 10
    Windows 10 Home 64bit
    Thread Starter
       #17

    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.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:10.
Find Us




Windows 10 Forums