Reading DVDs results in a BSOD and Machine_Check_Exception 1

[festivus528]

Anytime I put a DVD into my DVD drive, my computer will reboot and I will get a BSOD. The error I get is a Machine_Check_Exception with the error code: STOP: 0x0000009c(0x00000004,0x8054d5f0,0xb2000000,0x00070f0f). I have tired multiple drivers, and changed the ide cable. When I changed the IDE cable, I was able to play Oblivion. When I shut down and restarted, my computer would not boot until I took the disc out. This problem is recent, as I was able to load DVDs a month ago. The only thing I have changed hardware-wise would be a Viewsonic vx2025wm and a Creative X-Fi xtrememusic.

My computer:
AN8-SLI Premium (latest Bios)
AMD x2 3800+ (Not overclocked)
eVGA GeForce 7800GT
1 Gb Corsair XMS TWINX1024-3200C2PRO
Western Digital 160Gb Caviar (SATA)
Lite-On Combo Drive
Creative X-Fi Xtrememusic

I am stumped on this one. Any help would be greatly appreciated.

 

[festivus528]

I ran memtest on July 25, in response to your first post. Do you think I should retry it? I'll set up a mini dump and see whatI can find.

 

[festivus528]

I can't read the memory dumps. It opens and then closes immeadiately.

 

[festivus528]

Ok I figured out how to get it but I can't understand it. Here is what I get for every mini dump:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini082006-01.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 Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Aug 20 14:09:41.656 2006 (GMT-7)
System Uptime: 0 days 0:40:34.345
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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:
------------------

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000000000000001110000111100001111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_PCC_BUSCONNERR_30F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_IA32_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 806e7bff to 804f9c37

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


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: 0x9C_IA32_AuthenticAMD_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0x9C_IA32_AuthenticAMD_ANALYSIS_INCONCLUSIVE

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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:
------------------

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000000000000001110000111100001111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_PCC_BUSCONNERR_30F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_IA32_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 806e7bff to 804f9c37

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


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: 0x9C_IA32_AuthenticAMD_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0x9C_IA32_AuthenticAMD_ANALYSIS_INCONCLUSIVE

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

 

[stduc]

You appear to have either a faulty CPU, Mobo, or possibly faulty DVD drive or cables. I am not enough of an expert to tell. Your HAL layer could even be corrupt.

Hopefully some who knows more than me will take a look at this thread.

Meanwhile.

Can you upload the minidump so people (inc me) can take a look at it themselves? (use

http://www.Rapidshare.de

or similar free service & post the link back here.)

If you have a spare hard drive you could try removing your current drives and see if you can re-install windows on the new drive. I see several possible outcomes to doing this.

1- Windows installs just fine - the problem is solved. In which case you could replace the original drives & attempt a repair?

2- Windows fails to even install (suggests you do have serious hardware problems)

3- Windows installs but the problem is still there - unlikely outcome I think.

Before you go down the new DVD drive/Mobo/CPU route I think you should wait for further advice. Meanwhile post your dump and pray I can see a definite answer! Although I would suspect the DVD drives cables, then the DVD before the mobo or CPU. But what do I know?

 

[festivus528]

Okay here is the link:

http://rapidshare.de/files/30244544/Memorydump2.WEW.html

I have changed the DVD cables, to no avail.

 

[stduc]

All I got was a file called Memorydump2.WEW that wasn't a memory dump! It was only 1Kb in size!!!!!!!!!!!

I have no idea what it was - but can you try again?

You need to upload "Mini082006-01.dmp

 

[festivus528]

Haha oops. Here you go:

http://rapidshare.de/files/30247894/Mini082006-01.dmp.html

 

[stduc]

That's better.

Well, I get a different result than you did. I didn't get ERROR: FindPlugIns 8007007b or your NOTE: This is a hardware error...........

I did get (amongst the "garbage")

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

and
0: kd> !process
GetPointerFromAddress: unable to read from 80561114
PROCESS 8055b0a0 SessionId: none Cid: 0000 Peb: 00000000 ParentCid: 0000
DirBase: 00310000 ObjectTable: e1000ed0 HandleCount: <Data Not Accessible>
Image: Idle
VadRoot 00000000 Vads 0 Clone 0 Private 0. Modified 0. Locked 0.
DeviceMap 00000000
Token e1001ad8
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
ffdf0000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 0
QuotaPoolUsage[NonPagedPool] 0
Working Set Sizes (now,min,max) (7, 50, 450) (28KB, 200KB, 1800KB)
PeakWorkingSetSize 0
VirtualSize 0 Mb
PeakVirtualSize 0 Mb
PageFaultCount 0
MemoryPriority BACKGROUND
BasePriority 0
CommitCharge 0

THREAD 8055ae40 Cid 0000.0000 Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 0
*** Error in in reading nt!_ETHREAD @ f77aee20

So I guess your installation of WinDBG was somehow incomplete. (Did you install on the machine you are having trouble with?)

I found this though.

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).

at Almost Random BSOD's (7 Minidumps)

Now given I am no debug expert - so I really hope one takes a look at this. My interpretation is:-

It's caused by a corrupt HAL (unlikely) or it's a memory error - specifically at location 80561114 Or your CPU is bad.

the !process command points to the idle process being the cause of the problem. Or rather - being the task executing at the time.

So, all in all I think its most likely you have dodgy RAM.

Have you run memtest86 for a decent period of time since you changed the PSU? If not, do so and ensure it is testing all your RAM.

However - from info on the link above I would say its a possibility its actually a problem with your graphics card.

So, if memtest passes OK - then change your graphics card? If you decide to do that - then uninstall the drivers of the current card first, shut down & replace the card and re-boot. If you just replace the card then windows can get confused.


If it turns out I'm wrong - I'll say sorry now (in advance)

 

[festivus528]

I haven't run memtest since I got my new PSU, so I'll run it overnight and see what I get. I don't have another graphics card to test with.

 

[stduc]

Shame you don't have another card. Try changing your settings. If the problem goes away when you reduce resolution/number of colours - then it seriously implicates a problem with the graphics card or its drivers.

That's assuming memtest86 comes up clean overnight.

 

[festivus528]

Memtest passed with no errors. I'll try changing my settings right now.

 

[festivus528]

I am typing this right now with Band of Brothers in my drive! I lowered my resolution to 1024x768 and the colors to 16-bit, and no BSOD. So is this my card or the driver?

 

[stduc]

More than likely the driver - go to the manufacturers web site & see if you can find an update.

 

[stduc]

Or up the colours / resolution until you find the fail point and see if you can live with it.
Or buy another card anyway.?

Hopefully the manufacturers website will offer an update that fixes the problem and doesn't introduce another one!

 

[festivus528]

They don't have any updates. Only drivers. Couldn't I just try to reinstall the drivers and see if it works? Could I RMA the card?

 

[festivus528]

Okay, I reinstalled the driver (nVidia 91.31) and then put in Band of Brothers. No BSOD. I open Windows Media Player and start watching. I don't feel like watching the special features, so I put in a different disc. This time I got a BSOD.

Why would it work that one time and not the other?

 

[tekuser999]

Hey Guys,
You seemed to have looked at all components and change whatever you can get your hands on but have you tried to change the DVD drive and see if the problem goes away?

 

[festivus528]

Yes, I tried another drive and got the same problem.

 

[cupid11213]

ok i see that you guys have done some extensive homework on this and all you guys did great.

I recently came across the same error you have with a clients computer and i also could not install a printer or the computer would restart and then give a bsod.but none the less i had the exact same error you have right now.

I know that alot of things sometimes points at hardware but in my case it turned out to be windows. I reinstalled windows xp sp2 pro and then never had a problem since and i have myself one happy customer who didnt have to purchase a new mobo (wich was what we believed to be faulty)

i'd recommend instead of spending more money on things that might resolve it or not. Spend a few hours to do a back up and a clean install of windows, if that does not solve your issue then you can be really sure that you have a hardware problem.


good luck with your issue and hopefully you can solve it soon.


Luis

Some people make things happen, some people watch things happen, while others wonder what happened.

 

[festivus528]

I need to try that, but its hard to backup when you can't burn DVDs.