BSOD randon crashes.

Page 3 of 4 FirstFirst 1234 LastLast

  1. mcco
    Posts : 34
    Windows 7 64 bit
    Thread Starter
       New #21

    Hi Again

    Another crash today. Pc was running for around 8 hours and I got the following crash dump.


    Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Michael\Desktop\SF_07-09-2012\090712-23758-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`0ec51000 PsLoadedModuleList = 0xfffff800`0ee95670
    Debug session time: Fri Sep 7 18:50:31.341 2012 (UTC + 1:00)
    System Uptime: 0 days 7:59:33.294
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa80092a2028, be200000, 5110a}

    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : GenuineIntel

    Followup: MachineOwner
    ---------

    3: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80092a2028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: f

    STACK_TEXT:
    fffff880`033bca58 fffff800`0ec1aa3b : 00000000`00000124 00000000`00000000 fffffa80`092a2028 00000000`be200000 : nt!KeBugCheckEx
    fffff880`033bca60 fffff800`0edddb03 : 00000000`00000001 fffffa80`08fb0ea0 00000000`00000000 fffffa80`08fb0ef0 : hal!HalBugCheckSystem+0x1e3
    fffff880`033bcaa0 fffff800`0ec1a700 : 00000000`00000728 fffffa80`08fb0ea0 fffff880`033bce30 fffff880`033bce00 : nt!WheaReportHwError+0x263
    fffff880`033bcb00 fffff800`0ec1a052 : fffffa80`08fb0ea0 fffff880`033bce30 fffffa80`08fb0ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`033bcc50 fffff800`0ec19f0d : 00000000`00000004 00000000`00000001 fffff880`033bceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`033bcc90 fffff800`0ec0de88 : fffff880`033b4180 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`033bccc0 fffff800`0ecceaac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`033bccf0 fffff800`0ecce913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`033bce30 fffff800`0ecdb730 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`033dca80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeUpdateRunTime+0x50


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: GenuineIntel

    IMAGE_NAME: GenuineIntel

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

    BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

    Followup: MachineOwner
    ---------

    I have attached the info requested in a zip file

    The headset was not plugged in and the device was uninstalled in the device manager.

    Thanks again

    Michael
      My Computer
    Quote Quote

  3. FredeGail
    Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       New #22

    Hello again my friend, no problem we'll get it sorted.

    Code:
    WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
    Usual causes: Hardware, Incompatibility, May be driver corruption

    1) It's only a few bits of voltages we're talking about, but make sure that your cables are tight, the BIOS settings are default and most important -- nothing is overclocked. Small bits of voltages of the difference is not too serious when dealing with the CPU; but it might be a causer - especially when the Processor is rapidly blamed in the 'Probably Caused By'-line.

    2) Ensure that the case is cool inside, check your temperatures in BIOS or use Speccy for instance. Try to open your case ( Ensure warranty rules and regulations), and get a fan to blow directly into the hardware.

    3) Update every driver that interacts with the hardware. (Raid, Controllers, Graphics Card driver)

    4) Nevertheless it's important to keep Windows updated because 0x124 might not point to hardware.

    5) Report if these bugchecks appears at times, they're the most common one within Hardware issues and overclocking.
    0x77 – KERNEL_STACK_INPAGE_ERROR
    0x7A - KERNEL_DATA_INPAGE_ERROR
    0x101 - CLOCK_WATCHDOG_TIMEOUT

    * Are you using the stock cooler?

    Best Regards,
    Frederik.
      My Computer
    Quote Quote

  4. mcco
    Posts : 34
    Windows 7 64 bit
    Thread Starter
       New #23

    Hi Frederik

    I have changed the settings in my Bois to Default I'll see if this helps. I have been running with the side of the case open as I haven't got round to putting it back on after testing the ram! Lazy I know.

    My pc was bought as an overclocked packaged - Krypton Z68 600i Intel Core i5 2500K 3.30GHZ @ 4.60GHZ.

    Cooling is a stock fan which came with the pc

    I will will you know how I get on.

    Thanks as always

    Michael
      My Computer
    Quote Quote

  6. mcco
    Posts : 34
    Windows 7 64 bit
    Thread Starter
       New #24

    Hi Frederiek

    I checked my cooling system and it appears I might have installed in incorrectly

    I placed it horizontally instead of vertically. My fan faced down towards the graphics card, it now is parallel to the case fan so air can flow freely out the back of the PC. Its hard to explain, see the attached diagram

    I ran Intel burn and it said the system was stable. My normal running temps are 41-45C and when running FSX 70-75C. I have checked for my motherboard and these temps are well inside the limits.

    Fingers crossed the problem was heat. I will keep you updated

    Thanks again for your help

    Michael
      My Computer
    Quote Quote

  7. mcco
    Posts : 34
    Windows 7 64 bit
    Thread Starter
       New #25

    Well, it didn't make a difference, I experienced another crash



    Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Michael\Desktop\SF_08-09-2012\090812-23431-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`0ec0c000 PsLoadedModuleList = 0xfffff800`0ee50670
    Debug session time: Sat Sep 8 16:31:00.824 2012 (UTC + 1:00)
    System Uptime: 0 days 4:47:10.026
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa800928a028, be200000, 5110a}

    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : GenuineIntel

    Followup: MachineOwner
    ---------

    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800928a028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: f

    STACK_TEXT:
    fffff880`0314aa58 fffff800`0f206a3b : 00000000`00000124 00000000`00000000 fffffa80`0928a028 00000000`be200000 : nt!KeBugCheckEx
    fffff880`0314aa60 fffff800`0ed98b03 : 00000000`00000001 fffffa80`0906fea0 00000000`00000000 fffffa80`0906fef0 : hal!HalBugCheckSystem+0x1e3
    fffff880`0314aaa0 fffff800`0f206700 : 00000000`00000728 fffffa80`0906fea0 fffff880`0314ae30 fffff880`0314ae00 : nt!WheaReportHwError+0x263
    fffff880`0314ab00 fffff800`0f206052 : fffffa80`0906fea0 fffff880`0314ae30 fffffa80`0906fea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`0314ac50 fffff800`0f205f0d : 00000000`00000004 00000000`00000001 fffff880`0314aeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`0314ac90 fffff800`0f1f9e88 : 00000000`00000000 fffff880`03142180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`0314acc0 fffff800`0ec89aac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`0314acf0 fffff800`0ec89913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`0314ae30 fffff880`079dcc61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`0316ab58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: GenuineIntel

    IMAGE_NAME: GenuineIntel

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

    BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

    Followup: MachineOwner
    ---------
      My Computer
    Quote Quote

  8. FredeGail
    Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       New #26

    My pc was bought as an overclocked packaged - Krypton Z68 600i Intel Core i5 2500K 3.30GHZ @ 4.60GHZ.

    ¨¨¨¨¨¨¨¨¨¨

    This. This is the cause of your crash as far as I'm concerned. Your crash dumps are pointing over and over to your CPU, which is definitely overheated. Are you able to make it run on normal settings in any way? Maybe call the guys where you've bought your computer.

    Best Regards,
    Frederik.
      My Computer
    Quote Quote

  10. mcco
    Posts : 34
    Windows 7 64 bit
    Thread Starter
       New #27

    Hi Frederik

    Thanks for your help with this, I will contact overclockers.co.uk, the guys I got the pc off and see if they can suggest something.

    Michael
      My Computer
    Quote Quote

  11. FredeGail
    Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       New #28

    Excellent, they probably have more expertise within it. Also feel free to write a short thread in our Overclocking and Case Mods forum. By that, you'll secure a faster solution.
      My Computer
    Quote Quote

  12. mcco
    Posts : 34
    Windows 7 64 bit
    Thread Starter
       New #29

    Hi Frederik

    I posted on the overclockers customer support forum, no response yet (i did post on the weekend). I have tested my pc out and after running prime 95 at 4.6 & 4.5GHZ the pc crashed to the BSOD after 3-5 minutes with core temps of 90+. After checking the dump files it pointed to the cpu again.

    I have turned the pc down to 4.4GHZ, ran prime 95 for an hour resulting in temps of 70-80. The pc seems stable.

    Hopefully this will sort out my BSOD!

    Kind Regards

    Michael
      My Computer
    Quote Quote

  13. FredeGail
    Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       New #30

    Great news Michael, let's see how it turns out.

    Best Regards,
    Frederik.
      My Computer
    Quote Quote

 
Page 3 of 4 FirstFirst 1234 LastLast

  Related Discussions
BSOD and randon restarts
in BSOD Help and Support

Hi, I am trying to help a freind. Their PC randonly just restarts. I did see a blue screen once, but then PC restarted before I could take down any info! I have attached 2 mini dump file (zipped) and have a memory dump file that is too big to send when zipped. Any help or advice appreciated....
Computer is experiencing random, sudden crashes. Push the power button to reboot - nothing. If I manually unplug the power cord, replug in, the computer will reboot. Get the screen about the improper shut down, select last good start up and the computer loads as it is supposed to. Tried contacting...
Randon BSOD System_Service_Exception
in BSOD Help and Support

I am getting the BSOD S_S_E and I'm not sure why. From what I've read it seems to usually be a memory issue or a VGA driver. I have ran the Mem Diag with zero results and ensured that my video crad driver was up to date. I could not get perfmon / report to run. "The parameter is incorrect." is the...
BSOD Randon Crashes with DVDFab
in BSOD Help and Support

PC fault finding is pretty new to me so I need help detecting and fixing. Random crashes when using DVDFab. I've unistalled the two applications that were put on prior to these problems Sim City 4 and Nokia OVI suite. Still having issues. PC will crash while DVDFab is running, it flashes a...
Randon BSOD during booting
in BSOD Help and Support

Hello all, i am just getting random BSOD and i do not know what to do :-( I am using Window 7 64bit on my media center (Shuttle SG33G6) Please help!! Cheers, Kronoz
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 23:59.
Find Us