BSOD on new build

Personally wouldn't touch the OCing options in AI Suite. It did funny things to my system, and sent my cpu temps very high too.
Restore to stock speeds and uninstall it- you can overclock manually through the BIOS.

Might be worth a windows repair install too.

Whenever I tried it in AI Suite, my system blue screened. Worked fine it bios...
 
so should i try uninstalling the AI suite,, i havent used it to overclock, ive spent the last 2 days following the ocz set up guide,

again today whent throu the set up and reinstalled every thing BUT got it again, and yes i have the AI installed

windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17127448576 total
VM: 2147352576, free: 1945542656



Crash Dump Analysis


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 25/06/2012 17:50:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-14040-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8012CADB30, 0xFFFFFA8012CADE10, 0xFFFFF800039C5240)
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.


On Mon 25/06/2012 17:50:30 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, 0xFFFFFA8012CADB30, 0xFFFFFA8012CADE10, 0xFFFFF800039C5240)
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 following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\062512-13525-01.dmp




it it only me having this issue ?
 
Last edited:
Back
Top Bottom