Vista64 BSOD

[cactusjack]

Hello all,

I was hoping someone could help me or offer further advice in relation to my problem.


Some history:

My Dell PC (Studio XPS Desktop 435MT, Vista 64) was purchased in December last year. It has been working well for the most part.

But then 3 weeks ago, when checking Event Viewer, I found a critical error relating to the hard drive. After running chk disk and Dell's diagnostics, the error was confirmed. Dell replaced the hard drive within 2 days - excellent service. The Dell technician reloaded Vista for me and reinstalled my drivers from the Dell CD - he used a recent set of ATI drivers (from the ATI website) for my Graphics card. I then went through the annoyance of reinstalling my software and reloading my data - thinking that was the end of my problems. For 3 weeks, all has been well - the PC feels like it has a spring in its step. Happy days....


BSOD:

Last night, a blue screen of death came up - I was shocked to say the least! I haven't seen a BSOD for years - going back to Windows 98 days. There was lots of text on the screen and I scrambled to find my camera to take a snapshot - couldn't do it in time. The PC restarted - and took longer than usual to restart.

The BSOD happened when I had a couple of internet browsers open and World of Warcaft open (nothing out of the ordinary - and this has always been fine).

Upon restarting the PC, the following info was presented:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 101
BCP1: 0000000000000019
BCP2: 0000000000000000
BCP3: FFFFFA6001927180
BCP4: 0000000000000006
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini111109-01.dmp
C:\Users\1\AppData\Local\Temp\WER-40170-0.sysdata.xml
C:\Users\1\AppData\Local\Temp\WER3B7.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409


Analysing the dump file:

I looked at the dump file and tried to make sense of it - I downloaded the Windows debugging software and the symbols file - although on my first attempt, it said there was an issue with loading incorrect symbols (not sure why since I installed the symbols to C:\windows\symbols and pointed to that path...). I used a different symbols path and this produced the analysis that is shown below.

I notice something about a hung processor, and something about inconclusive analysis - so I wonder if the dump file was analysed properly.

I would be grateful if someone could tell me what this BSOD means - can I relate it to a specific piece of hardware or a specific driver?


Action taken after the BSOD

After the BSOD, over a few hours, I ran Dell's diagnostics (which appear quite thorough). It came up with no errors - suggesting that the hard drive, RAM and processor are ok perhaps.


Further background info

I installed all of my software and drivers 3 weeks ago when Dell fitted the new hard drive. Since then I have not really done anything new to the machine. I don't use file sharing on this PC, or visit 'dodgy' websites - it is my work machine so I try and keep it as clean as can be :-)

All I use it for is: work (using MS office, e-mail, etc) and leisure (listening to music from itunes and playing World of Warcrft).

When I get home tonight I will be running the PC again to see if a BSOD reappears - but I just wanted to get any initial thoughts from the community on what could have caused the BSOD - I am in a slight panic, since it is my work machine...

My computer spec is:

Intel i7 920 2.66GHz processor, 6GB RAM 1067MHz DDR3 Tri Channel , ATI 512MB 4850 card, 640GB hard drive (western Digital), 6X Blu-Ray Burner Drive (BluRay, DVD & CD read and write) and 16X DVD ROM Drive, Integrated HDA 7.1, Vista 64bit.


Any advice is gratefully received, thank you.




_______________________________________________________

Mini Kernel Dump File: Only registers and stack trace are available

Invalid directory table base value 0x0
Mini Kernel Dump does not have process information
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/s...indows\Symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Machine Name:
Kernel base = 0xfffff800`03211000 PsLoadedModuleList = 0xfffff800`033d5dd0
Debug session time: Wed Nov 11 21:17:04.998 2009 (GMT+0)
System Uptime: 0 days 12:14:24.807
Loading Kernel Symbols
.....................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

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: fffffa6001927180, 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:
fffffa60`071a55c8 fffff800`03227370 : 00000000`00000101 00000000`00000019 00000000`00000000 fffffa60`01927180 : nt!KeBugCheckEx
fffffa60`071a55d0 fffff800`03264d4a : fffff800`037563c0 fffffa60`071a56f0 fffffa60`071a5740 fffff800`037563c0 : nt! ?? ::FNODOBFM::`string'+0x2de4
fffffa60`071a5610 fffff800`03733f04 : 00000000`00000000 00000093`04234c6c 00000000`00000000 00000093`04238462 : nt!KeUpdateSystemTime+0xea
fffffa60`071a5640 fffff800`0326450d : 00000000`23ae9a3e 00000000`00000001 fffffa80`0940e020 fffffa60`00000000 : hal!HalpHpetClockInterrupt+0x8c
fffffa60`071a5670 fffff800`0329d7d1 : 00000000`00000000 fffff800`03228d67 fffffa80`0b0be610 00000000`000fee00 : nt!KiInterruptDispatchNoLock+0x14d
fffffa60`071a5800 fffff800`03293574 : 00000000`00000000 00000000`fee00300 fffff800`033c1460 00000000`00000000 : nt!KxFlushEntireTb+0xbd
fffffa60`071a5830 fffff800`032279b6 : 00000000`00000000 00000000`00000000 00000000`fee00300 00000000`00000001 : nt!KeFlushTb+0x30
fffffa60`071a5860 fffffa60`063e1baa : 00000000`00000808 00000000`00000100 fffff800`00000000 fffffa80`00000300 : nt!MmMapIoSpace+0x12e
fffffa60`071a5920 00000000`00000808 : 00000000`00000100 fffff800`00000000 fffffa80`00000300 fffffa60`071a5d00 : 0xfffffa60`063e1baa
fffffa60`071a5928 00000000`00000100 : fffff800`00000000 fffffa80`00000300 fffffa60`071a5d00 fffff800`0326e0fd : 0x808
fffffa60`071a5930 fffff800`00000000 : fffffa80`00000300 fffffa60`071a5d00 fffff800`0326e0fd fffff800`03384680 : 0x100
fffffa60`071a5938 fffffa80`00000300 : fffffa60`071a5d00 fffff800`0326e0fd fffff800`03384680 fffff880`00000001 : 0xfffff800`00000000
fffffa60`071a5940 fffffa60`071a5d00 : fffff800`0326e0fd fffff800`03384680 fffff880`00000001 00000093`0178bc31 : 0xfffffa80`00000300
fffffa60`071a5948 fffff800`0326e0fd : fffff800`03384680 fffff880`00000001 00000093`0178bc31 fffffa60`071a5980 : 0xfffffa60`071a5d00
fffffa60`071a5950 00000000`00000008 : 00000000`00000001 00000000`20206f49 fffffa80`05dfce50 00000000`00000000 : nt!SwapContext+0x1ad
fffffa60`071a5990 00000000`00000001 : 00000000`20206f49 fffffa80`05dfce50 00000000`00000000 fffffa80`05c1ec10 : 0x8
fffffa60`071a5998 00000000`20206f49 : fffffa80`05dfce50 00000000`00000000 fffffa80`05c1ec10 fffff800`032815fb : 0x1
fffffa60`071a59a0 fffffa80`05dfce50 : 00000000`00000000 fffffa80`05c1ec10 fffff800`032815fb 00000000`00683d3a : 0x20206f49
fffffa60`071a59a8 00000000`00000000 : fffffa80`05c1ec10 fffff800`032815fb 00000000`00683d3a 00000000`00000000 : 0xfffffa80`05dfce50


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

[shbris]

dude i think we need more info

[cactusjack]

Sorry I went a bit over board :-)

[Syllopsium]

driver error. The event log may have more information if youre lucky. Id probably try the graphics driver first.

[cactusjack]

That is a relief!! thanks Syllopsium - at least I can potentially rule out hardware failure :-)

I have made a decision to upgrade to windows 7 tonight - I wonder if I am opening myself up to a huge load of problems......

[shbris]

nah mate drivers on windows 7 are faultless, other than realtek lan driver (AVOID AT ALL COSTS)

[cactusjack]

I have read somewhere that people install windows 7, go with whatever driver windows wants or has (and dont bother installing their own drivers) - is that wise?

Drivers scare me.

[shbris]

i've been using the RC and beta version now since first public beta and it's been great for drivers compared to vista, so i along with alot of other people would thoroughly recommend

[cactusjack]

I bought it for £30 (as I am a university student) - just installed it - so far so good. It seems to have picked up chipset, wireless and network card drivers - so havent installed those.

I did install graphics card and audio drivers - and so far its ok.

I am installing all of my programs now - so hopefully things continue to go well :-)