Page File Vista 64

e v o · Apr 27, 2008, 12:00 AM

Here's my issue. Recently I finished Crysis and had installed forceware 174.74. Everything was fine until I tried playing COD4 after. I got the infamous "display driver has stopped working". In COD4, it would pause, go to black screen, recover, play for a second and then do the same thing. The first time this happened i got a bluescreen. I read up on this problem, but saw there really wasn't a definite solution. I decided to try going back to 169.44, but encountered the same thing.

I finally read somewhere reducing the page file to 512-1024 instead of letting vista manage it would help. I tried it and viola, it's been fixed. My problem with this is I've played COD4 previously without touching the pagefile. This was a while ago, but I don't think I've made any drastic changes. My pagefile before changing it was around 4100mbs. I also noted that in COD4 when I tried letting vista manage the pagefile, I would get a "tear" in-game, similar to a v-sync tear, but much worse. When I set the pagefile back to 512-1024, it went away. The only changes I can think of that I've done are install Vista SP1 and *maybe* put in another 2 gigs of ram, but don't remember if I've been able to play COD4 with 4gbs.

Has anyone experienced this? I will continue to try things, but it's just kinda bothering me. Thanks for any advice or thoughts.

PangingJr · Apr 28, 2008, 12:11 PM

i used to often have the display driver has stopped working problems, but i didn't change the setting of the system paging file,
i found that occurs when the memory timing too tight and the RAM was running too fast, i think it's like a soft error occurs.
and i know exactly what i did wrong because that problem occured when i was configuring the memory timing.
but i guess yours is different.

MitchRapp · Apr 28, 2008, 03:43 PM

I'm guessing this is an nVidia video driver problem only right?
I don't seem to have any issues playing Crysis and COD4 back to back. My pagefile is set to 4096mb and on a different internal drive.

PangingJr · Apr 28, 2008, 04:30 PM

nope the display driver has stopped working... has also occured in system with ATi based card
i can't remember exactly what it said but it was similar to that, and then it would get a pause, go to black screen, recover, just like that.

however, i was able to fix mine easily, i usually changed my memory timing settings, or add some Vcore or sometime Vdimm.

e v o · Apr 28, 2008, 05:56 PM

thanks for the replies guys. I will try to see if it's something with my overclock.

PangingJr · Apr 28, 2008, 06:15 PM

and when the problem occurred i remember i could almost reproduce the problems, but it has to happen once, then after i changed some BIOS settings the problem stopped, and then changed back to previous settings and after running the system for awhile the problem would start again. i think i only saw this after SP1.

e v o · Apr 28, 2008, 10:22 PM

yeah, it seems sp1 has contributed to this. I'm going to fool around with the timings. etc

PangingJr · Apr 30, 2008, 04:58 AM

how's it going?

i don't recall i ever had a BSOD for this before.

IF you have ever gotten a BSOD, here (below) is the exact Stop error message...

"attempt to reset the display driver and recover from timeout failed"

try a Google search for that, it seems to me there are a number of solution to this problem,
and i now think the SP1 may has nothing to do with this problem.

e v o · Apr 30, 2008, 09:22 PM

The time i got a BSOD was when the loading screen would get interrupted, I had left it, without trying to press esc and eventually it led to a BSOD. My experience is you can avoid the BSOD by pressing escape, etc. I'm still in the process of fooling around with variables. I really hope it's not a dying video card as I just bought this and it would be a pain to take it out of the water cooling loop.
I added a little more vcore, fooled around with timings, disabled overclocking on my vid card, but I haven't gotten a chance to test in COD4 really. I'll try to do so tonight.

edit: Well I was able to finish COD4 without another interruption, so hopefully this problem is solved for me. I adjusted ram timings and added a bit more vcore (my board has serious v-droop). On a somewhat related note, COD4 was one of the best 1st person shooters I've ever played, wow.

PangingJr · May 21, 2008, 01:38 PM

how's it going?

Apr 27, 2008, 12:00 AM	#1
e v o ........ Join Date: Dec 2004 Posts: 1,038 Rep Power: 33 System Specs	Page File Vista 64 Here's my issue. Recently I finished Crysis and had installed forceware 174.74. Everything was fine until I tried playing COD4 after. I got the infamous "display driver has stopped working". In COD4, it would pause, go to black screen, recover, play for a second and then do the same thing. The first time this happened i got a bluescreen. I read up on this problem, but saw there really wasn't a definite solution. I decided to try going back to 169.44, but encountered the same thing. I finally read somewhere reducing the page file to 512-1024 instead of letting vista manage it would help. I tried it and viola, it's been fixed. My problem with this is I've played COD4 previously without touching the pagefile. This was a while ago, but I don't think I've made any drastic changes. My pagefile before changing it was around 4100mbs. I also noted that in COD4 when I tried letting vista manage the pagefile, I would get a "tear" in-game, similar to a v-sync tear, but much worse. When I set the pagefile back to 512-1024, it went away. The only changes I can think of that I've done are install Vista SP1 and maybe put in another 2 gigs of ram, but don't remember if I've been able to play COD4 with 4gbs. Has anyone experienced this? I will continue to try things, but it's just kinda bothering me. Thanks for any advice or thoughts. __________________

Apr 28, 2008, 05:56 PM	#5
e v o ........ Join Date: Dec 2004 Posts: 1,038 Rep Power: 33 System Specs	thanks for the replies guys. I will try to see if it's something with my overclock. __________________

Apr 28, 2008, 10:22 PM	#7
e v o ........ Join Date: Dec 2004 Posts: 1,038 Rep Power: 33 System Specs	yeah, it seems sp1 has contributed to this. I'm going to fool around with the timings. etc __________________

Apr 30, 2008, 09:22 PM	#9
e v o ........ Join Date: Dec 2004 Posts: 1,038 Rep Power: 33 System Specs	The time i got a BSOD was when the loading screen would get interrupted, I had left it, without trying to press esc and eventually it led to a BSOD. My experience is you can avoid the BSOD by pressing escape, etc. I'm still in the process of fooling around with variables. I really hope it's not a dying video card as I just bought this and it would be a pain to take it out of the water cooling loop. I added a little more vcore, fooled around with timings, disabled overclocking on my vid card, but I haven't gotten a chance to test in COD4 really. I'll try to do so tonight. edit: Well I was able to finish COD4 without another interruption, so hopefully this problem is solved for me. I adjusted ram timings and added a bit more vcore (my board has serious v-droop). On a somewhat related note, COD4 was one of the best 1st person shooters I've ever played, wow. __________________ Last edited by e v o; May 1, 2008 at 11:35 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Windows Vista SP1 RC1 Public	Vikingod	Windows Vista Forum	28	Jan 31, 2008 05:47 AM
Ati/AMD Catalyst 7.12 Drivers for Vista rate them and discuss them here!	temeteus82	Windows 7 & Vista Radeon Display Drivers	22	Jan 11, 2008 06:19 AM
Is a Page File Neccesary?	Raptor	Windows XP / 2000 / NT / 9x Forum	30	Feb 6, 2005 05:56 PM
need help with paged file?	Nforce2XP	Benching	11	Jan 29, 2005 12:09 PM
WinXP page file	Spdklls 2.0	Windows XP / 2000 / NT / 9x Forum	2	May 12, 2002 08:05 PM

Apr 28, 2008, 12:11 PM	#2
PangingJr Member Join Date: Mar 2003 Posts: 5,989 Rep Power: 55	i used to often have the display driver has stopped working problems, but i didn't change the setting of the system paging file, i found that occurs when the memory timing too tight and the RAM was running too fast, i think it's like a soft error occurs. and i know exactly what i did wrong because that problem occured when i was configuring the memory timing. but i guess yours is different.

Apr 28, 2008, 03:43 PM	#3
MitchRapp a.k.a. pepiman Join Date: Dec 2004 Location: Montreal Posts: 905 Rep Power: 35 System Specs	I'm guessing this is an nVidia video driver problem only right? I don't seem to have any issues playing Crysis and COD4 back to back. My pagefile is set to 4096mb and on a different internal drive.

Apr 28, 2008, 04:30 PM	#4
PangingJr Member Join Date: Mar 2003 Posts: 5,989 Rep Power: 55	nope the display driver has stopped working... has also occured in system with ATi based card i can't remember exactly what it said but it was similar to that, and then it would get a pause, go to black screen, recover, just like that. however, i was able to fix mine easily, i usually changed my memory timing settings, or add some Vcore or sometime Vdimm.

Apr 28, 2008, 06:15 PM	#6
PangingJr Member Join Date: Mar 2003 Posts: 5,989 Rep Power: 55	and when the problem occurred i remember i could almost reproduce the problems, but it has to happen once, then after i changed some BIOS settings the problem stopped, and then changed back to previous settings and after running the system for awhile the problem would start again. i think i only saw this after SP1.

Apr 30, 2008, 04:58 AM	#8
PangingJr Member Join Date: Mar 2003 Posts: 5,989 Rep Power: 55	how's it going? i don't recall i ever had a BSOD for this before. IF you have ever gotten a BSOD, here (below) is the exact Stop error message... "attempt to reset the display driver and recover from timeout failed" try a Google search for that, it seems to me there are a number of solution to this problem, and i now think the SP1 may has nothing to do with this problem.

May 21, 2008, 01:38 PM	#10
PangingJr Member Join Date: Mar 2003 Posts: 5,989 Rep Power: 55	how's it going?