just got another one, I attached the .dmp file
sigh
also unfortauntely none of the drivers listed in the crash recorded a time stamp*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffff88003300180, 6}
Unable to load image ndis.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
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: fffff88003300180, 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
CURRENT_IRQL: d
STACK_TEXT:
fffff800`00ba21e8 fffff800`02c37443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03300180 : nt!KeBugCheckEx
fffff800`00ba21f0 fffff800`02c935f7 : fffffa80`00000000 fffff800`00000006 00000000`00026160 fffff880`05f645b5 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff800`00ba2280 fffff800`03200895 : fffff800`03225460 fffff800`00ba2430 fffff800`03225460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00ba2380 fffff800`02c873f3 : fffffa80`08628e70 fffffa80`0a11a020 fffffa80`09e6b980 0000057f`f595ba48 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00ba23b0 fffff800`02c4caa0 : 00000000`00000002 fffffa80`093e3168 00000000`00000000 fffffa80`093e3060 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00ba2540 fffff800`02c91a3f : fffff800`02e03e80 00000000`00000001 fffffa80`0a612168 fffffa80`0a6120e8 : nt!KxWaitForSpinLockAndAcquire+0x20
fffff800`00ba2570 fffff800`02c8673f : fffffa80`0a0ac1a0 00000000`00000002 fffffa80`0a648870 fffff880`0592a118 : nt!KeAcquireSpinLockAtDpcLevel+0x6f
fffff800`00ba25c0 fffff880`01964759 : fffffa80`0a60c7bc fffff880`059005e0 fffffa80`0a608030 00000000`00000000 : nt!KeSynchronizeExecution+0x2f
fffff800`00ba2600 fffffa80`0a60c7bc : fffff880`059005e0 fffffa80`0a608030 00000000`00000000 00000000`00000000 : ndis+0x8f759
fffff800`00ba2608 fffff880`059005e0 : fffffa80`0a608030 00000000`00000000 00000000`00000000 fffff880`059009e6 : 0xfffffa80`0a60c7bc
fffff800`00ba2610 fffffa80`0a608030 : 00000000`00000000 00000000`00000000 fffff880`059009e6 fffffa80`0a5d9040 : 0xfffff880`059005e0
fffff800`00ba2618 00000000`00000000 : 00000000`00000000 fffff880`059009e6 fffffa80`0a5d9040 fffff880`0587e30f : 0xfffffa80`0a608030
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
---------
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in \\\"verifier\\\" (without the quotes) and press Enter
- Select \\\"Create custom settings (for code developers)\\\" and click \\\"Next\\\"
- Select \\\"Select individual settings from a full list\\\" and click \\\"Next\\\"
- Select everything EXCEPT FOR \\\"Low Resource Simulation\\\" and click \\\"Next\\\"
- Select \\\"Select driver names from a list\\\" and click \\\"Next\\\"
Then select all drivers NOT provided by Microsoft and click \\\"Next\\\"
- Select \\\"Finish\\\" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting \\\"Delete existing settings\\\" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode (by pressing F8 repeatedly & select)
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
To disable Driver Verifier so that it no longer performs verification checks at startup, run Driver Verifier Manager again and select Delete Existing Settings in the initial dialog box.
Alternatively, click Start, then Run, and type verifier /reset in the Open box.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
I thought I had uninstalled avg..I ran the utility trouble suggested to completely remove it.
Ok, how safe/unsafe is this Driver Verifier?
well I tried it, restarted my computer, and it wouldnt boot. Turned it off then on again and tried to go into safe mode, but it came up with a startup recovery screen instead.
edit: I just tried it again and it booted this time. Now I guess I just wait for the crash. Would it be brought on by any specific software? I usually run windows live sync, but it just got updated, so I can't run the version I was running before. (it won't let you run an outdated version)
hopefully this one is more helpful
I have ms security essentials for anti virus. Yes driver verified should be running still. I figured I would leave it on in case that dmp didn't help. I can uninstall utorrent if u think it will help.
Home built system about 2 months old with Gigabyte GA-EP45T-UD3LR motherboard, intel q9550 cpu, Corsair XMS3 TW3X4G1333C9AG 4GB Dual Channel DDR3 RAM - - PC10666, 1333MHz, EVGA Geforce 7100gs 256mb ddr2 pcie, Western Digital SATA 250 drive, Win7 home premium 64 bit oem.
I get a BSOD at different times during startup. Sometimes before it makes it to windows, sometimes after I log in. The last 2 times was only the first startup of the day. It even happened once while logged in safe mode. I've reinstalled windows on 3 different drives, ran memtest86+ & windows mem diagnostic with no errors, removed and reinstalled memory, vid card & hard drive to ensure proper seating. The system & cpu only run about 39 degrees celcius.
I don't want to just start buying more parts ie. vid card or memory. I've attached a zipped folder containing .dmp files from the past 4 days since reinstalling windows.
I could really use some help.
well my computer has "shutdown unexpectantly" twice since the 18th, but no dmp files since then yet. sigh. no other options than just waiting and hoping it catches it?