Blue screen

[007Raider]

I keep getting a random blue screen stating that there is an uncorrectable hardware and windows has to shut down......there is a lot more to the error, like numbers and stuff... however, i did not get all of it before it rebooted. what do i need to do to fix this. all my graphics and sound card drivers are up to date. the only driver i cannot seem to figure out is my mobo chipset driver. that is another question. asus has a download on their website for the mobo chipset driver and it is 530 Mbs and Nvidia has a nforce update for the chipset of 131 Mbs? which one do i install? How do I fix the blue screen?

 

[Flavius]

Find in C:\Windows\Minidump any *.DMP files and debug them - it may help you to diagnose problem.See below how to do.
How to read the small memory dump files that Windows creates for debugging

 

[kword88]

i would go with the update from asus. it should include the nforce drivers.

 

[H2SO4]

What Flavius said.

Although, if it's reporting a "Machine Check Exception" (read the text at the top), that's a hardware error report and Windows is merely passing the message along. Driver updates will not help in that case.

 

[patio]

Post the entire blue screen message...including the gibberesh.

 

[007Raider]

awesome help gents! i will check the minidump and follow the directions for the debug. i will also post the entire screen today when i can make the machine fail?. however, i was able to generate the screen via a memory check test? i believe that is what it is called... that caused the blue screen to come up before vista even booted.

now regarding the chipset driver from asus.... each time i try and download the 530 Mbs, it tells me it will take 10 hrs?? is there anyway i can get it faster.. i know it should only take 35-60 mins or less.

 

[007Raider]

i am trying to install the chipset driver from asus' web page... on their global server

 

[007Raider]

H2SO4 and others... the BSOD did say uncorrectable hardware error.... is that what you are talking about, and there is NO help? does that mean part of my system is incompatible with the rest?

 

[lordbob75]

Hello 007 Radier,

It could be a BIOS problem, or a bad mobo, or incompatible hardware. However, we will not know until we see the BugCheck code. That should be similar to 0x00000b3. If you can only get one thing from the BSOD, get that.

~Lordbob

 

[007Raider]

thanks for the help, i did my best with the debugger and this is the information i recieved... i attached the three BSOD minidumps from the windbg program.. what do you think my issue is? can i fix it?


View attachment mini030409-03.TXT

View attachment mini030409-01.TXT

View attachment mini030409-02.TXT

 

[Klaudius]

ASUS boards hurt, they are fast, they have amazing options, but the pain involved in troubleshooting wierd problems like this that always show up will hurt you.

My first idea would be do the following if you dont have data you need to save.
1)reformat
2)reinstall windows
3)install motherboard drivers

/rant apology
I went to google, typed in ASUS motherboard blue screen, and here is my result

ASUS motherboard bluescreen - Google Search

First I will start off by saying im sorry.
It could be anything, loose memory on the board, bad nvram chip, bad pci slot, memory falling off, cpu seated wrong, cpu overheating, bad powersupply, CPU voltage settings wrong for MHZ setting, video card not allowing air to pass through case, motherboard built on a friday at 4:59 PM by an angry robotic arm, gnomes....

It was so bad for me building machines with ASUS componants that I switched to intel and never looked back.
/end rant apology

 

[H2SO4]

It's a hardware problem, unfortunately. Reinstalling Windows and updating drivers is very unlikely to achieve anything.

Intel and AMD both have different names for a mechanism whereby the hardware can report certain types of failures. In this case, the OS is simply passing on that message in the form of a bluescreen.

There's actually more data in your minidumps. From the first one:

"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: 0000000000000000, Machine Check Exception
Arg2: fffffa80073b4030, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b636c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value."
​

In other words, the Windows Hardware Error Architecture (WHEA) has detected a Machine Check Exception (MCE). You could look up the precise meaning of those 64 bits that comprise the MCi_STATUS in AMD docs, but nowadays the debugger can do that for you, to a certain extent.

Try this:

1) Fire up any of those minidumps in WinDBG again.
2) At the prompt, type: .SYMFIX c:\SymCache <enter>
3) Then, type: .reload <enter>
4) Then: !analyze -v <enter>

That should fix up your debugger symbol loading issue (as long as the machine running the debugger can access the MS web symbol server at the time) and cause the analysis to give you more info. If you post the new results here, someone might be able to suggest which part of your hardware sounds most likely to be the culprit.

 

[007Raider]

Ok, I will do that this afternoon and repost any new information... On the other hand, can my mobo handle an overclock? it says it can, but to what degreee is my question? i say this, b/c i have my 7750 BE overclocked just a little (from 2.7 - 3.1) Could that be causing the issue? I did it by bumping up the multiplyer instead of the BUS. According the the info I have, the CPU maxes out at 3.7.....so i figured i am ok... Any opinions?

 

[lordbob75]

Any mobo can handle an overclock, but it always needs to be cautiously done.

If you are going to try, do it slowly, and check each step.

~Lordbob

 

[H2SO4]

Overclocking frequently causes crashes and it may very well be responsible for your crashes too.

By definition, overclocking components means driving them beyond their design specs. It's a bit like asking "if I use something in a way for which it wasn't designed, is there a chance it may fail?". Yes.

Not overclocking should be the first thing you do at this point in time. It's pointless to troubleshoot ongoing machine check errors while the box remains overclocked.

 

[lordbob75]

Overclocking frequently causes crashes and it may very well be responsible for your crashes too.

By definition, overclocking components means driving them beyond their design specs. It's a bit like asking "if I use something in a way for which it wasn't designed, is there a chance it may fail?". Yes.

Not overclocking should be the first thing you do at this point in time. It's pointless to troubleshoot ongoing machine check errors while the box remains overclocked.

Exactly. I agree. Have some rep.

~Lordbob

 

[007Raider]

the windbg is not working right....or at least not how you stated it would. i am not getting any symbol confussion cleared up. any pointers? i am not even sure i am running the debugger correctly.

 

[007Raider]

will do....thanks for the help

 

[007Raider]

here is the report i am getting.... any ideas? it took almost 3 weeks to get anther error.

Description
A problem with your video hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.0.6001.2.1.0.768.2
Locale ID: 1033
Files that help describe the problem
WD-20090301-1427.dmp
sysdata.xml
Version.txt
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.
Extra information about the problem
BCCode: 117
BCP1: FFFFFA8004A984E0
BCP2: FFFFFA600261A1A0
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

 

[007Raider]

here is another error i keep getting...

Description
Windows was able to successfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is 31.
Problem signature
Problem Event Name: PnPDeviceProblemCode
Architecture: x64
Hardware Id: V1394\HOST_DEBUGGER
Setup class GUID: {66f250d6-7801-4a64-b139-eea80a450b24}
PnP problem code: 0000001F
Driver name: 1394kdbg.sys
Driver version: 6.1.7015.0
Driver date: 02-26-2009
OS Version: 6.0.6001.2.1.0.768.2
Locale ID: 1033
Files that help describe the problem
DMIFBD7.tmp.log.xml
LOGFD00.tmp
oem23.inf
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.