Bsod while playing diablo 3

Page 2 of 2 FirstFirst 12

  1. Posts : 14
    windows 7 professional 64 bit
    Thread Starter
       #11

    ok, ran driver verifier for a few days no errors, thought my bsod problem was finally gone
    i turn it off and boom bsods start again lol

    mindumps are attached
    no kaspersky installed
    Microsoft security installed instead

    please help me

    also, i have a question
    i have an SSD, when i reinstalled windows i put the paged file on my HDD instead of the SSD because it writes to it too much, do you think this might be the culprit?
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #12

    Mate there is a problem, see it:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff80002fce7e0}
    
    Unable to load image Unknown_Module_00000000`000039e9, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`000039e9
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`000039e9
    Unknown module 'Unknown_Module_00000000_000039e9' found on stack, using vad to reload module.
    !vad_reload -1 0x39e9
    Failed to get old VAD root
    Unknown module 'Unknown_Module_00000000_000039e9' found on stack, using vad to reload module.
    !vad_reload -1 0x39e9
    Failed to get old VAD root
    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    A stop 0x7F may be caused out of a lot of reasons.
    Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack (source: Carrona.org)

    May I see your MSINFO32 file once again? The latest state?

    1. Click on the start button
    2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
    3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
    4. Give the time for processing, it will save a .nfo file on your desktop.
    5. Zip it, and upload it following the instruction.

    Also run Driver Verifier.
    Driver Verifier - Enable and Disable

    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  3. Posts : 14
    windows 7 professional 64 bit
    Thread Starter
       #13

    ok i uploaded the txt file it created

    how about the other minidumps?
    one of them was something about usb while the other said something about amd
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #14

    I checked the latest one only. As the latest one gives the information about the latest situation. Dont worry. Just enable driver verifier. Upload a few dumps with verifier on.

    Probably those will give it causes, including USB and AMD :)
      My Computer


  5. Posts : 14
    windows 7 professional 64 bit
    Thread Starter
       #15

    ok ran verifier for the whole day while i did stuff on comp and played d3
    crashed just now after 24 hours with verifier on
    it said dxgkrnl.sys

    dump attached
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #16

    Still it is unknown image.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {114f30, b, 0, fffff880052445ff}
    
    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    Now what we are to do at first is to burn test the CPU


    And a stress test of the RAM modules.


    Do the tests and let us know the results.
      My Computer


 
Page 2 of 2 FirstFirst 12

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

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