BSOD - Machine Check Exception

[Rookie1986]

Hey,

Just has a BSOD with a Machine Check Exception error, does anyone know what this could be?

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 9c
BCP1: 0000000000000000
BCP2: FFFFF880033BCB70
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\051312-15537-01.dmp
C:\Users\Steve\AppData\Local\Temp\WER-21793-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

This isn't the only BSOD I've had since finishing my build, I also get one if I install the utilities (not Drivers) from my motherboard disk but I haven't recorded that log and since I removed the utilities the problem hasn't happened again.

Hope someone can help me,
Rookie

[Tifosi]

whats in

C:\Windows\Minidump\051312-15537-01.dmp
C:\Users\Steve\AppData\Local\Temp\WER-21793-0.sysdata.xml

[Phage]

This is a really handy tool for translating those minidumps and error messages.
http://www.resplendence.com/whocrashed
What does it tell you ?

[Rookie1986]

Hey,

Sorry for not getting back to this but after another crash today it reminded me that I had made this thread. I have downloaded whocrashed and these are my three errors or what ever you want to call them:

On Tue 15/05/2012 14:31:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x9C (0x0, 0xFFFFF8800334AB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown MACHINE_CHECK_EXCEPTION

Todays crash

On Sun 13/05/2012 22:40:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051312-15537-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880033BCB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 13/05/2012 17:34:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051312-17986-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800569D150, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

And then my two crashes from Sunday.

[shaithis]

Test with 1 stick of RAM at a time.

[Phage]

As above, sounds like a dodgy ram stick.
Memtest will find that out.

[Rookie1986]

I know this is going to sound silly but....... how do I test the RAM??

[shaithis]

You have 2 sticks? Pull one out.......run system until it crashes or your happy it isn't going to crash.....then swap the sticks.

[Rookie1986]

You have 2 sticks? Pull one out.......run system until it crashes or your happy it isn't going to crash.....then swap the sticks.

But its took 2 days to replicate the problem.... there must be a better way??

[GoNz0]

not really, i see you have corsair ram, it will need to be set in the BIOS at the correct rated speeds as well.

leaving it to auto detect is not good with corsair RAM.

you can download a memtest86 cd to speed up the testing phase.

[Phage]

http://www.custompcblog.com/troubles...tutorial-guide
Memtest how-to.

[Rookie1986]

not really, i see you have corsair ram, it will need to be set in the BIOS at the correct rated speeds as well.

leaving it to auto detect is not good with corsair RAM.

you can download a memtest86 cd to speed up the testing phase.

Well that's a shame, guess I might as well remove one stick and see how things go, is there anyway to stress the RAM to see if it's faulted?

My RAM was installed by Scan, so it should be right shouldn't it. I don't think I'm able to alter their settings in the BIOS without voiding my warranty am I??

[GoNz0]

My RAM was installed by Scan, so it should be right shouldn't it.

i have seen plenty of posts on here to prove otherwise.

if they installed it i suggest you contact them.

[Rookie1986]

Ok, I've ran the memtest and it came back 100% Pass no Errors found.... so now begins my new nightmare , if its not the RAM what could it be? My Mrs is going fkn nuts with me about this, things along the lines of:

£2000 for a computer that keeps crashing

I told you not to build one yourself

Should have just ordered that Alienware system like I told you to

Maybe its time to go prep the sofa bed - Its fun to be me

Rookie

[Carlh]

i have seen plenty of posts on here to prove otherwise.

if they installed it i suggest you contact them.

GoNz0

How can you install memory wrong?? as surely the memory will only go in one way

Please provide prove of where these "posts" are which have shown SCAN have installed memory incorrectly.

[kalniel]

My guess is hard drive issues, possibly just bad software/drivers.

Check that SATA cables are tightly connected as they can easily come loose in transit

Run a full chkdsk (/r) http://support.microsoft.com/kb/315265 to check for bad sectors.

Check BIOS is updated, try running the hard drive in IDE mode or update ACHI drivers.