BSOD - Machine Check Exception

[Rookie1986]

Still getting the BSOD with the altered voltage

On Mon 21/05/2012 21:47:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052112-16348-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003342180, 0x2)
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 sent an email off to Scan asking if they have any more ideas or if the system is going to have to have an RMA opened on it.

Rookie

[Phage]

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

I tried that - It seemed to be Ok with Furmark. Worth a try though. Try Heaven and 3dMark11 for good measure.

I used to get the buzzing crashes only in game, but YMMv as they say. What drivers are you using for the card ? latest from AMD I assume ? 12.4 I think today.

Everything I've seen from here and your other thread tells me the OC is not holding. It's also interfering with the GPU. Is your 7970 OC'd as well ? try underclocking the VRAM. This may well help with the buzzing and non-BSOD crashes.

[Rookie1986]

I tried that - It seemed to be Ok with Furmark. Worth a try though. Try Heaven and 3dMark11 for good measure.

I used to get the buzzing crashes only in game, but YMMv as they say. What drivers are you using for the card ? latest from AMD I assume ? 12.4 I think today.

Everything I've seen from here and your other thread tells me the OC is not holding. It's also interfering with the GPU. Is your 7970 OC'd as well ? try underclocking the VRAM. This may well help with the buzzing and non-BSOD crashes.

Yeah FurMark ran fine for the full 15 minute test. My GPU got to a max temp of 72 but my FPS average was only 32 which sounds low to me (not that I have a benchmark to compare to).

I've had the buzzing crashes the most while watching YouTube and yes I'm running the latest drivers, the XFX disk that came with the GPU couldn't find it when I tried to use it so I had to download the drivers directly frm the ATI website.

The XFX 7970 shipped as OC but I haven't touched it myself. I'm now just waiting for an email from Scan (or as Mrs Rookie keeps calling them "Scam" - j/k j/k but I was in creases when she said it). I just hope it's earlier this morning rather then late on in the afternoon so if they do require me to try some other settings I get some test time before their office closes.

Rookie

[Phage]

No - Don't wait. It's your money and it does seem like the OC is the issue. hang on the phone until they answer.

[Rookie1986]

My GPU seems to perform better when the OC is turned off, it this normal?

[Phage]

The 7970 ?
If it's an XFX yes. Fits my earlier theory.
Otherwise it's not no. My Gigabyte loves every Hz I can wring out of my 920.

[Rookie1986]

Yeah its an XFX card.

I've now been running my computer with the BIOS set to default all day and not had a single BSOD so it looks like what you were saying is right Phage, and that the problem does in fact lie with Scans Overclocked bundle and not my other components. Still awaiting a response via the forums, email or a call back to see where we go from here.

Anyone know what Scans usual protocol is if they ship out a faulty OC bundle? Please say I'm not going to have to remove everything from my case to send it back

Rookie

[Phage]

Yep. I'm afraid so.
You should really get them on the phone. These things are so much easier in real time.

[Rookie1986]

Voltage up to 1.32 now as advised and still having some problems:

On Wed 23/05/2012 02:57:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052312-17066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF88005E3638C, 0x0, 0xFFFFF880049C85D8, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.

[GoNz0]

get your money back and buy a decent package instead.

[Rookie1986]

get your money back and buy a decent package instead.

I am past my 7 days now so wouldn't be able to return it for my money back.

[Phage]

Yes - but you have ample evidence that the machine is unstable. I believe that under 30 days they have the obligation to prove that it is NOT faulty under the SoGA. You can still get it swapped.
I can't stress enough that you need to speak to them directly. Communication is what it's all about.

[Rookie1986]

I've been advised by Scan to try one more setting change. I've now changed the load line setting from Lv.5 to Lv.1 and upped the voltage to 1.34v. I'm now testing it with Prime95, FurMark and I've got CPU Temp open too but my CPU is getting readings of almost 90* which sounds very high to me. How long should I keep running Prime95 at these temperatures to ensure everything is stable??

Thanks,
Rookie

[GoNz0]

90 is to high, they are trying to get you to cook the CPU, its already due to throttle back, don't get to a situation where its just stable at the point of throttling back to then find out when the weather gets hotter it craps out.

they are clutching at straws after selling you a package not as described (it doesn't do what its meant to)

start the process to get a refund and buy your own kit, use the many guides on here to overclock it yourself and spend the change on better cooling!

[Rookie1986]

90 is to high, they are trying to get you to cook the CPU, its already due to throttle back, don't get to a situation where its just stable at the point of throttling back to then find out when the weather gets hotter it craps out.

they are clutching at straws after selling you a package not as described (it doesn't do what its meant to)

start the process to get a refund and buy your own kit, use the many guides on here to overclock it yourself and spend the change on better cooling!

Hey Gonzo,

What should my CPU be running at to be classed as normal? At the moment I've got both side panels off, my 200mm MegaFlow as an intake fan, A Corsair H100 Push/Pull with Corsair stock fans and SickleFlows and then a 120mm SickleFlow exhaust fan at the rear.

Well I've BSOD again anyway so it doesn't look like this has worked either.

Rookie

[GoNz0]

water cooled! about 20 degrees lower imo.