BSOD freezing and crashing under load

  1. Posts : 4
    Windows 10

    BSOD freezing and crashing under load

    My computer has always crashed frequently since I built it a few months ago. I finally did a clean Windows 10 install to see if that would sort it out but it didn't. It appears random. It crashes during resource intensive games, not resource intensive games, browsing, watching a video, or even just idling once every 2 to 6 hours of use. BSOD point their fingers at the RAM (which has tested fine), my graphics driver (the latest), and other things I'm not sure about. Please help, it's very annoying. I've been able to fix any problems my previous computers had by searching online, but this is over my head.
      My Computer

  2. axe0's Avatar
    Posts : 14,811
    Windows 10 Pro

    Hi wineheart,

    Welcome to the 10forums.

    Please check your Razer software for updates.
    Do you have any razer device connected? If you do, check Razer for driver updates
    ffffd000`86d155d8  fffff800`18ca0200Unable to load image \??\C:\Windows\system32\drivers\RzDxgk.sys, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for RzDxgk.sys
    3: kd> lmvm RzDxgk
    start             end                 module name
    fffff800`18ca0000 fffff800`18cbdb00   RzDxgk     (no symbols)           
        Loaded symbol image file: RzDxgk.sys
        Image path: \??\C:\Windows\system32\drivers\RzDxgk.sys
        Image name: RzDxgk.sys
        Timestamp:        Thu Apr 03 17:39:50 2014 (533D80C6)
        CheckSum:         0002AEC4
        ImageSize:        0001DB00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computers

  3. Posts : 4
    Windows 10
    Thread Starter

    My mouse driver is up to date.

    I have a few more crashes to add, all with unique BSOD reasons. I was either playing a game or switching between a game and firefox.
      My Computer

  4. axe0's Avatar
    Posts : 14,811
    Windows 10 Pro

    The 0x1A(MEMORY_MANAGEMENT) and 0x4E(PFN_LIST_CORRUPT) are related to memory issues
    The 0xA(IRQL_NOT_LESS_OR_EQUAL) is a read error what is usually caused by corrupted memory
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arg1: fffffd57cb000068, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800c4c6fa5a, address which referenced memory

    Diagnostic Test


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note

    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
      My Computers

  5. Posts : 4
    Windows 10
    Thread Starter

    I ran this all night and while I was at work today. 17 tests and no failures. =( This is frustrating.
      My Computer

  6. axe0's Avatar
    Posts : 14,811
    Windows 10 Pro

    Do you mean 17 passes or really 17 tests?
    Each pass has 10 tests where each test tests something different. But you need to run 8 or more passes to finish the test or until you get an error.
      My Computers

  7. Posts : 4
    Windows 10
    Thread Starter

    17 passes. It ran for 18-20 hours.
      My Computer

  8. axe0's Avatar
    Posts : 14,811
    Windows 10 Pro

    Diagnostic Test


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  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 07:13.
Find Us

Windows 10 Forums