BSOD HELP!

I looked into how to read a dump file and this is what i got. This is for one of the dump files not all of them. I really have no clue what its saying. If i can get any help, i would truly truly appreciate it :smile:

Loading Dump File [C:\Documents and Settings\Admin\My Documents\Downloads\Minidump\Mini080312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`0361c000 PsLoadedModuleList = 0xfffff800`037e0dd0
Debug session time: Fri Aug 3 12:52:57.952 2012 (UTC - 6:00)
System Uptime: 0 days 19:00:57.825
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffffa60019d8180, 3}

*** WARNING: Unable to verify timestamp for hal.dll
Unable to load image \SystemRoot\system32\DRIVERS\i8042prt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for i8042prt.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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffffa60019d8180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffffa60`0a1fc6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopWriteDriverList+0xf1


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_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

MasterChaosX said:

Ok i downloaded the BIOS download from a differnet computer and strted it on my VISTA. and then my computer BSOD. I think everything is fine right now but what happens if my computer happens to BSOD in the middle of the BIOS update?

Click to expand...

Hi, as loda advised, running a BIOS update when you're in the middle of BSOD hardships is not recommended because if you happen to unfortunately BSOD during a BIOS update, you run the risk of bricking your BIOS, and then we'd be in even deeper water than we are now.

I checked the directions for the BIOS update, and it seems there are only directions for updating the BIOS through Windows itself, and not the BIOS... so we're going to cross out a BIOS update for now.

I've checked your dumps, all of which are 124 hardware bugchecks... but I'm having pshed!_WHEA_ERROR_RECORD_HEADER symbol errors, so I cannot get much info :banghead:

However, what I can see is that there's two different process crashes going on here, and it's happening too much to not be a coincidence, at least we can hope.

For example.. one dump, the process crash was - avgidsagent.exe

in the next - AAWService.exe (This is the main Ad-Aware service that runs in the background, and is considered the "central hub" of the program. It runs the Real-time Protection (RP) engine, as well as maintaining the Definitions, Whitelists and Blacklists.)

in the next - AAWService.exe

and then - avgidsagent.exe (AVG Identity Protection Service)

etc etc...

My theory is that both of these programs / services are clashing. I would for temporary troubleshooting purposes recommend the removal of both of these programs. At this point, it would help us know whether or not your issue is software of hardware (given we're dealing with 124 hardware bugchecks).

AVG remove tool.

Lavasoft remove tool.

Regards,

Patrick