Game trouble

[Dorkenstein]

I know there are numerous threads regarding similar problems already but I have some questions regardless. Since putting in new memory, graphics and power supply things went fine for a week or three but now for some reason I am getting hanging in games and demos, getting booted out of them and today I got a blue screen error. I keep immaculate care of windows (so I think) and I don't really believe it to be 'windows rot' setting in. I gathered from other posts that this is usually a driver issue. In my case, the only new component that needs drivers is my graphics card and that uses Detonator 61.77, which happens to be the current driver release. I considered rolling it back to a more stable release if others have the same problem but for now I guess I just don't know. I will post a screenshot or dump of it when it happens again. Thanks for your time and help.

 

[Theslowone]

If you give more info about your system, then better responses may come forth.

How much ram do you have, what games,graphics card, brand and wattage of psu, video card model, etc.


and what windows?

 

[Dorkenstein]

Barton 2500+ oc'ed to 3200
Soltek SL-FRN2-L
1 gb of Buffalo memory
Winfast A250 6800 GT
Hercules Muse XL sound card
Hitachi 120 gb hard drive

 

[Sideswipe001]

Of course the first suggestion has to be...

Have you clocked your system back to stock speeds? Do you still get the errors if you do?

 

[Dorkenstein]

All I did was raise the FSB to 200, which I had to do anyway for my new memory. That automatically made my cpu recognized as a 3200+.

Oh and here's another thing, when I rebooted from the BSOD, spybot warned me that a registry key had been deleted and did I want to allow or deny this action. Weird, I hope I don't have to reformat.

 

[Theslowone]

you don't have to raise your fsb for your memory, I would try to run it at stock speeds before formatting.

 

[Dorkenstein]

So you don't think it's a driver issue? I thought that was the common cause of BSODS. Also could it be caused by the page file being too small?

 

[neovan]

just set your fsb back to 166 and run those programs again to see if you encounter the same problem.

 

[Nothinman]

Also could it be caused by the page file being too small?

Generally if that's the case you'll get a "Running Low on Virtual Memory" dialog around the time the process is killed, but if you've done something like set the pagefile to static values stop that. Put it back to system managed and see if that helps, probably won't in this case but it's the 'right' setting and you can move onto figuring out what the real problem is.