New
#1
BSOD pointing to ntoskrnl.exe - Major Slow boot up now!!
Hi All,
I have a new build which has been running flawlessly for the past 3 month, no errors of any kind, extremely fast boot times and shutdowns, a pleasure to use.
The other day though I experienced a BSOD (surprised and disappointed) and ran Whocrashed and got the following error details: (please ignore the dates in bold, my system clock was set to those date on purpose)
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 18/09/2009 11:22:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091909-29312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009191B30, 0xFFFFFA8009191E10, 0xFFFFF80002F8A2D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
On Fri 18/09/2009 11:22:32 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009191B30, 0xFFFFFA8009191E10, 0xFFFFF80002F8A2D0)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
This BSOD has only happened twice now in past 2 days, but this has caused my Boot times to become quite long. Normally i was logged into Windows 7 within about 40sec from start to finish. Now it is taking between 90sec - 120sec.
However once inside Windows 7, everything appears to be working smoothly. The only time the BSOD happened was on boot up.
My problem now is trying to figure out if it is just a corrupt ntoskrnl.exe file and/or ntkrnlmp.exe file and what the best approach would be to fix this.
Though after checking my system, those 2 files do exist but are not in the C:\Windows\system32\ folder. Are they suppose to reside in there????
If so, (1) would using the Windows 7 install disc to copy them over fix this??
Or (2) should I be trying a "System Repair" ??
I really do not want to do a fresh install if I can avoid it.
The only possible cause I can think of that I have done in the past couple of days that may have screwed something was that in preparation for some overclocking (I am still running my system Stock) I ran a stress test using AIDA64 on stock clocks for 5 hours, which passed without a hitch. System was fine until I logged off and noticed the BSOD and slow boot time the next time I used my computer.
My Specs are:
ASUS P8P67 PRO (M/B), Intel i5-2500K (CPU), 8GB G.Skill RAM, 1TB Samsung f4 Spinpoint drive, Corsair HX850 PSU.
Much thanks
M88