Almost Random BSOD's (7 Minidumps)

[kabukiqf]

System Built less than a week ago.

System Info:
GA-K8N51GMF-9 Motherboard
AMD Athlon64 X2 3800+
3 x 512MB DDR400 (All Kingston)
MSI Radeon X1600 PRO 256MB
(Used both the ATI 6.1 Catalyst, and MSI 8.22 drivers)
160GB SataII Hdd(Main), and several IDE Hdd's 80GB, 120GB, 250GB

WinXP Pro SP2 with latest updates and hotfixes.

The BSOD's occur only when I play certain games, and once at the desktop.
1. When playing NFS: Most Wanted.
2. SW Battlefront II
3. Tigerwoods PGA 2006, with Windows media player also playing
4. One time after I printed off a page and then turn my printer off Canon Pixma IP4000, the USB disconnection sound played then the evil BSOD appeared.???

At all times the save dump event in the viewer left the same bugcheck hexes.
The bugcheck was: 0x0000009c (0x00000004, 0x8054d5f0, 0xb2000000, 0x00070f0f).

I've checked the ram out with MemTest86, and each stick had no errors, and all sticks came from the previous setup anyway.
Completed a disk check and no errors there, also reset the pagefile to 0 and defragged then re did that back to normal.
And now you can have these 7 minidumps and hopefully used your larger brains to tell me what the hell is going on.

Thanks in advance...

 

[kabukiqf]

Trying more stuff without waiting...

I downloaded the debugging tools, and viewed the minidumps myself...


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


Loading Dump File [F:\WINDOWS\Minidump\Mini012106-04.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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.050928-1517
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Jan 21 18:58:54.718 2006 (GMT+11)
System Uptime: 0 days 1:56:58.420
Loading Kernel Symbols
.....................................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {4, 8054d5f0, b2000000, 70f0f}

Probably caused by : ntkrpamp.exe ( nt!KdPitchDebugger+ef4 )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000004
Arg2: 8054d5f0
Arg3: b2000000
Arg4: 00070f0f

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


BUGCHECK_STR: 0x9C_IA32_AuthenticAMD

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

LAST_CONTROL_TRANSFER: from 806e7bf7 to 804f9d1b

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:
8054d5c8 806e7bf7 0000009c 00000004 8054d5f0 nt!KeBugCheckEx+0x1b
8054d6f4 806e2c52 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
8054d6f4 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a


STACK_COMMAND: dds @$csp ; kb

FOLLOWUP_IP:
nt!KdPitchDebugger+ef4
8054d5f0 0100 add [eax],eax

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KdPitchDebugger+ef4

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 433b28b7

FAILURE_BUCKET_ID: 0x9C_IA32_AuthenticAMD_nt!KdPitchDebugger+ef4

BUCKET_ID: 0x9C_IA32_AuthenticAMD_nt!KdPitchDebugger+ef4

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



Now I have very little idea what it all is, but I assume that it could be my processor at fault, now these amds have a driver also.. (argh drivers)
I have amd v1.2.2 installed right now, and im gonna try v1.2.2.2 (a whole extra .2)

And going to muck round to see if it crahses again... probably will, so please do your thing and tell me what the hell it is...

 

[howard_hopkinso]

Hello and welcome to Techspot.

For whatever reason(probably corruption) I can only open one of your minidumps. When I try to open any of the others the debugger crashes.

The one minidump I can open crashes at ntkrpamp.exe. This is the Windows nt kernel and system file. The mindump has a bugcheck of 9C.

0x0000009C: MACHINE_CHECK_EXCEPTION

This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).

Can you please Zip the mindumps together again, and re-attach them.

Regards Howard :wave: :wave:

 

[kabukiqf]

test 1006 - no more minidumps

I took out the Ati X1600 Pro, and just used the mobo's onboard gfx card for a bit.

I havent had a single crash, but it may be due to the fact the onboard gfx doesnt expect much for the pc.

I'll borrow someones card later and see if I get the same kind of BSOD to test the PCIe graphics slot and all that jazz.

PS. I have nothing overclocked, and as for overheating.. the air con brings the room temp down to 20 degress celcius, and then for good measure, I opened the side panel and faced the desk fan towards it, the cpu temp dropped 5 degrees with that..




I'm gonna go find me a white man and lie to him right now - The Boondocks

 

[alanhemenway]

This was solved for me. It was the power supply.

This was solved for me.

When my computer would get this crash, almost every night, when I wold re-boot, a message invited me to submit a report to Microsoft and Microsoft generated a message that said that my problem was either the CPU, Memory, Video Card, or Power Supply. I have an AMD 4400 on a Gigabyte board, 1 gig of Corsair RAM, BFG 7800 OC, and the 430W Antec PSU that came with the case, and it is all about one year old. I called either Gigabyte or nVidea and they had me run a diagnostic test by logging on to CPUID.COM and I went to PC Wizard and did the Self Install. It told me that my power supply was running at 11.47 Volts instead of 1.8 - 1.9 Volts. I now have a 550W PSU and the computer no longer crashes.

 

[cpc2004]

What bugcheck do you have?

Hi Alan,

Thanks for sharing your experience with us. It would be much helpful if you would provide the bugcheck of your crash. You can find the bugcheck code at system event log 1001 and 1003.