locked
BSOD Help please RRS feed

  • Question

  • Can you helps with blue screen of death error please
    .

    050615-10904-01.dmp    06/05/2015 18:18:43    INTERNAL_POWER_ERROR    0x000000a0    00000000`00000009    ffffffff`c0000001    00000000`00000001    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+72a40    NT Kernel & System    Microsoft® Windows® Operating System    Microsoft Corporation    6.1.7601.18798 (win7sp1_gdr.150316-1654)    x64    ntoskrnl.exe+72a40                    C:\Windows\Minidump\050615-10904-01.dmp    8    15    7601    278,480    06/05/2015 19:40:07   

    • Edited by bwildrd Wednesday, May 6, 2015 7:37 PM
    Wednesday, May 6, 2015 7:36 PM

All replies

  •  
    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask


    Wanikiya and Dyami--Team Zigzag

    Wednesday, May 6, 2015 8:10 PM
  • Dump files are zipped in this location

    https://onedrive.live.com/?cid=D09EC63A6191B7AD&id=D09EC63A6191B7AD!103

    Thursday, May 7, 2015 11:11 AM
  • BW

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.

    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!!  If you do not know what this means you probably are not


    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)



    Wanikiya and Dyami--Team Zigzag

    Thursday, May 7, 2015 11:19 AM
  • Can't seem to get it to work. Ran Verifier. Seems to be running as I checked via the Command prompt and a load of info appeared but doesn't crash so no report file.

    Thursday, May 7, 2015 4:39 PM
  • BW

    It will not crash until the misbehaving driver is loaded.  May take up to 24 hours. 


    Wanikiya and Dyami--Team Zigzag

    Thursday, May 7, 2015 4:51 PM