First BSOD, 3 minutes after system came back from hibernation.

Page 1 of 2 12 LastLast

  1. Posts : 22
    Windows 7 64 bit Ultimate
       #1

    First BSOD, 3 minutes after system came back from hibernation.


    Hello, Today i turnes on my pc this morning from hibernaton, i wrote down my password, and then i clicked on Google Chrome, i moved my mouse to the bar and when i was about to write the screen froze, and i receieved a BSOD, turned it on again and WhoCrashed said...


    On Wed 07/09/2011 02:52:55 p.m. GMT your computer crashed
    crash dump file: C:\Windows\Minidump\090711-29312-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF88003115180, 0x6)
    Error: CLOCK_WATCHDOG_TIMEOUT
    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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 07/09/2011 02:52:55 p.m. GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: hal.dll (hal!HalSendNMI+0xBD0)
    Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF88003115180, 0x6)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


    Id like to know why did this happen, a few days ago i installed a new case to my pc, my temps while playing on the CPu are max 71 C , for the videocard around 60s, and the nrothbridge has always benn around 70s max max 80, (im buying an Antec Spot Cool for it), when it ocured i was running HW info, Catalyst steam origin Razer drivers logitech drivers ESET nod 32 anti virus X padder and logitech Gaming software should hae been running but it crashes after every hibernation process (just clicking on the icon agian re opens it and its fixed)


    Thanks for your help in advance guys!

    EDIT: System Specs, Windows 7 Ultimate 64 bit
    HD 5850 and HD 5870 CF
    Intel Core i7 920 (STOCK)
    6 gb Ram
    Corsair TX850W
    Msi PRO E X58 Motherboard
    2 500 GB HD
    Thermaltake Element G Case

    ill attach the BSOD info as soon as it finnishes the process.

    id really like to know if its a hardware or driver issue (hope its driver related)

    I am not able to upload the html for some reason.

    Thanks again guys ill wait for your answers :)

    Please note that i ran prime 95 for 2 minutes when the temps hitted 80 C i got scared but it didnt crash in 2 minutes :)
    Last edited by Dan011093; 07 Sep 2011 at 11:18.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    According to your dump file the issue is with your Processor. This occurs when the processor is nonresponsive or is deadlocked.

    Possible Solutions :

    a) BIOS bug
    b) a driver whose activity is causing the target processor to lock up
    c) a hardware defect/bad CPU (temperature, voltage, dust)
    For more info https://www.sevenforums.com/crash-loc...tml#post567135

    Win 7 A Clock Interrupt... BSOD (101 Error)

       Warning
    Ensure Proper Cooling

    Run Prime 95[Again] to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff88003115180, The PRCB address of the hung processor.
    Arg4: 0000000000000006, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  d
    
    STACK_TEXT:  
    fffff880`0a3a3468 fffff800`02ce88c9 : 00000000`00000101 00000000`00000018 00000000`00000000 fffff880`03115180 : nt!KeBugCheckEx
    fffff880`0a3a3470 fffff800`02c9b497 : fffff880`00000000 fffff800`00000006 00000000`00002626 fffff880`01103a10 : nt! ?? ::FNODOBFM::`string'+0x4e2e
    fffff880`0a3a3500 fffff800`032111c0 : 00000000`00000000 fffff880`0a3a36b0 fffff800`0322d460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
    fffff880`0a3a3600 fffff800`02c8d173 : fffff800`02e06e80 fffff800`0322d460 00000000`00000001 fffff800`02c14000 : hal!HalpRtcClockInterrupt+0x130
    fffff880`0a3a3630 fffff800`02c66661 : 00000000`00000000 00000000`00000000 fffff800`02c9b845 fffff800`02e06e80 : nt!KiInterruptDispatchNoLock+0x163
    fffff880`0a3a37c0 fffff800`02f9adef : 00000000`00000000 fffff880`0a3a3ca0 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65
    fffff880`0a3a3830 fffff800`02f9b449 : 00000000`00425da0 fffff800`02f874de 00000000`00000000 fffff800`02c8fda1 : nt!ExpQuerySystemInformation+0x13af
    fffff880`0a3a3be0 fffff800`02c8fed3 : 00000000`00000000 fffff880`0a3a3ca0 ffffffff`fffe828e 000007fe`fc870b90 : nt!NtQuerySystemInformation+0x4d
    fffff880`0a3a3c20 00000000`77ce167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00fcf258 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ce167a
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 22
    Windows 7 64 bit Ultimate
    Thread Starter
       #3

    as i said before i cant run prime 95 so long because i dont want to put my processor onto those temps, when the error occured the processor was on fresh temps, the pc was idling, i dont really know what to do now, ive been reading and they say that the error is likely to be a hardware error, but i remember i had this error before when i ran everest (6 months agho) and it only occured when i ran everest, now if i run aida i dont get this issue, anyway this is my forst bsod in months, what could i do to know if its driver related?
    Thanks
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    Dan011093 said:
    as i said before i cant run prime 95 so long because i dont want to put my processor onto those temps, when the error occured the processor was on fresh temps, the pc was idling, i dont really know what to do now, ive been reading and they say that the error is likely to be a hardware error, but i remember i had this error before when i ran everest (6 months agho) and it only occured when i ran everest, now if i run aida i dont get this issue, anyway this is my forst bsod in months, what could i do to know if its driver related?
    Thanks
    Thats the problem here, your PC is inadequately cooled, you should get a better cooling solution
      My Computer


  5. Posts : 22
    Windows 7 64 bit Ultimate
    Thread Starter
       #5

    I Will try to get a better cooling solution this days, right now when gaming it doesnt go voer 70 C so its ok i guess, but what worried me is that it crashed on idle state (low 40c temps) is there any posibilitie it was a driver related issue or something like that? if the error isnt reproduced in days, should i still worry? what are suggestions on this issue? thanks!
      My Computer


  6. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #6

    Dan011093 said:
    I Will try to get a better cooling solution this days, right now when gaming it doesnt go voer 70 C so its ok i guess, but what worried me is that it crashed on idle state (low 40c temps) is there any posibilitie it was a driver related issue or something like that? if the error isnt reproduced in days, should i still worry? what are suggestions on this issue? thanks!
    This is a hardware/Bios error unrelated to software
      My Computer


  7. Posts : 22
    Windows 7 64 bit Ultimate
    Thread Starter
       #7

    But i used to get this error when running everest so maybe it can be caused by a software ike that?
      My Computer


  8. Posts : 22
    Windows 7 64 bit Ultimate
    Thread Starter
       #8

    I ran Crysis 2 benchmark for like an hour and nothing happened so what are the odds that im experiencing a bad cpu? or do you guys think it could have been caused by a driver or some software [problem?
      My Computer


  9. Posts : 845
    Windows 7 - Vista
       #9

    Hi -

    Bugcheck 0x101 BSOD = CPU hang and is usually caused by hardware failure.

    A few things I noticed on the software end. . . no harm in seeing if they may have involvement.

    You have an outdated version of ESET installed -
    Code:
    eamonm.sys      Wed Jul 14 04:13:43 2010 (4C3D71B7)
    epfw.sys        Wed Jul 14 04:10:34 2010 (4C3D70FA)
    Epfwndis.sys    Wed Jul 14 04:10:31 2010 (4C3D70F7)
    Remove ESET w/ removal Tool - http://kb.eset.com/esetkb/index?page=content&id=SOLN146

    Reboot upon completion. If you have current ESET key, install NOD32 v4.2.71.2 only - http://go.eset.com/us/download

    If no current ESET keycode, install MSE - http://www.microsoft.com/en-us/secur...s/default.aspx


    What does WinRing do for you? Driver = 3 years old and was written before Windows 7 RTM -
    Code:
    WinRing0x64.sys Sat Jul 26 09:29:37 2008 (488B26C1)
    http://www.sysnative.com/0x1/DriverReference.html#WinRing0x64.sys


    See if Driver Verifier flags any 3rd party drivers - http://sysnative.com/0x1/driver_verifier.htm


    Run Speccy - it will show you temps & info may provide a clue -
    - http://www.filehippo.com/download_speccy
    - "File" | "Publish Snapshot" | Paste URL into your next post


    Hardware failure for 0x101 CPU hang is the norm. Try the above - nothing to lose except a little time. I would advise that you reinstall Windows 7 and see if 0x101 returns before replacing any hardware.

    Windbg Logs
    --> http://sysnative.com/bsod2011/jcgrif..._jcgriff2_.html


    Regards. . .

    jcgriff2


    `


    BSOD SUMMARY
    Code:
    
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\090711-29312-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Wed Sep  7 10:52:55.601 2011 (GMT-4)
    System Uptime: 1 days 9:48:39.797
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    Bugcheck code 00000101
    Arguments 00000000`00000018 00000000`00000000 fffff880`03115180 00000000`00000006
    BiosVersion = V8.5
    BiosReleaseDate = 07/22/2009
    SystemManufacturer = MSI
    SystemProductName = MS-7522
    MaxSpeed:     2670
    CurrentSpeed: 2673
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
      My Computer


  10. Posts : 22
    Windows 7 64 bit Ultimate
    Thread Starter
       #10

    Hello jcGriff thanks for your reply, i dont knwo what does wingRing do to me,, the temps on my pc are normal on idling and gmaing they only go high at prime 95, i will do what you said, but.. how do i diagnose a hardware failure? yesterday i ran soem benchmarks and then gamed for some hours with no errors, please note that the error happened on idling so it wasnt temperature caused, or at least thats what i guess.

    Thanks

    Snapshot =D
    http://speccy.piriform.com/results/A...GuyooEARtE4PsI

    Its been 24 hours from the crash and i havent received any BSODS, only 1 (yesterday) First bsod i receive from this fresh windows install i made 4 months ago. Is there any way to test my cpu to see if theres a HW issue?
    Last edited by Dan011093; 08 Sep 2011 at 11:42.
      My Computer


 
Page 1 of 2 12 LastLast

  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 12:21.
Find Us