Need help with crashdmp debug!!

Bazerk83 said:

Hi guys, I'm a newbie when it comes to analysing and troubleshooting .dmps so I'd really appreciate some help with this.

My PC has been BSOD'ing quite a few times since I built it and installed Windows 7 but then it stopped for quite awhile and is back again.

I'm running a malware check now using SUPERantiSpyware PRO

The physical symptoms of the crash was a complete desktop freeze. Everything LOOOKED physically normal but completely unresponsive, even to mouse movement and keystrokes.

Below is the crashdmp details.


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

Loading Dump File [C:\Windows\Minidump\061810-27861-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x8320e000 PsLoadedModuleList = 0x83356810
Debug session time: Fri Jun 18 04:01:15.766 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:10.498
Loading Kernel Symbols
....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 8719f8fc, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8719f8fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------

BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
8cf97cc4 832dcfc5 8719f8e0 83375c28 83375c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8cf97ce4 832dddef 83375c20 8719f8e0 83375c50 nt!WheapProcessWorkQueueItem+0x56
8cf97d00 8327bf3b 83375c20 00000000 85a20020 nt!WheapWorkQueueWorkerRoutine+0x1f
8cf97d50 8341c6bb 00000001 aa623210 00000000 nt!ExpWorkerThread+0x10d
8cf97d90 832ce0f9 8327be2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------


Already I can see it seems to be pointing me towards a bad vista driver? Am I right or way off?

I'd really appreciate any help on the problem and/or solution.


Many thanks!

This is obviously a hardware problem. Use these to find out what it means and what to try. https://www.sevenforums.com/crash-loc...-what-try.html

Also we cant be sure unless we have the actual DMP file created when the computer crashed. use these to find it and upload it to us. https://www.sevenforums.com/crash-loc...d-problem.html

thanks

Ken

Thanks, that was really helpful! I'll zip up the dmp file right now

:)

I really hope my hardware isn't fried. I have 5 cooling fans (one of which is a huge one on the front of the case, and 2 directly over my graphics cards).

Bazerk83 said:

Thanks, that was really helpful! I'll zip up the dmp file right now

:)

I really hope my hardware isn't fried. I have 5 cooling fans (one of which is a huge one on the front of the case, and 2 directly over my graphics cards).

Probably not fried. You can test by downloading cpu-z and gpu-z (both free) to keep an eye on the temps.

Also may just be a case of something either being misconfigured or incompatible.

Have you added memory lately?

Are you overclocking?

Running a RAID?

etc

Ken

zigzag3143 said:

Bazerk83 said:

Thanks, that was really helpful! I'll zip up the dmp file right now

:)

I really hope my hardware isn't fried. I have 5 cooling fans (one of which is a huge one on the front of the case, and 2 directly over my graphics cards).

Probably not fried. You can test by downloading cpu-z and gpu-z (both free) to keep an eye on the temps.

Also may just be a case of something either being misconfigured or incompatible.

Have you added memory lately?

Are you overclocking?

Running a RAID?

etc

Ken

I'll do that. I was using SpeedFan and even when I'm idle i get temps of between 51-55 C which I know is not good. I set my fans to 100% at 40c and upwards but that doesn't seem to be having any affect.

I AM running 2 Nvidia GEforce GTX 260s (SLI) with fans directly over them and they came pre-overclocked.

I've not tweaked them at all and I've tried looking in bios to see if they are set at default overclocking (as in not overclocked).

Should I uninstall Rivatuner? I installed it but never actually set any overclock settings.

I haven't added anything new since I built it. I have 2 SATA HDDs and I THINK they're running RAID but I'll have to reboot and check.

are you seeing the attachment? I edited and attached it but I don't see it being shown on here.

:\

nevermind. done it.

bumped.

I'm bumping this because I'm hoping someone will help me out with the dmp.zip file I've attatched.


Many thanks.