New system BSOD in games

Monotone · 10 Jan 2011 at 21:55

Hi all just build a cheap system for myself today from overclockers.

Which was basically the Titan nero

http://www.overclockers.co.uk/showproduct.php?prodid=FS-259-OK

but with this processor,

http://www.overclockers.co.uk/showproduct.php?prodid=CP-259-AM&groupid=701&catid=6&subcat=803

this PSU,

http://www.overclockers.co.uk/showproduct.php?prodid=CA-201-CM&groupid=701&catid=123&subcat=

and this gfx card,

http://www.overclockers.co.uk/showproduct.php?prodid=GX-238-AS&groupid=701&catid=1914&subcat=1830

It installed windows 7 x64 fine and runs find in terms of normal desktop usage but when i play any game after about 10-15 mins I get a BSOD with a an error like this one:

Code:

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7600.2.0.0.256.1
  Locale ID:	2057

Additional information about the problem:
  BCCode:	fc
  BCP1:	FFFFF8A009B08000
  BCP2:	83B000005D9B4963
  BCP3:	FFFFF8800D7DD910
  BCP4:	0000000000000002
  OS Version:	6_1_7600
  Service Pack:	0_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\011011-23556-01.dmp
  C:\Users\Mat\AppData\Local\Temp\WER-28969-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I have uninstalled all the drivers that came on the cds and replaced them with newer version where needed and the problem is the same. Any ideas?

Mat.

RJC · 10 Jan 2011 at 21:58

Could be a problem with the ram, could try downloading mem test and run this from a bootable disc.

Monotone · 10 Jan 2011 at 22:03

Thanks RJC i'll give that a whirl while i'm eating my dinner!

*edit* Tested the Mem and no errors, I have a suspicion that it may be gfx card drivers?

*edit* Seems that TCPIP.sys is the problem thats what pops up on all the BSODs. Not sure what to do with that since I have already reinstalled the drivers for it.

Monotone · 12 Jan 2011 at 23:32

Sorry for the double post but this is driving me mad now!

This happens only when in game, I left the system on all night downloading from steam and it was fine in the morning. Played TF2 last night for around 3 hours and not a single hitch.

Now it's giving me messages about

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 24
BCP1: 001904FB
BCP2: A5DC5628
BCP3: A5DC5200
BCP4: 8304F560
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\011211-18610-01.dmp
C:\Windows\Temp\WER-23041-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Seem that the 24 code is for NFTS?

Ran sfc.exe to see if it was windows files that was causing it and that came back 100% correct and no errors.

Any ideas?

MuttsNutts · 13 Jan 2011 at 02:12

Download a program called "Blue Screen View" its freeware you load the minidump file into it and it points you to what driver file has caused the issue etc also can point to hardware aswell..... not a clear cut diagnosis but points you in thr right direction.

:-)

Monotone · 13 Jan 2011 at 02:37

Thanks I'll have a look through the vast BSOD's!

*edit* Only found two I think I deleted temp files while troubleshooting direct x install.

But both point towards ntkrnlpa.exe, and then Ntfs.sys/halmacpi.dll. From what I have looked at this could mean a bad install?

This is the second time I have installed now since monday?

Could bad ram corrupt an install?

I ran a small Memtest, but I don't trust it's findings. It said 100% it was ok.

Can't get my head around this, it's killing watching 15-30 mins of amazing graphics—compared to my old 7900gs and amd dual core—for it
to die on me, really need to get it up and running for next week too for uni!

Here are the exact specs of the build just to check I haven't overlooked anything and made a boob right at the start:

- Case: Xigmatek Asgard - Black
- Power Supply: Cooler Master GX 550W Power Supply
- CPU: AMD Athlon II X4 Quad Core 630 2.80GHz (Socket AM3)
- Motherboard: Gigabyte GA-880GM-UD2H 880G (Socket AM3) DDR3 Motherboard
- RAM: OCZ Gold Low Voltage 4GB (2x2GB) DDR3 PC3-10666C9 1333MHz Dual Channel
- Hard Drive: Seagate 500GB SATA-II 16MB Cache
- Graphics Card: Asus GeForce GTX 460 Direct CU TOP 768MB GDDR5

Thanks.

Monotone · 13 Jan 2011 at 18:28

Right I seem to have this one down now, faulty ram stick! It seems to be fine with just this one stick in, I have tried sawpping slots and sticks around. With the suspect stick in on its on, games etc only get to the menus before BSOD'ing on me.

I'm ok at software troubleshooting but hardware is not me, is there any reason why it wouldn't be my stick of suspect ram before, I go down the RMA route?

At least I can now see the benifits of my purchase, 2gb down, but better than nothing!

Mat.

MuttsNutts · 18 Jan 2011 at 14:00

Sorry for very late reply, but looks like your bang on with the failed stick of RAM......
when RAM is faulty you normally get a random amount of BSOD due to what process or driver is using that tiny part within the faulty stick so that;s why you can get different BSOD each time.....

If the stick is faulty near the front end of it's memory addressing this means it's already loaded and using the faulty part of it when Windows loads..... so this is a ticking timebomb untill it decides when to DUMP...... this this case it's normally when you push it with heavy load (Like when running s game).....
the latter seems to what you have.....
I bet if you run some memory Diags it will fail the stick within a few seconds of it being tested.