OS and Software > Microsoft Help > [WIN7] BSOD and the Minidump... how to analyze it?

[WIN7] BSOD and the Minidump... how to analyze it?

You can zip up the minidump and post it here. There are a couple of people who can analyze it, one of them being the Mod, auggy .

If you post it, I can take a look at it too. I have experience with debug dumps too.

Thanx guys... I'll zip it up now...
--
Mike C

reply to trparky

Minidump.zip 45,718 bytes minidump attached

reply to trparky
would you prefer I post it in it's native format? or is it being zipped up alright?
--
Mike C

I wasn't even ON the computer, in fact, I was on THIS computer selecting my avatar when the machine in question just had another BSOD... the only program open at the time was Avid Studio 16
--
Mike C

There are no indications of a specific driver that is causing the problem.

113012-32744-01.dmp referrers to a process name of "BGRnd.exe" but that's not a driver, it's a program's EXE file, specifically Avid Studio.

Then there's 113012-33493-01.dmp that referres to another program's EXE file called "NGStudio.exe" which again is associated with Avid Studio.

At this point, since Avid Studio is a memory intensive application and that the two dump files you uploaded are not referencing any specific drivers, I'm going to say that there is quite possibly a RAM issue in which as memory is being used heavily, it causes the system to crash. At this point, run MemTest86+ on your machine to diagnose RAM issues.
--
Tom
Boycott AT&T uVerse! | Tom's Android Blog | AOKP (The Android Open Kang Project)

reply to MikeC578
Your computer appears to have developed a hardware problem which can't be identified from the crash dumps.

crash dump file: C:\Windows\Minidump\113012-33493-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA801B510028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 
 
On Fri 11/30/2012 3:17:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\113012-32744-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA801B41C028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 
 

reply to trparky
Correction, both dump files are referring to hal.dll and ntoskrnl.exe, both of these are core system binaries. Which again, if the kernel crashes (which ordinarily should not happen), that's even more evidence of memory corruption issues.
--
Tom
Boycott AT&T uVerse! | Tom's Android Blog | AOKP (The Android Open Kang Project)

thanx again... I'll run memtest again
--
Mike C

Sometimes, it may take hours for a MemTest86+ test to turn up problems. One pass is not necessarily enough, multiple passes running for 24 hours (or more) may be necessary.

I'm going to run it now and let it run throughout the night... I'll let you know tomorrow if anythings up... I really appreciate your suggestions guys!
--
Mike C

running now - downloaded the latest version of memtest86+ for 64 bit pc's... v. 4.20
I'll be in touch - already well into it's 1st pass - nothing noted in the rror column
--
Mike C

I've often seen tests that won't indicate failure until well into multiple tests. I saw a test that didn't fail until the RAM was at a certain temperature which of course was only after multiple tests.

Temperature of the RAM can make the difference just like CPUs can fail when they are running too hot.
--
Tom
Boycott AT&T uVerse! | Tom's Android Blog | AOKP (The Android Open Kang Project)

reply to MikeC578
Also, if problems persist consider updating the BIOS to the latest version.

The present BIOS version, according to the minidump file, is 0906:

kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=3886]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 0906
BiosReleaseDate = 03/26/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily = To be filled by O.E.M.
SystemVersion = System Version
SystemSKU = SKU
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = P8Z77-V DELUXE
BaseBoardVersion = Rev 1.xx

The latest version appears to be 1709 and several of the more recent updates address stability.

You have a point re: the BIOS. Memtest has been running for almost 8 hours - still no errors...
--
Mike C

Memtest has been running for over 16 hours now - no errors... gonna update the BIOS after I let the program run until the full 24 hours has come and gone...
--
Mike C

reply to MikeC578
The details provided by this dump are the same as the other 2. Have you checked your event viewer yet, just to see if there are any events being posted prior to the crash?

How many different disk arrays/types (hardware) do you have in that thing?