BSOD - Rebooted from bugcheck 0x0000000a


  1. Posts : 4
    Windows 7 Ultimate 64 bit with SP1
       #1

    BSOD - Rebooted from bugcheck 0x0000000a


    My PC is a system I build a couple of months ago and is based on a ASUS P8P67 Deluxe motherboard running the Windows 7 Ultimate 64 bit operating system which has been updated to SP1.

    Currently my PC crashes with BSOD every other day and the event viewer shows:-

    Log Name: System
    Source: Microsoft-Windows-WER-SystemErrorReporting
    Date: 16/06/2011 09:57:53
    Event ID: 1001
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: STUDY
    Description:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x000009769eae965a, 0x0000000000000002, 0x0000000000000001, 0xfffff80003061782). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061611-13930-01.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-06-16T08:57:53.000000000Z" />
    <EventRecordID>19153</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>STUDY</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="param1">0x0000000a (0x000009769eae965a, 0x0000000000000002, 0x0000000000000001, 0xfffff80003061782)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">061611-13930-01</Data>
    </EventData>
    </Event>

    I have examined the dumps using WhoCrashed and got the following:-

    On Thu 16/06/2011 08:38:18 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\061611-13930-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
    Bugcheck code: 0xA (0x9769EAE965A, 0x2, 0x1, 0xFFFFF80003061782)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time

    I have run Windows Memory Diagnostic tool and it shows no problems.

    I attach the files created by your BSOD Dump & System File Collection app. As requested I also ran perfmon/report from the Start menu but it reported "Windows cannot find 'perfmon/report' Make sure you typed the name correctly, and then try again". Since you provided the name then are you sure it is correct?

    Can anyone please help me to resolve this issue?
    Last edited by Chevalier; 16 Jun 2011 at 06:09. Reason: additional information.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Chevalier said:
    My PC is a system I build a couple of months ago and is based on a ASUS P8P67 Deluxe motherboard running the Windows 7 Ultimate 64 bit operating system which has been updated to SP1.

    Currently my PC crashes with BSOD every other day and the event viewer shows:-

    Log Name: System
    Source: Microsoft-Windows-WER-SystemErrorReporting
    Date: 16/06/2011 09:57:53
    Event ID: 1001
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: STUDY
    Description:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x000009769eae965a, 0x0000000000000002, 0x0000000000000001, 0xfffff80003061782). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061611-13930-01.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-06-16T08:57:53.000000000Z" />
    <EventRecordID>19153</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>STUDY</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="param1">0x0000000a (0x000009769eae965a, 0x0000000000000002, 0x0000000000000001, 0xfffff80003061782)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">061611-13930-01</Data>
    </EventData>
    </Event>

    I have examined the dumps using WhoCrashed and got the following:-

    On Thu 16/06/2011 08:38:18 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\061611-13930-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
    Bugcheck code: 0xA (0x9769EAE965A, 0x2, 0x1, 0xFFFFF80003061782)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time

    I have run Windows Memory Diagnostic tool and it shows no problems.

    I attach the files created by your BSOD Dump & System File Collection app. As requested I also ran perfmon/report from the Start menu but it reported that it could not find the file.

    Can anyone please help me to resolve this issue?


    These was Related to aaHMSvc.exe from ASUSTeK Computer Inc.. I would update or remove to test.

    Also


    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

    They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

    Use this SPTD uninstaller DuplexSecure - Downloads

    when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.
      My Computer


  3. Posts : 4
    Windows 7 Ultimate 64 bit with SP1
    Thread Starter
       #3

    Many thanks for your prompt response. I shall try what you suggest and will report back later.
      My Computer


  4. Posts : 4
    Windows 7 Ultimate 64 bit with SP1
    Thread Starter
       #4

    I have removed the items suggested, rebooted the PC, cleaned the Registry and rebooted again. I then ran Prime95 to see how the PC responded to stress tests. Aftyer a short time the PC crashed and BSOD appeared. I allowed the crash dump to be created and then re-ran your BSOD Dump & System File Collection app. The results are attached.

    I hope that this latest information will help to identify what is causing these BSOD.

    Kind regards,

    Chevalier
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    Chevalier said:
    I have removed the items suggested, rebooted the PC, cleaned the Registry and rebooted again. I then ran Prime95 to see how the PC responded to stress tests. Aftyer a short time the PC crashed and BSOD appeared. I allowed the crash dump to be created and then re-ran your BSOD Dump & System File Collection app. The results are attached.

    I hope that this latest information will help to identify what is causing these BSOD.

    Kind regards,

    Chevalier
    Sptd.sys is still being loaded.

    sptd.sys 8/24/2010 2:13:12 AM fffff880`0103f000 fffff880`0119c000 0x0015d000 0x4c7362f8
      My Computer


  6. Posts : 4
    Windows 7 Ultimate 64 bit with SP1
    Thread Starter
       #6

    zigzag3143 said:
    Chevalier said:
    I have removed the items suggested, rebooted the PC, cleaned the Registry and rebooted again. I then ran Prime95 to see how the PC responded to stress tests. Aftyer a short time the PC crashed and BSOD appeared. I allowed the crash dump to be created and then re-ran your BSOD Dump & System File Collection app. The results are attached.

    I hope that this latest information will help to identify what is causing these BSOD.

    Kind regards,

    Chevalier
    Sptd.sys is still being loaded.

    sptd.sys 8/24/2010 2:13:12 AM fffff880`0103f000 fffff880`0119c000 0x0015d000 0x4c7362f8
    Sorry about that. I used Windows uninstal and clearly remnants still existed. I manually ran through regedit and I found and eliminated 3 instances of sptd.sys.

    After a reboot I ran Priome95 again and ........WOW no BSOD. You are a star!

    I shall watch for the next few days and hope this is not a false dawn.

    Many thanks.
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    Chevalier said:
    zigzag3143 said:
    Chevalier said:
    I have removed the items suggested, rebooted the PC, cleaned the Registry and rebooted again. I then ran Prime95 to see how the PC responded to stress tests. Aftyer a short time the PC crashed and BSOD appeared. I allowed the crash dump to be created and then re-ran your BSOD Dump & System File Collection app. The results are attached.

    I hope that this latest information will help to identify what is causing these BSOD.

    Kind regards,

    Chevalier
    Sptd.sys is still being loaded.

    sptd.sys 8/24/2010 2:13:12 AM fffff880`0103f000 fffff880`0119c000 0x0015d000 0x4c7362f8
    Sorry about that. I used Windows uninstal and clearly remnants still existed. I manually ran through regedit and I found and eliminated 3 instances of sptd.sys.

    After a reboot I ran Priome95 again and ........WOW no BSOD. You are a star!

    I shall watch for the next few days and hope this is not a false dawn.

    Many thanks.
    Fingers crossed. Good luck
      My Computer


 

  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 10:43.
Find Us