locked
Windows 7 (64 Bit) crashes daily RRS feed

  • Question

  • I installed Windows 7 64bit a few months ago after my hard drive died with XP on it.  Unfortunately, it crashes on average once a day with BSOD or similar.  (I have had as many as 4 crashes in one day, and other weeks only 3 or 4 crashes in a week.)  I just uploaded my last 5 minidumps to my (newly created) SkyDrive.  Any chance somebody might take a look and see if you might see anything?  This is truly driving me crazy.

    Let's see, I had been running XP on this same hardware (exact same with the exception of the hard drive) with only 2 crashes under XP in the previous 3 years or so.  I have also run Linux on this same hardware without issue as well.

    Any help would be greatly appreciate!  Thanks in advance!

    (Look for Windows Live ID jheiden2 in the Crash Info folder)

    • Moved by Ronnie VernonMVP Sunday, January 23, 2011 5:56 AM Focus (From:Windows 7 Miscellaneous)
    Sunday, January 23, 2011 4:41 AM

Answers

  • You always get the same crash:

    Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

    This bug check indicates that a fatal hardware error has occurred.

    http://msdn.microsoft.com/en-us/library/ff557321%28VS.85%29.aspx


    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 1/19/2011 9:33:44
    Flags         : 0x00000000

    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8004c140b8
    Section       @ fffffa8004c14190
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal

    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 0
    CPU Version   : 0x0000000000010676
    Processor ID  : 0x0000000000000000

    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8004c14100
    Section       @ fffffa8004c14250
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal

    Local APIC Id : 0x0000000000000000
    CPU Id        : 76 06 01 00 00 08 02 00 - fd e3 08 00 ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

    Proc. Info 0  @ fffffa8004c14250

    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8004c14148
    Section       @ fffffa8004c142d0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal

    Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)

    cluberti wrote:

    That error (BUSL0_SRC_ERR_M_NOTIMEOUT_ERR) means the processor sent out a read request to L0 cache, and there was a delay in return (either a cache miss, or invalid data in cache).

    Is this CPU overclocked, or overheating? Does it pass stress testing without failing?

    Source:
    http://www.sevenforums.com/858818-post4.html

    Can you test your Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz with prime95? Also try a BIOS update, because yours is too old:

    BiosVersion = 0708  
    BiosReleaseDate = 12/19/2007
    SystemProductName = P5K-V
    BaseBoardManufacturer = ASUSTeK Computer INC.

    What's the temperature of your CPU?

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Nicholas Li Thursday, February 3, 2011 7:53 AM
    Sunday, January 23, 2011 8:52 PM
  • Hmmm, OK.  Were all of the minidumps the same?  I don't mind replacing this, just want to be sure I am replacing the right part(s) for the right reason.  I am considering getting a 2600.

    Oh yeah, I ran prime95 64-bit 3 times.  Crashes the system between 8-10 minutes after starting it up each time.

    yes, all dumps say the same. If the PC crashes after 10minutes of Prime95, the CPU is damaged.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Nicholas Li Thursday, February 3, 2011 7:53 AM
    Monday, January 24, 2011 2:32 PM

All replies

  • A bugcheck (BSOD) is a mechanism to protect your PC from damage.

    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here .

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Sunday, January 23, 2011 1:02 PM
  • You always get the same crash:

    Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

    This bug check indicates that a fatal hardware error has occurred.

    http://msdn.microsoft.com/en-us/library/ff557321%28VS.85%29.aspx


    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 1/19/2011 9:33:44
    Flags         : 0x00000000

    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8004c140b8
    Section       @ fffffa8004c14190
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal

    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 0
    CPU Version   : 0x0000000000010676
    Processor ID  : 0x0000000000000000

    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8004c14100
    Section       @ fffffa8004c14250
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal

    Local APIC Id : 0x0000000000000000
    CPU Id        : 76 06 01 00 00 08 02 00 - fd e3 08 00 ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

    Proc. Info 0  @ fffffa8004c14250

    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8004c14148
    Section       @ fffffa8004c142d0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal

    Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)

    cluberti wrote:

    That error (BUSL0_SRC_ERR_M_NOTIMEOUT_ERR) means the processor sent out a read request to L0 cache, and there was a delay in return (either a cache miss, or invalid data in cache).

    Is this CPU overclocked, or overheating? Does it pass stress testing without failing?

    Source:
    http://www.sevenforums.com/858818-post4.html

    Can you test your Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz with prime95? Also try a BIOS update, because yours is too old:

    BiosVersion = 0708  
    BiosReleaseDate = 12/19/2007
    SystemProductName = P5K-V
    BaseBoardManufacturer = ASUSTeK Computer INC.

    What's the temperature of your CPU?

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Nicholas Li Thursday, February 3, 2011 7:53 AM
    Sunday, January 23, 2011 8:52 PM
  • Hmmm, OK.  Were all of the minidumps the same?  I don't mind replacing this, just want to be sure I am replacing the right part(s) for the right reason.  I am considering getting a 2600.

    Let's see, cores are 35c to 41c.  It's only been overclocked once briefly to try it out.  As for BIOS update, I have only found one newer update and it's not that much newer.  Apparently ASUS stopped putting out BIOS for this board back in 2008.  Which particularly annoys me given that I bought the board in 2007 brand new.  I had no idea they were planning to stop supporting it so sooner after.

    Oh yeah, I ran prime95 64-bit 3 times.  Crashes the system between 8-10 minutes after starting it up each time.

    Anyway, thank you for looking at this.  I really do appreciate it.

    Sunday, January 23, 2011 11:46 PM
  • Hmmm, OK.  Were all of the minidumps the same?  I don't mind replacing this, just want to be sure I am replacing the right part(s) for the right reason.  I am considering getting a 2600.

    Oh yeah, I ran prime95 64-bit 3 times.  Crashes the system between 8-10 minutes after starting it up each time.

    yes, all dumps say the same. If the PC crashes after 10minutes of Prime95, the CPU is damaged.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Nicholas Li Thursday, February 3, 2011 7:53 AM
    Monday, January 24, 2011 2:32 PM
  • Hi Andre,

    Thank you very much.  I appreciate your help. 

     

    John

    Monday, January 24, 2011 4:21 PM