BSOD driving me potty!

Associate
Joined
20 Apr 2003
Posts
1,316
Location
Gloucestershire
Hi All,

I'm having major issues with a machine I built for my grandfather about a year ago. Ever since it was built it's been consistently blue screening, but I'm having no luck tracking down what the issue is.

Initially I thought it was a hardware issues, so I've tried different memory, motherboard, hard drive and even graphics, but it's still not stable. I've re-installed it so many times it's ridiculous. The only items I haven't swapped out hardware wise is the CPU and PSU.

Usually the BSOD is a system service exception error, but sometimes it's others.

I've got blue screen viewer installed on the machine so I can read the dump files easily etc, but other than typically it being ntoskrn.exe that it relates to I'm not making any other headway.

Please, please, please, can anyone suggest what I need to do next as this is the most problems I've ever had with a machine despite building many over the years and I'm very close to throwing the thing out the window.

Many thanks,

E-I
 
So, some details..

Motherboard: Gigabyte 880GM-UD2H
CPU: AMD Phenom 2 840
RAM: 8GB OCZ (4x2Gb) Also tested with Corsair XMS 3 (2x4Gb)
HD: Samsung spinpoint F3 (tested with other same model hard drive also)
GFX: using motherboard on board gfx
OS: Windows 7 64bit home premium

Last dump file text
==================================================
Dump File : 122812-23930-01.dmp
Crash Time : 28/12/2012 14:07:57
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`0352f458
Parameter 3 : fffff880`0352ecb0
Parameter 4 : fffff880`0122b999
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+5999
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122812-23930-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 271,912
==================================================

Best,

E-I
 
What PSU is it? Have you changed the SATA cable to the hard drive?

Have you stress tested the system with something like Prime95 blend? See if it causes a BSOD.
 
Thanks for reply speed.

Yes, have changed sata cable several times
PSU is BeQuiet pure power 530
I have stress tested, sometimes it appears rock solid, other times BSOD whilst idle in windows. Stressing it certainly isn't the cause as it actually seems more stable when under load.
 
I think the thing that is really making this weird is the inconsistency of the whole thing.

There's a variety of BSOD messages, usually system service exception (ntoskrn.exe) but also regularly NTFS_FILE_SYSTEM and a few others.

I've run memtest on the RAM and a couple of times have had memory errors, so I swapped out the memory and that passed memtest fine. However the original memory when tested on another machine tests fine. I also found that the machine was still unstable with the replacement memory (even though it passed memtest). Weirdly, putting the old memory back in then passed memtest with flying colours, stable for 12 hours or more without any error.

I've had it apparently rock solid stable at home (prime stable for 24 hours or more using setting that used all available memory), yet once back at my grandfathers it BSOD'ing again, despite him having done nothing more than just switched it on.

I'm beginning to wonder whether it could be a dodgy power supply where its giving some sort of voltage drop or something?

E-I
 
Last edited:
Back
Top Bottom