Sudden BSOD (Win7 Ultimate x64). DUMP's attached.

[vitaliks777]

Hi all!

Here is the dmp file.

Any suggestions?

 

[vitaliks777]

CONFIGURATION:

OS W7 x64
CPU Intel i3 530
Motherboard Asrock P55DE3
Memory 4096 (2x2048) MB DDR III
Graphics Card 1028 MB nVidia GeForce GTS 250
Sound Card Realtek
Hard Drives Hitachi 320GB SATA

 

[Jonathan_King]

Not too much info in that dmp. It's either bad RAM or a device driver, but it doesn't say which one.

Try a memory test first. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

If it comes out clean, follow these instructions for enabling Driver Verifier. Upload the new dmps the result. http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

[/B]Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\050510-24687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c95e50
Debug session time: Wed May  5 07:15:35.107 2010 (GMT-4)
System Uptime: 0 days 0:06:52.388
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8001489e00, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001489e00
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002b3c26e to fffff80002ac9f00

STACK_TEXT:  
fffff880`069c4968 fffff800`02b3c26e : 00000000`0000001a 00000000`00041790 fffffa80`01489e00 00000000`0000ffff : nt!KeBugCheckEx
fffff880`069c4970 fffff800`02b0bc4a : 00000000`00000000 00000000`288effff fffffa80`00000000 fffffa80`0610d060 : nt! ?? ::FNODOBFM::`string'+0x339d6
fffff880`069c4b30 fffff800`02ac9153 : ffffffff`ffffffff 00000000`00ebf328 00000000`00ebf320 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`069c4c20 00000000`76ee009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00ebf2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ee009a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`02b3c26e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

Followup: MachineOwner

 

[vitaliks777]

Thanks, Jonathan_King!

I'll try it.

 

[jroggjr]

I'm also having issues with BSOD's in W7 U x64....the last 4 have been with CPU clock interrupts as shown in the memory dump below:


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


Loading Dump File [C:\Users\Joseph\Documents\My Received Files\050510-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03414000 PsLoadedModuleList = 0xfffff800`03651e50
Debug session time: Wed May 5 07:23:27.091 2010 (UTC - 4:00)
System Uptime: 0 days 0:27:46.215
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880009b1180, 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: fffff880009b1180, 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: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffff800`00b9bfb8 fffff800`03432443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b1180 : nt!KeBugCheckEx
fffff800`00b9bfc0 fffff800`0348ccf7 : 00000000`00000000 fffff800`00000004 00000000`000030d4 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff800`00b9c050 fffff800`039fa895 : fffff800`03a1f460 fffff800`00b9c200 fffff800`03a1f460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9c150 fffff800`03480af3 : fffff880`100ca352 fffffa80`06e14101 00000000`046c6b64 fffff800`00b9c200 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9c180 fffff800`03446173 : fffff800`035fee80 fffffa80`03cf4b60 fffff800`035fee80 00000000`00000004 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9c310 fffff800`0348d2a9 : 00000000`00000002 fffff800`03610000 fffff880`00000005 00000000`000000ff : nt!KxWaitForSpinLockAndAcquire+0x23
fffff800`00b9c340 fffff880`04612f3a : 00000000`00000001 fffff800`03629600 fffff800`00b9c430 fffffa80`06e131a0 : nt!KeAcquireSpinLockRaiseToDpc+0x89
fffff800`00b9c390 fffff880`046144a1 : fffffa80`06e131a0 fffffa80`06e04050 fffff800`00b9c430 fffffa80`06e041a0 : USBPORT!USBPORT_AcquireEpListLock+0x2e
fffff800`00b9c3c0 fffff880`0461c259 : fffffa80`06e041a0 fffffa80`06e041a0 00000000`00000003 fffffa80`06e131a0 : USBPORT!USBPORT_ProcessNeoStateChangeList+0x39
fffff800`00b9c430 fffff800`0346f493 : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`04e689f8 : USBPORT!USBPORT_DM_IoTimerDpc+0x29
fffff800`00b9c460 fffff800`034906a6 : 00000000`00000002 fffff800`00b9c6a8 00000000`00000000 00000000`00000000 : nt!IopTimerDispatch+0x132
fffff800`00b9c570 fffff800`0348fa26 : fffffa80`08e71e50 fffffa80`08e71e50 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0349057e : 00000003`dc3eca1e fffff800`00b9cc58 00000000`00019f29 fffff800`036017a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0348fd97 : 00000001`023faccb 00000001`00019f29 00000001`023faceb 00000000`00000029 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`0348cdfa : fffff800`035fee80 fffff800`0360cc40 00000000`00000000 fffff880`10114ea0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


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