BSOD Stop 0x101, Clock Interrupt not received in required interval |
![]() ![]() |
BSOD Stop 0x101, Clock Interrupt not received in required interval |
Oct 1 2008, 10:09 AM
Post
#1
|
|
|
New Member ![]() Posts: 2 OS: Vista Ultimate x64 |
Vista Ultimate x64 SP1 Problem: BSOD Stop 0x00000101 (0x00000060, ...) received anytime I run Witcher: Enhanced version 1.4, any settings, during "video" sequences (e.g. introduction) Also occurs on Crysis, but only rarely, with all settings at max. Never occurred with UT3. All other operations seem immune to problem. While I believe it is video related, I cannot isolate the problem. Any help on the "Bug Check" would be appreciated. System Specs: ASUS M2N4-SLI, BIOS 1204 Built in RealTek AC'97 (disabled) AMD Athlon 64 X2 6400+ Artic Cooler Geforce 9800GTX SB-XFi Extreme Audio Seagate 250GB SATA drive 8 GB RAM - Corsair PC6400 4 x 2GB Additional Info: No overclocking BIOS 1204 is beta, so also tried with 1002. AMD Dual Core optimizer running. Internal temps are normal. Memory Diagnostics: passed Video Driver: Nvidia Geforce 178.13 WHQL (Also rolled back and tried others.) Sound Driver: Up-to-date (Tried removing SB card and driver, reverting to RealTek AC'97, Tried disabling both and removing SB card) Reseated all cards. BSOD Info: MODULE_NAME: nt FAULTING_MODULE: fffff80001c49000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7 BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT CUSTOMER_CRASH_COUNT: 2 STACK_TEXT: fffff800`02f44aa8 fffff800`01ced311 : 00000000`00000101 00000000`00000060 00000000`00000000 fffffa60`005ec180 : nt!KeBugCheckEx fffff800`02f44ab0 fffff800`01c97eda : 00000000`00000000 fffff800`02f44bd0 fffff800`02f44c20 fffff800`01c303c0 : nt!wctomb+0x4c19 fffff800`02f44af0 fffff800`01c1340f : 00000000`00000000 fffff800`02f44bd0 fffff800`01c303c0 fffffa80`0933a1c0 : nt!KeUpdateSystemTime+0xea fffff800`02f44b20 fffff800`01c9fb2d : 00000000`00000000 fffff800`01c303c0 fffffa80`07cf5f00 fffff800`01c115cb : hal!HalSendNMI+0x65f fffff800`02f44b50 fffffa60`012eb062 : fffffa60`012ea0d9 fffffa80`00000001 fffff800`02f44d50 fffff800`01dbd680 : nt!KeSynchronizeExecution+0xc7d fffff800`02f44ce8 fffffa60`012ea0d9 : fffffa80`00000001 fffff800`02f44d50 fffff800`01dbd680 fffff800`01ca7a9f : amdk8+0x4062 fffff800`02f44cf0 fffff800`01cb97b8 : fffffa80`0b382bb0 fffff800`01dc2b80 fffff800`02f44db0 fffff800`01ca1a2d : amdk8+0x30d9 fffff800`02f44d20 fffff800`01ca8b31 : fffff800`01dbd680 00000000`0000509c 00000000`00000000 00000000`00000000 : nt!IoAcquireRemoveLockEx+0x3d8 fffff800`02f44d80 fffff800`01e765c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExEnterPriorityRegionAndAcquireResourceExclusive+0x141 fffff800`02f44db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlGetCompressionWorkSpaceSize+0x700 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntkrnlmp.exe This post has been edited by Mark H: Oct 1 2008, 11:02 AM |
|
|
Oct 1 2008, 03:09 PM
Post
#2
|
|
|
Trusted Tech Posts: 2,663 OS: Windows XP |
Possibly a faulty CPU
|
|
|
Oct 2 2008, 12:34 PM
Post
#3
|
|
|
New Member ![]() Posts: 2 OS: Vista Ultimate x64 |
Seems to be a problem between the SB600 and the CPU.
Swapped the motherboard (M2N4-SLI to M3N78 Pro) No more problem. (All other components as they were.) |
|
|
![]() ![]() |
Similar Topics
| Topic Title | Replies / Views | Topic Information | |||||
|---|---|---|---|---|---|---|---|
![]() |
0 / 213 | 18th August 2008 - 10:59 AM starjax started - last by starjax |
|||||
![]() |
0 / 341 | 18th August 2008 - 08:25 PM ITDAD started - last by ITDAD |
|||||
![]() |
25 / 914 | 1st November 2008 - 11:53 AM Aichi started - last by hfcg |
|||||
![]() |
2 / 97 | 28th November 2008 - 05:14 PM lucing1 started - last by emeraldnzl |
|||||
|
Time is now: 2nd December 2008 - 06:32 PM |
| Advertisements do not imply our endorsement of that product or service. The forum is run by volunteers who donate their time and expertise. We make every attempt to ensure that the help and advice posted is accurate and will not cause harm to your computer. However, we do not guarantee that they are accurate and they are to be used at your own risk. |