Recent Crashing Problem.

[Xonim]

Still haven't seen an attempt at furmark with onboard graphics. You know the GPU crashes during furmark. See if onboard does.

If it doesn't lock with onboard, that would point to something with your GPU.

 

[james7679]

It would really help if you uploaded the extracted .dmp files. You can use whocrashed or bluescreenviewer to do so. It would really help to know the full stack ref. But;
You know what? I think you are still overclocking. Not necessarily your fault though.

First, update all of your system drivers. Then, update your BIOS.
After updating your BIOS set the system to run at failsafe settings. Stress it again and watch temps/volts.

But please, before you do that, extract your .dmp files and upload the content.

 

[Slugbait]

... What am I missing?

VRAM test result?

 

[MBrown]

It would really help if you uploaded the extracted .dmp files. You can use whocrashed or bluescreenviewer to do so. It would really help to know the full stack ref. But;
You know what? I think you are still overclocking. Not necessarily your fault though.

First, update all of your system drivers. Then, update your BIOS.
After updating your BIOS set the system to run at failsafe settings. Stress it again and watch temps/volts.

But please, before you do that, extract your .dmp files and upload the content.

Here is my crash dumps And it turns out you are right. Even after I flashed by bios removed the battery and updated my bios I cannot remove my overclock at put it back to stock settings unless I turn the tpu switch off so right off the bat that seems to be a issue right there. Any way I turned the tpu switch off and my CPU STILL will not run at 3.3GHz which is its stock speed it stays at around 3.6 or 3.5 GHz. Anyway I have my GPU removed and I'm using oboard video I will run furmark when I have some time.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 11/30/2012 9:00:39 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF80002E199B0) 
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E199B0, 0xFFFFF80002E199B0, 0xFFFFF82002E199B0)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. 
A third party driver was identified as the probable root cause of this system error. 
Google query: BAD_POOL_HEADER



On Fri 11/30/2012 6:34:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\113012-7176-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007D18028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
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 hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
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 that cannot be identified at this time. 



On Thu 11/29/2012 1:45:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112912-7004-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007C27028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
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 hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
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 that cannot be identified at this time. 



On Thu 11/29/2012 12:46:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112812-7020-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007E5A028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
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 hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
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 that cannot be identified at this time. 



On Thu 11/29/2012 12:40:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112812-6988-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007E0D028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
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 hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
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 that cannot be identified at this time. 



On Wed 11/28/2012 3:26:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112812-9578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0xD1 (0xFFFFF84002C7EA32, 0x2, 0x8, 0xFFFFF84002C7EA32)
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 that cannot be identified at this time. 



On Wed 11/28/2012 3:22:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112812-7425-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0x50 (0xFFFFF920C06B78B0, 0x0, 0xFFFFF80002E0C608, 0x5)
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 that cannot be identified at this time. 



On Wed 11/28/2012 3:14:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112812-7659-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C60) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CC3C60, 0xFFFFF880031A0F68, 0xFFFFF880031A07C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 that cannot be identified at this time.

 

[james7679]

Yeah, you didn't mention the x124 bug checks. What kind of PSU do you have? Did you check your min and max voltages using hwmonitor? It's possible that you have a bad psu, but I still think that these crashes and issues are a result of overclocking. If you can't get your 2500k to run at stock specs, then you should look into RMAing the board.

 

[coffeejunkee]

It's called Asus Multicore Enhancement in the uefi and it makes all cpu cores run at the single core highest turbo bin. Disable it to get the official turbo behaviour back.

I'd be surprised if that's the cause of your crashes though. Asus decided it wouldn't cause problems for any SB/IVB cpu to run all cores at max turbo speed so they enabled it by default.

 

[MBrown]

Yeah, you didn't mention the x124 bug checks. What kind of PSU do you have? Did you check your min and max voltages using hwmonitor? It's possible that you have a bad psu, but I still think that these crashes and issues are a result of overclocking. If you can't get your 2500k to run at stock specs, then you should look into RMAing the board.

Corsair tx650. Its a few years old now.

 

[MBrown]

It's called Asus Multicore Enhancement in the uefi and it makes all cpu cores run at the single core highest turbo bin. Disable it to get the official turbo behaviour back.

I'd be surprised if that's the cause of your crashes though. Asus decided it wouldn't cause problems for any SB/IVB cpu to run all cores at max turbo speed so they enabled it by default.

I've never seen this in the Bios. I looked it up and it is tied with the XMP feature. If you turn it on, that feature is on, if you have it off, that feature is off. I do not have XMP enabled.

 

[coffeejunkee]

I have the P8Z77-M Pro board and that option is visible to me with xmp enabled or not. So might have been changed with the newer chipset.

But visible or not, it appears to be working anyway. And maybe try using the xmp profile, should be the correct timings.

 

[MBrown]

Furmark with not work with my onboard graphics. It says it requires an open gl 2.0 compliant graphics card.

 

[james7679]

Do you have another gpu you could test with?
Your psu should be fine. Min max voltages?

 

[MBrown]

Do you have another gpu you could test with?
Your psu should be fine. Min max voltages?

I do not unfortunately. Should I be looking my min max voltages with my GPU in while gaming?

Edit: I can't even see the PSU voltages in HW monitor.

 

[james7679]

There are two versions of HWMonitor. I, honestly, can't remember which you need. When I get home I will look and upload a screen from the voltages.

 

[MBrown]

There are two versions of HWMonitor. I, honestly, can't remember which you need. When I get home I will look and upload a screen from the voltages.

The asus desktop software has a voltage monitor. I ran a furmark test with nothing overclocked for real this time, with my 6950 and voltages stayed at around 12v and 5v. Also ran p95 on blend with nothing overclocked for 5.5 hours and no errors.

 

[james7679]

So, you were able to get your cpu and ram to stock specs? Maybe try deleting, with REVO uninstaller at an advances level all of your asus software. Its possible that you are softclocking(overclocking within the os using software, this should NEVER be done). If not, I recommend starting a thread in the mobo section, linking this thread, and asking for help to manually set up your cpu and ram to stock and see if you're still crashing.

If you still can't find stability, then you need to rma the mobo.