BSOD - Machine Check Exception

[shaithis]

What should I do if I find that having the system not overclocked means it works because I paid scan to overclock it for me and TBH I don't want it non-overclocked because I've spent a lot of money on cooling and parts to make sure it could be overclocked.

One of the reasons I won't pay premium for "pre overclocked" is that I don't believe for a second that the kit will have been properly tested at the advertised speed. The amount of time and effort required to do so is way too much for it to be financially viable......so why pay for something you know has not been done properly?

[Rookie1986]

One of the reasons I won't pay premium for "pre overclocked" is that I don't believe for a second that the kit will have been properly tested at the advertised speed. The amount of time and effort required to do so is way too much for it to be financially viable......so why pay for something you know has not been done properly?

Because:

1). I don't 100% know it hasnt been done properly.

2). I wouldn't know how to do it myself.

[Rookie1986]

I haven't had a BSOD now for the last two days, is it possible that by turning off sleep mode, resetting the BIOS to default and then reloading the OC profile could have fixed my problems or am I just sitting & waiting for another BSOD??

Rookie

[Rookie1986]

Maybe I spoke to soon:

On Sun 20/05/2012 13:10:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16239-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009C0180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[Rookie1986]

On Sun 20/05/2012 13:28:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16333-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCB545)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000EB545, 0xFFFFF8800C2F2B70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 20/05/2012 18:05:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009C0180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

I've also had several other crashes that don't show up in WhoCrashed, is this normal?

Rookie

[Phage]

depends on the type of crash. BSODs will create a dump to be analysed. What are the other crashes ?
Do they occur when you're doing something particular ? I've had Grey crashes (GSOD) with overclocked memory on the GPU and thermal shutdowns when it just turns itself off.
What have you got ?

EDIT: You need to speak to scan. Whatever it is, it seems related to tne core of the system so I'm looking at CPU, RAM or the OC.

[Rookie1986]

Hey Phage,

I'm getting three main types of crashes, some are just back to the desktop where everything freezes up for a few seconds (only happens when gaming) and then I can continue on as normal, the second type of crash that I’m getting is where everything freezes and then my speakers make a loud buzzing//juttering noise and my PC restarts or finally I get the BSOD's that I've documented above. The BSOD and other crashes happen when doing almost anything; I'm getting them during BF3/Diablo 3, when listening to music on iTunes, when watching videos on YouTube, when typing in Microsoft Office and even when just browsing the web.

I guess that’s not much help in pinpointing the problem because it could be just about anything, its kind of disappointing because it’s really took the shine off getting and building my own computer and would make me think twice in the future about even considering something like this, that’s if Mrs Rookie will ever let me anyway after the way things have been…. That Alienware looks the better choice than dropping over 2k on a system like I have

I’ve opened a support ticket with Scan and they have been in touch via the Hexus support site, PM and email but at present things don’t seem to be any further forward. I guess I can only wait until next week and see if they have a solution for me but what happens if they don’t? Will I be stuck with a 2k+ BSOD ornament???

Rookie

[Phage]

That buzzing crash is fairly common. I used to get them all the time. Appears to be some sort of weird sound driver conflict. If you google buzzing sound loop crash you'll see what I mean.

Reading what you've posted above, and my experience with weird crashes I think your problem is actually your GPU. Certainly all my GSODs, Buzzing crashes etc all went away when I changed my GPU. Is your GPU XFX ? Their memory is notorious for not playing well with an OC. Have you got an old GPU to test ?

Also there's no guarantee your Alienware wouldn't have the same issues. Check their forums...

[Rookie1986]

That buzzing crash is fairly common. I used to get them all the time. Appears to be some sort of weird sound driver conflict. If you google buzzing sound loop crash you'll see what I mean.

Reading what you've posted above, and my experience with weird crashes I think your problem is actually your GPU. Certainly all my GSODs, Buzzing crashes etc all went away when I changed my GPU. Is your GPU XFX ? Their memory is notorious for not playing well with an OC. Have you got an old GPU to test ?

Also there's no guarantee your Alienware wouldn't have the same issues. Check their forums...

I sold my old GPU when I bought the XFX 7970 so no I don’t have another GPU to test with, I knew I should have got the GTX 680 like my brother said - But what about the Motherboard crashing to blue when the drivers/utilities are installed from the provided disk, surely that can’t be anything to do with my GPU…. Can it???

Yeah I guess, but then it would have just been boxed up and sent back to Dell to be fixed, I can't really box it up and send it back to myself can I lol because I can't fix it

Rookie

[Rookie1986]

Oh, another one I forgot to post:

On Sun 20/05/2012 21:14:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0xB, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Happy Days

Rookie

[Phage]

Well. The install of W7 certainly seems buggered. If all of these are down to MoBo drivers, then you certainly can get scan to fix them up. What have they said so far ?

[Rookie1986]

Well. The install of W7 certainly seems buggered. If all of these are down to MoBo drivers, then you certainly can get scan to fix them up. What have they said so far ?

I'm still waiting for a reply about it

Rookie

[Phage]

Get them on the phone. Always better than email or forum.

EDIT: I also have an old 2600 Pro GPU you can borrow for testing if needed. One of these.
http://hexus.net/tech/reviews/graphi...locked/?page=2

[Rookie1986]

Get them on the phone. Always better than email or forum.

EDIT: I also have an old 2600 Pro GPU you can borrow for testing if needed. One of these.
http://hexus.net/tech/reviews/graphi...locked/?page=2

I'm stuck at work right now... Well all day in fact so won't be able to phone them today.

Thanks for the offer of the 2600 but it looks like my brother is going to drop in his 460 to test it with.

Regards,
Rookie

[Rookie1986]

I've been advised via email to increase the voltage from 1.30v to 1.305 to see if that offers more stability,

I will have to check this out tonight and see how things go.

Rookie

[Rookie1986]

That buzzing crash is fairly common. I used to get them all the time. Appears to be some sort of weird sound driver conflict. If you google buzzing sound loop crash you'll see what I mean.

Reading what you've posted above, and my experience with weird crashes I think your problem is actually your GPU. Certainly all my GSODs, Buzzing crashes etc all went away when I changed my GPU. Is your GPU XFX ? Their memory is notorious for not playing well with an OC. Have you got an old GPU to test ?

Also there's no guarantee your Alienware wouldn't have the same issues. Check their forums...

Would running something like FurMark test my GPU to make sure it's 100% working??