• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BSOD is killing me...

F

FrozenYak

Senior member
Hi, I bought a variety of new hardware and occasionally at startup it is giving me a

Machine_Check_Exception

Now with how much hardware that has been added I dont know enough to be able to tell what hardware exactly is causing the problem. Is there any somewhat reasonable way to understand the MCE's?

My specific error is

0x0000009c (0x00000000, 0xbab3c050, 0xb2000040, 0x00000800)

Any suggestions appreciated
 
A quick google search shows many mention a Creative Labs sound card..........maybe uninstall the sound card software and uninstall the sound card and see what happens?
 
Thanks, but I dont even have a sound card installed right now (never did care much for anything but the basics). The only sound software I have is what came with my EVGA mobo and ive been having the problems since before I installed it.

I figured it may be a memory problem, and I did have some errors pop up when I ran a mem test, but I moved them around and so far have not received any new errors from the memtest (it's still running). I thought that was the fix but I got the BSOD again when I reloaded up.
 
Originally posted by: FrozenYak
Hi, I bought a variety of new hardware and occasionally at startup it is giving me a

Machine_Check_Exception

Now with how much hardware that has been added I dont know enough to be able to tell what hardware exactly is causing the problem. Is there any somewhat reasonable way to understand the MCE's?

My specific error is

0x0000009c (0x00000000, 0xbab3c050, 0xb2000040, 0x00000800)

Any suggestions appreciated
Click to expand...

Open the dump in the debugger and post the output from !analyze -v - see my .sig and website for full details on the howto.
 
Ok thanks dclive, ill try that when I get home.

I did run a memtest but I believe I fixed what was causing its problems. I may get memtest86 and give it a try later too quicksilver.
 
I searched and cant seem to find any windows dump file on my comp aside from if I download your example. My install is recent I have experienced crashes since then...is there a reason it wouldnt be there?
 
If you're getting BSODs, you should have a c:\windows\minidump folder or a c:\windows\memory.dmp file. Can you confirm you have neither?
 
Is your pagefile located on c: ?

Is your PC set to write a dumpfile (kernel is best) ?

Both can be found in MyComputer (rightclick) / Advanced ...
 
It's set up to write a small memory dump (64kb) to %systemroot%\minidump so as far as I can tell then it should be there somewhere, but looking manually or searching doesnt reveal anything.

Not sure about the pagefile, when i try to change the memory dump type it gives me a warning about the pagefile size on C:
Edit: Yes the pagefile is located on C:

I set it to kernal anyway and changed where it saves....im off to see if i can crash it again, maybe it will record this time.(Gee never thought I'd be trying to get my computer to crash)
 
Nope...doesnt look like there is any dmp file being saved. Would it matter if the BSOD was happening before the system actually loads?
 
Nope; it will still write there assuming it can boot up enough to do so. If you can reboot and get into the OS, it should write that file.
 
Well thanks for the help...cant seem to find this file anywhere. I think it's time I finally took it in to have it looked at. This has gone way past my knowledge base.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top