Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Frequent BSOD Crashes


04 Oct 2010   #1

Windows 7 Ultimate x64
 
 
Frequent BSOD Crashes

Hello, I would very much appreciate some assistance diagnosing the cause of frequent BSOD crashes that have been occurring on my Dell Studio XPS. They just started recently and I have not been able to nail down any commonalities regarding when the crashes occur. I have not installed any new hardware, everything is factory installed.

Here is some info. regarding my machine. All in-depth diagnostic tests were run and have been attached to this post. Please help me with whatever assistance you can provide. Thanks.

OS: Windows 7 Ultimate 64-bit
Full Retail version
System age: Approx 1.5 yrs.
OS installation age: Approx 1 yr.

My System SpecsSystem Spec
.

04 Oct 2010   #2

Windows 7 Professional x64
 
 

Are you doing any overclocking? If so, reset to defaults.

Do a CPU test with Prime95: http://www.sevenforums.com/tutorials...t-prime95.html

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Downloads\100210-18049-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0304d000 PsLoadedModuleList = 0xfffff800`0328ae50
Debug session time: Sat Oct  2 04:26:16.136 2010 (UTC - 4:00)
System Uptime: 0 days 1:12:30.213
Loading Kernel Symbols
...............................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88003113180, 6}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v;lmtsmn
*******************************************************************************
*                                                                             *
*                        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: fffff88003113180, 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:  
fffff880`095cd478 fffff800`0306b453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03113180 : nt!KeBugCheckEx
fffff880`095cd480 fffff800`030c5de7 : 00000000`00000000 fffff800`00000006 00000000`00002711 fffffa80`06512580 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`095cd510 fffff800`0300e895 : fffff800`03033460 fffff880`095cd6c0 fffff800`03033460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`095cd610 fffff800`030b9c33 : fffff800`03237e80 00000000`00000001 0000000e`80000019 00000000`00000008 : hal!HalpHpetClockInterrupt+0x8d
fffff880`095cd640 fffff800`0307c9ef : 00000000`00000046 fffff800`030b95ef fffff800`03237e80 fffff800`03245c40 : nt!KiInterruptDispatchNoLock+0x163
fffff880`095cd7d0 fffff800`033bb568 : 00000000`00000000 fffff880`095cdca0 fffff800`0304d000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x6b
fffff880`095cd840 fffff800`033bc1e5 : 00000000`05512580 fffff800`033b810e 00000000`00000000 fffff800`030bc993 : nt!ExpQuerySystemInformation+0x1368
fffff880`095cdbe0 fffff800`030bc993 : 00000000`00000000 fffff880`095cdc01 ffffffff`fffe7960 000007fe`00000001 : nt!NtQuerySystemInformation+0x4d
fffff880`095cdc20 00000000`76f8021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c6f248 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f8021a


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

start             end                 module name
fffff880`00f32000 fffff880`00f89000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`01009000 fffff880`01014000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`01000000 fffff880`01009000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e1a000 fffff880`00e44000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00cf0000 fffff880`00db0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c92000 fffff880`00cf0000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01525000 fffff880`01598000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01474000 fffff880`0148a000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e44000 fffff880`00e58000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00db0000 fffff880`00dfc000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`015a9000 fffff880`015b3000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0143a000 fffff880`01474000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`0168b000 fffff880`016d5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`03004000 fffff800`0304d000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`017f1000 fffff880`017fa000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00bba000 fffff800`00bc4000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`0150b000 fffff880`01525000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01660000 fffff880`0168b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00c3a000 fffff880`00c7e000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00e00000 fffff880`00e1a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f92000 fffff880`00f9c000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`014ad000 fffff880`0150b000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`017df000 fffff880`017f1000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`016e5000 fffff880`017d7000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01600000 fffff880`01660000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`0304d000 fffff800`03629000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01249000 fffff880`013ec000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00fdc000 fffff880`00ff1000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00fa9000 fffff880`00fdc000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`011e8000 fffff880`011ef000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`011ef000 fffff880`011ff000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01598000 fffff880`015a9000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c7e000 fffff880`00c92000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`00e58000 fffff880`00e63700   PxHlpa64 PxHlpa64.sys Wed Oct 17 14:25:02 2007 (4716537E)
fffff880`01400000 fffff880`0143a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01148000 fffff880`01177000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`017d7000 fffff880`017df000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01801000 fffff880`019fe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
3126b1b6`146b2e08 3126b1b6`35af3669   Unknown_Module_3126b1b6_146b2e08 Unknown_Module_3126b1b6`146b2e08 unavailable (00000000)
fffff880`00f9c000 fffff880`00fa9000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`016d5000 fffff880`016e5000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`01177000 fffff880`0118c000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0118c000 fffff880`011e8000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`015b3000 fffff880`015ff000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00e7f000 fffff880`00f23000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f23000 fffff880`00f32000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f89000 fffff880`00f92000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
My System SpecsSystem Spec
04 Oct 2010   #3
Microsoft MVP

 
 

Please note the following items from the stack text:
Code:
fffff880`095cdc20 00000000`76f8021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 
00000000`00c6f248 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f8021a
This looks to me to be a 3rd party driver issue (from the System Service thing). As such I'd suggest running Driver Verifier according to these instructions (normally I don't suggest Driver Verifier for a STOP 0x101 error - but the System Service thing says we might have a chance to get something helpful):
Quote:
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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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.
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:
Code:
Delete these registry keys (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
.


Reply

 Frequent BSOD Crashes




Thread Tools



Similar help and support threads for2: Frequent BSOD Crashes
Thread Forum
Solved Frequent BSOD crashes BSOD Help and Support
Frequent BSOD and crashes BSOD Help and Support
Frequent crashes and, now, BSOD BSOD Help and Support
Frequent BSOD Crashes BSOD Help and Support
BSOD Crashes more frequent than I like BSOD Help and Support
BSOD and frequent app crashes BSOD Help and Support
frequent crashes with BSOD can you help? BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 05:59 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33