ntoskrnl.exe BSOD

Which version of the P6T board do you have? I had a P6T Deluxe v1 and had to upgrade to v2 in order to stop my BSOD's when I hibernated.

The first thing to do is to reset the system to factory defaults (no overclock). This will tell us if it's due to the overclock or not. The memory dumps show default as 2.67 gHz and current as 3.1 gHz.

Beyond that there's no specific cause to suspect here. The BSOD's blame memory corruption - which can be due to the overclock or to faulty drivers. Let us know if resetting the system to default fixes things. If not, then start with these free diagnostics:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080111-28844-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Aug  1 02:01:36.662 2011 (UTC - 4:00)
System Uptime: 0 days 10:23:04.630
Probably caused by : memory_corruption ( nt!MiTrimWorkingSet+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  CCC.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiTrimWorkingSet+c0
Bugcheck code 00000050
Arguments fffff683`fb7ca888 00000000`00000000 fffff800`02f50bc0 00000000`00000002
BiosVersion = 0904   
BiosReleaseDate = 11/12/2009
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 3100
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-24414-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 14:30:19.632 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:01.600
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
Bugcheck code 00000050
Arguments fffff683`fb7f46b8 00000000`00000000 fffff800`02e8231b 00000000`00000002
BiosVersion = 0904   
BiosReleaseDate = 11/12/2009
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 3100
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

You'll have to either contact Cyberpower or make notes about the settings on your system if you want to regain the overclock in the future. In most cases (with Asus boards) you can reset the BIOS to default/fail safe values and that will stop the overclock. Until then we'll try and work around the overclock (because it'd be a shame to remove the overclock and not be able to get it back correctly) - I haven't done any overclocking in almost 10 years!

BSOD troubleshooting is ½ scientific and ½ guesswork. So we fix things and then we wait to see if the BSOD comes back. In most cases going a week without a BSOD means we've probably fixed it. Going 2 weeks means that we've most likely fixed it. There's just no guarantee's here :0)

The BSOD itself doesn't harm the system. But if there's a hardware cause for it, then that may harm the system.

There are several ways to test drivers. We, at times, use Driver Verifier (with certain specific settings). Or we remove the drivers to see if the BSOD goes away (most BSOD's are caused by problems with 3rd party drivers).

So, while waiting for the overclock to be reset, let's proceed with the diagnostics. If they come back OK, then we'll try some free stress tests (but I'd prefer to do them without the overclock working). If we have to, we can do them with it - but that'll be testing both the overclock and the hardware.