BSOD on new build

Associate
Joined
11 Jun 2012
Posts
46
Location
Warminster, Nr Bath
Hi

Built a new system all was ok, however im now getting BSOD. not all the time but 5 time since the 13th

system just freezes and restarts.

all drivers are up to date even the ssd firmwear
tryed the windows repair,

used bluescreenview

http://s385.photobucket.com/albums/oo292/trackpad72/?action=view&current=Untitled5.jpg
0x000000f4 00000000`00000003 driver.ntoskrnl.exe 17/06/12

http://s385.photobucket.com/albums/oo292/trackpad72/?action=view&current=Untitled4.jpg
0x000000f4 00000000`00000003 driver.ntoskrnl.exe 17/06/12

http://s385.photobucket.com/albums/oo292/trackpad72/?action=view&current=Untitled3.jpg
0x0000007a fffff6fc`40060b60 driver.ntoskrnl.exe 17/06/12

http://s385.photobucket.com/albums/oo292/trackpad72/?action=view&current=Untitled2.jpg
0x1000007e ffffffff`c0000006 driver.ntoskrnl.exe 16/06/12

http://s385.photobucket.com/albums/oo292/trackpad72/?action=view&current=Untitled1.jpg
0x000000f4 00000000`00000003 driver.ntoskrnl.exe 13/06/12

it has also done it a few other times without loging anything

specs are
ssd OCZ Agility 3 240g
16gb ram
i5 3570K ivy
750 psu
2 x GTX 560ti oc twin fozzer
 
Last edited:
I've also stumbled across this 0x000000f4 crash code whilst installing windows 7 on a 60GB OCZ Agility 3 SSD! Updated firmware from 2.15 to 2.22 and touch wood! so far so good.
 
I have run memtest, and sea tools all with passes,

the ssd if on firmare 2.22

i did the sfc/scannow and i came back with ..did not find any integrity violations
 
Last edited:
no i haven't, but i dont under stand wot that would be testing ?? with them error codes

Have a look at this Tweak guide http://www.overclock.net/t/1156654/seans-windows-7-install-optimization-guide-for-ssds-hdds check to see if there is anything in there that may help you out, Tweaks ect! and a good installation guide. I've come across this same error as you and it's only happened since I installed the Agillity 3 SSD. If I see it again I will investigate it further.
 
no i haven't, but i dont under stand wot that would be testing ?? with them error codes

couple of reasons

ran a quick check on ntoskrnl.exe and part of what it does relates to memory management (amongst other things), so reducing the memory in the system and reducing the graphics card memory available, will give the give it less to do.

things like this are a matter of elimination, you don't need 2 gfx cards and all the memory to run/test the system.

thinking about it you could remove both graphics cards and use the onboard graphics.

what sort of temps are processor and graphics cards running at ?
 
ok might have found the problem.

The hotswap sata power connection has disintegrated exposing the pins and leaving the sata cable lose, just touching the pins , will have to bypass the pannel and connect the drives individually and see if that sorts it,
 
well thought it was sorted but just got it again :-(

BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8013DE6B30
BCP3: FFFFFA8013DE6E10
BCP4: FFFFF80002BD8510
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
 
thanks , it came back with this

On Thu 21/06/2012 11:25:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062112-11840-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8013DE6B30, 0xFFFFFA8013DE6E10, 0xFFFFF80002BD8510)
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.
 
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.
 
Back
Top Bottom