locked
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000080, 0x0000000000000002, 0x0000000000000001, 0xfffff80002cebc3f). RRS feed

  • Question

  • I just reinstalled my laptop after experiencing severe data corruption. There seems to be no problem with the hardware, I run RAM tests, disk tests, burning in tests, etc.

    Everything worked fine for a few days after the reinstall, but this morning I found it rebooted with this error in the event log:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000080, 0x0000000000000002, 0x0000000000000001, 0xfffff80002cebc3f).

    Since I suspect the corruption that forced me to reinstall was caused by this kind of reboots, I want to get rid of them, if possible. I've seen in other reboot/bugcheck threads that a copy of the memory dump helps investigate, so here it is:

    https://skydrive.live.com/?cid=d652e988db742907&sc=documents&uc=1&id=D652E988DB742907%21109#

    Thursday, June 23, 2011 5:49 AM

Answers

  • Hi,

     

    To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Having said that, I'd still like to share the following information with you:

     

    This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

     

    The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

     

    You could refer to the following article:

     

    Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

    http://msdn.microsoft.com/en-us/library/ff560129(v=vs.85).aspx

     

    Alex Zhao


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Bigteddy Monday, June 27, 2011 5:25 AM
    • Marked as answer by Cloud_TS Thursday, June 30, 2011 9:46 AM
    Monday, June 27, 2011 5:08 AM

All replies

  • Hi Vladimir,

    I have analysed your crash dump, but it does not reveal anything.  I think you need to submit a full dump. 

    To do this, go into the Advance System Settings of you Computer Properties, and select the Advanced tab.  Under "Startup and recovery settings" make sure that "Write debugging information" is set to "Kernel Memory dump"

    Obvoiously, this full dump will only be created if your computer crashes again.

    Thursday, June 23, 2011 8:06 AM
  • It seems that the option was already set to "Kernel Memory Dump".

    Thursday, June 23, 2011 6:00 PM
  • Any progress on your problem, Vladimir?
    Sunday, June 26, 2011 10:20 AM
  • Hi,

     

    To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Having said that, I'd still like to share the following information with you:

     

    This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

     

    The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

     

    You could refer to the following article:

     

    Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

    http://msdn.microsoft.com/en-us/library/ff560129(v=vs.85).aspx

     

    Alex Zhao


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Bigteddy Monday, June 27, 2011 5:25 AM
    • Marked as answer by Cloud_TS Thursday, June 30, 2011 9:46 AM
    Monday, June 27, 2011 5:08 AM