Frequent BSOD (ntoskrnl.exe), No Theme I can recognize

loreseek · 03 Nov 2012

Hello,

I've been suffering computer instability for a while now - it would freeze after slowing down and going into an audio loop. I was running two HD in Raid0 and they had issues, which I thought were the root cause so I replaced them, installed Windows 7 Ultimate 64bit, service pack 1. It seemed to have resolved the issue for a while, and then problems started again. My new HDs (old one aren't connected) showed errors and so I assumed it might be bad HDs, though unlikely. I got SSD HD and installed a fresh copy of Windows 7 Ultimate 64 bit, including all updates and Service Pack 1.
Recently I started getting quite frequent BSOD, which were rare before, with no discernible pattern - light gaming, watching a movie, idle. I'm clearly suspecting a hardware problem, but I'm fairly sure it's not the HD as having 3 different setups be faulty seems unlikely.

Actions taken:
1. Ran MemTest over night - no issues.
2. Ran Prime95 - no issues
3. Stressed GPU - no issues
4. Ran antivirus checks, CHKDSK, defrag.
5. Updated drivers and removed anything that I didn't need

I'm concerned that it might be my mobo or PSU and I hope to get a power tester next week. However, if there is any chance it's faulty software, that would save me a lot of time and energy.

Information about the computer:

PSU: CORSAIR CMPSU-650TX 650W ATX12V / EPS12V SLI Ready CrossFire Ready 80 PLUS Certified Active PFC Compatible with Core i7 Power Supply

Mobo: ASUS P6T LGA 1366 Intel X58 ATX Intel Motherboard

CPU: Intel Core i7 920 Nehalem 2.66GHz LGA 1366 130W Quad-Core Processor Model BX80601920

Mem: G.SKILL 6GB (3 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Triple Channel Kit Desktop Memory Model F3-12800CL9T-6GBNQ

DVD: SAMSUNG 22X DVDąR DVD Burner with LightScribe Black SATA Model SH-S223Q

GPU: SAPPHIRE 100259-1GL Radeon HD 4870 1GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready CrossFire Supported Video Card

HDs:

(OS) SAMSUNG 830 Series 2.5-Inch 128GB SATA III MLC Internal Solid State Drive (SSD) MZ-7PC128B/WW
(Storage) 2 Western Digital Caviar Black 500GB SATA Desktop Internal Hard Drive (RAID 0)
(old drives - not connected anymore) Seagate Barracuda 7200.11 ST3500320AS 500GB 7200 RPM SATA 3.0Gb/s Hard Drive

Keyboard: RAZER Arctosa Silver USB Wired Standard Gaming KeyboardRAZER
Mouse: DeathAdder RZ01-00150100-R3M1 Black 5 Buttons 1 x Wheel USB Optical High Precision Gaming Mouse

Mostly used for light gaming (most of my games are 1-2 years old, or much older than that) or watching movies / shows online.

Attaching file per instructions. Please let me know if something is missing.

I would appreciate any help - thank you very much.

Arc · 04 Nov 2012

Welcome aboard.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880009b2180, 4}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`084c4468 fffff800`02adcd5a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx
fffff880`084c4470 fffff800`02a8fad7 : 00000000`00000000 fffff800`00000004 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`084c4500 fffff800`02ff9895 : fffff800`0301f460 fffff880`084c46b0 fffff800`0301f460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`084c4600 fffff800`02a82513 : fffff800`02bf8e80 00000000`00000001 00000000`00000001 fffff800`02a07000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`084c4630 fffff800`02a5ad47 : fffffa80`054ba788 fffff800`02a81c27 fffff880`084c48a0 fffff800`02a81a01 : nt!KiInterruptDispatchNoLock+0x163
fffff880`084c47c0 fffff800`02d8b9cf : 00000000`00000000 fffff880`084c4ca0 00000000`00000000 00001f80`00390294 : nt!KeFlushProcessWriteBuffers+0x6b
fffff880`084c4830 fffff800`02d8c029 : 00000000`03729e40 fffff800`02d7807a 00000000`00000000 00000000`00000246 : nt!ExpQuerySystemInformation+0x13af
fffff880`084c4be0 fffff800`02a85253 : fffffa80`054b0000 fffffa80`07956001 ffffffff`fffe7960 000007fe`f104c000 : nt!NtQuerySystemInformation+0x4d
fffff880`084c4c20 00000000`7790167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02f5f668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7790167a


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
---------

Follow the guide STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg .... there must be a solution for you.

loreseek · 04 Nov 2012

Arc,

Thanks for posting that. I followed those steps and ran verifier. Unfortunately, it crashed several times without giving me any info. I then selectively chose some drivers and got a BSOD with dadder.sys, which is my mouse driver. I installed the new driver, hoping that would be it, but next time got a BSOD, so that's probably not it. I'll try running Verifier again and see what I get. I'm hoping that it's not a hardware problem, but my hdds are failing more repeatedly. I can fix them and then they are up and running, but I'm sure they aren't enjoying the frequent crashes.

Thanks for the help, I'll keep trying, but let me know if anything else crosses your mind.

Arc · 04 Nov 2012

Well done.

Just a suggestion ... you may go for a clean install with all new drivers, if that stops them crashes.