BSOD - games, idle pc

Hey guys. First of all I would like to say hello to everybody. I really hope that you can point my at what's wrong with my new pc, because it drives me insane. That's my first post, I hope I explain my issues so that you can help me out.

So, let's roll.

My PC specs:
AMD X4 640 cpu
ASUS M4N68T-M LE V2 motherboard
2x2048 DDRIII EXCELRAM ram
500GB SATA-2 SEGATE hdd
Windows 7 ultimate x86 (previously x64)

My main problem is that after about 5-20 minutes (varies) of playing COD: Black Ops or Mafia 2 my computer gets a mem-dump BSOD and restets or crashes to desktop. This happens on both x86 and x64 win7 ultimate. What's worse about x86 is that I get the BSOD's even when I am not playing games. I got one today on a FRESH WINDOWS, when windows update was installing some stuff. After that happened, I formatted my hdd and installed x86 once again,only to get same symptoms with games and pc crashing while using Opera or just being idle.
My gpu temp doesn't get higher than 65C, cpu also stays cool. I ran memtest86 and it has shown no errors whatsoever.
The only thing that alerts me is the fact, that my monitor image gets blurry from time to time, as if the refresh rate ha changed from 75hz back to 60hz, but nvidia driver and windows shows, that nothing has changed. After changing the refresh rate back and forth it goes back to normal.

It really sucks, because I was haunted by the nv4.dll BSOD on x86 xp pro and now I get this mess. Please, help me out!

I attach the zipped folder that this software you recommended createt from reading my pc's logs. I hope it will let you help me.

Hi,

Inconclusive bugchecks - looks like a hardware problem to me, probably graphics related.

Run this stress test: Video Card - Stress Test with Furmark

What PSU do you have? A GTS450 uses a lot of power and an underpowered PSU may be the problem here.

Also, two drivers that you need to take care of:

Code:

ASACPI.sys   Fri Aug 13 14:52:52 2004 (411C2D04)
sptd.sys     Mon Oct 12 09:54:02 2009 (4AD245EA)

ASACPI.sys - ASUS ACPI Driver; the 2004/2005 version is almost guaranteed to cause BSODs on Windows 7 systems. Update link here, update instructions (slideshow) here (note that in the last step you select the ATK0110 driver in the list instead of the one mentioned)

SPTD.sys is known to cause BSODs; remove Daemon Tools, then use this SPTD installer to remove it (pick the uninstall option when you run the installer): DuplexSecure - Downloads

Regards,
Reventon

BUGCHECK SUMMARY

Code:

Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 08:46:55.218 2010 (GMT+13)
System Uptime: 0 days 0:23:26.841
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
BUGCHECK_STR:  0x7f_d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000007F
Arguments 0000000d 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 07:52:41.310 2010 (GMT+13)
System Uptime: 0 days 0:55:09.559
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 00000019
Arguments 00000020 a5ea3d78 a5ea3d88 0a020403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 01:48:23.772 2010 (GMT+13)
System Uptime: 0 days 0:21:04.022
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments c0000005 82c7cf2c 8df73c44 8df73820
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Wow, thanks for a really fast answer!

I took care of these two drivers you mentioned, but it didn't work out - COD crashed on me after 19 minutes of playing. BSOD with memory dump. I attach here the dmp file ad this software generated zip created after this crash, can you read anything out of it?

PS - if PSU means power supply (I am not English, so I don't understand all of this jargon :)) then it's 550 watt, dunno about the manufacturer. It should be enough, shouldn't it?

Hi,

Those drivers have been taken care of, so now we have to look at the hardware possibilities.

Stress tests to run:

Video Card - Stress Test with Furmark

RAM - Test with Memtest86+

https://www.sevenforums.com/tutorials...t-prime95.html (run the Blend test as well as the Small FFT test)

EooN said:

PS - if PSU means power supply (I am not English, so I don't understand all of this jargon :)) then it's 550 watt, dunno about the manufacturer. It should be enough, shouldn't it?

Yes, it means Power Supply. While 550W is technically enough, you find that low quality power supplies often get nowhere near their rated output. Consider replacing it with a good quality Corsair/Seasonic unit such as this one - Newegg.com - CORSAIR CMPSU-650TX 650W ATX12V / EPS12V SLI Ready CrossFire Ready 80 PLUS Certified Active PFC Compatible with Core i7 Power Supply

Regards...

BUGCHECK SUMMARY

Code:

Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 13:05:21.486 2010 (GMT+13)
System Uptime: 0 days 0:20:45.109
Probably caused by : ntkrpamp.exe ( nt!ObpCloseHandleTableEntry+28 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  BlackOps.exe
Bugcheck code 1000008E
Arguments c0000005 82e4c613 a0e68c2c 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Hi,
today I didn't have much time to test my pc. I managed to play COD for 27 minutes straight, and then it crashed but without BSOD, just game's own "fatal error". I also ran the Furmark for 40 minutes or so, the tem reached 75C max and stayed there. Throught the banchmark screen was getting blurry (especially text) and crisp again, so I am leaning towards the theory of damaged GPU.

Run the other tests before deciding to replace the graphics card. It may turn out that something else is at fault.