Machine_Check_Exception - Stop 0x9c

TVeblen · 29 May 2010

I'm driving down the highway and I get a frantic call from my daughter.

She sat down to use this computer (my specs), opened Winamp. The usual play list was gone - there was only one entry. The day before I was listening to a streaming radio broadcast in Winamp. That stream was the entry that Winamp makes when you link from the radio station's website.

When she clicked on the "song" the computer crashed. She wrote down the bluescreen info:

Machine_Check_Exception
Stop 0x0000009c
Minidump zip attached.

Told her to hit reset. She said when the computer restarted it took a long time on a black screen. After that all is right and no further probs.

Never seen this error before. Does anyone have any ideas what may have happened?

Thanks.

usasma · 29 May 2010

She's not supposed to have this error if she's running Vista or Win7. This error was last seen in XP - but you will see it in some Vista/Win7 systems if there's a dual boot w/XP or some virus infections.

Info on it here: BSOD Index

I'd suggest trying a couple of these free, online scans to make sure nothing has corrupted her current protection: Malware (read the details at the link)

Other than that, it could be broken hardware or an incompatible piece of hardware or software.

List of loaded drivers:

Code:

fffff880`01047000 fffff880`01052000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`04246000 fffff880`0428d000   avgldx64 avgldx64.sys Wed Feb 10 22:52:31 2010 (4B737EFF)
fffff880`015f7000 fffff880`015fe080   avgmfx64 avgmfx64.sys Wed Feb 17 17:40:14 2010 (4B7C704E)
fffff880`04056000 fffff880`040a7000   avgtdia  avgtdia.sys  Tue Apr 13 17:12:20 2010 (4BC4DE34)
fffff880`06c23000 fffff880`06c2b000   cpuz132_x64 cpuz132_x64.sys Thu Mar 26 19:17:23 2009 (49CC0D03)
fffff880`04d0e000 fffff880`04d19000   dump_msahci dump_msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`00c35000 fffff880`00c52000   jraid    jraid.sys    Wed May 27 01:39:35 2009 (4A1CD217)
fffff880`06c2b000 fffff880`06c35000   LVPr2M64 LVPr2M64.sys Wed Oct 07 04:26:50 2009 (4ACC50CA)
fffff880`00c2a000 fffff880`00c35000   msahci   msahci.sys   Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`10b9d000 fffff880`10b9e180   nvBridge nvBridge.kmd Sat Apr 03 19:50:52 2010 (4BB7D45C)
fffff880`0fe73000 fffff880`10b9c700   nvlddmkm nvlddmkm.sys Sat Apr 03 20:06:21 2010 (4BB7D7FD)
fffff880`044e6000 fffff880`0453d000   Rt64win7 Rt64win7.sys Thu Mar 04 08:42:52 2010 (4B8FB8DC)
fffff880`06846000 fffff880`069f2900   RTKVHD64 RTKVHD64.sys Fri May 22 14:04:20 2009 (4A16E924)
fffff880`015f0000 fffff880`015f7000   speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)

Summary of the BSOD:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 28 14:52:41.005 2010 (GMT-4)
System Uptime: 0 days 4:34:08.097
BugCheck 9C, {0, fffff880009bac70, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )
BUGCHECK_STR:  0x9C_GenuineIntel
PROCESS_NAME:  winamp.exe

TVeblen · 30 May 2010

Thanks for the dump report Usama.
She was using my computer (My System Specs below) running W7 64 bit.

I had her run AV and malware right away: clean.

It could very well be that Winamp Lite v5.572 is incompatible. The program loads funny on occasion, I believe due to issues with UAC. I should create an elevated shortcut for it, but it was just too low on the priority list.

My WAG (Wild Ass Guess): by clicking on the stream play in Winamp it initiated a process that required a browser to be running (it wasn't) and linked to the website feeding the stream and this caused a logic error?

My current thinking is that one time is an aberration, two times starts a pattern. So I plan to just keep an eye on it. Do you think that is wise?

Thanks for looking at this and for your help.

Jonathan_King · 30 May 2010

That's my thoughts. Everyone gets a BSOD every now and then, but it's not a big deal unless it starts becoming a real problem.

Besides, a single dmp can only tell so much.

usasma · 30 May 2010

If you suspect WinAmp, check it out here: http://www.microsoft.com/windows/com...namp&os=32-bit
It appears that the 32 bit is compatible - but something's up with the 64 bit version!

One of the most overlooked portions of the BSOD screen is where it says (most times):
"If this is the first time that you've seen this error - restart your computer.
If this screen appears again, follow these steps: . . . "

From Wikipedia: File:Windows XP BSOD.png - Wikipedia, the free encyclopedia

TVeblen · 30 May 2010

usasma said:

If you suspect WinAmp, It appears that the 32 bit is compatible - but something's up with the 64 bit version!

Now that is interesting! And it explains what I am seeing. I will be looking for the next upgrade.

One of the most overlooked portions of the BSOD screen is where it says (most times):
"If this is the first time that you've seen this error - restart your computer.
If this screen appears again, follow these steps: . . . "

Now that kind of talk is going to put a lot of repair shops out of business!

I've always preached about the amazing rejuvenating powers of the occasional restart. It amazes me to hear about people who never shut down for weeks!