RANDOM BOSD FNW 1.1.1.271

ok.. i have read and i saw that graphic cards lie ATI & Nvidia maybe its better if you all read this
http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx

so i went to look
registry key: HKLM\System\CurrentControlSet\Control\GraphicsDrivers\
TdrDelay: REG_DWORD
but saddly there is no TdrDelay: REG_DWORD in windows 7 registry at least not on my system.. so i look further and saw this post:
http://wiki.accelereyes.com/wiki/index.php/MTIMES_Benchmarks_(Jacket_1.4)
and on the end of this webpage in TIMEOUT section there is a small utility wich supposedly incise a timeout before GPU hangs.
I downloaded it and added to registry but with no luck :(. well i think that the game did survive a few minutes longer but BOSD at the end again :(

**the strange thing is that after i added specifiy registry i couldnt find TdrDelay: REG_DWORD in regedit so i dont know if utility actualy works. now i think i will restore my system a little bit and try to manualy add the line as suggested.
 
@ mobucks

i just tryed the TDR fix that you found on forums.. well i didnt manualy added the registry line as suggested here
Ok, the trick is:

1) open your vista registry editor

2) go to the key : HKLM\System\CurrentControlSet\Control\GraphicsDrivers\

3) highlight it then right click on this key

4) Add DWORD TdrDelay

5) Set value of TdrDelay to the number of seconds you allow your GPU to run with no feedback to the system (ie Timeout watchdog..)

personally I've set this value to 8 seconds (from the default 2s) so that it leaves plenty of time to the GPU to perform overcomplicated computing intensive kernel without having Vista considering a fault and hence "recovering the device"

That all folks, and should help some of you experiencing computer hung ups, or blue screens under vista.

i did more research and found this page
http://wiki.accelereyes.com/wiki/index.php/MTIMES_Benchmarks_(Jacket_1.4)
and on the end of it there is a small TDR utility wich do the same and i setted it to 20 sec... the game DID CRASH with BOSD but i think that it lasted a little bit longer
 
for some unknown reason the forum wont let me respond to the TDR settings and it keeps blocking my posts ... anyway

@ Mobucks i did try the TDR thing but no sucess and i setted the value to 20 and notthing :( but i do it using a utility that i found on one wiki web page here is what it says
If you are on Windows Vista or Windows 7 and get a timeout error, you may try modifying the TDR delay. The TDR delay is the time Windows waits for the GPU to finish whatever it's thinking about. After this time expires, the GPU driver gets reset. The default value is actually 2 seconds for a fresh install of Windows. The Jacket installer asks to increase this to 7. The original purpose of the TDR reset is to keep the desktop responsive, so the only negative side effect of increasing the timeout value is just to wait longer for the GPU control to return to the OS.
Here are some easy registry files to change the timeout value:
TDR_Fix zip file
Windows 7 / Vista only
7 seconds is the Jacket default
To Use: Just double-click the tdr_fix_20.reg file (inside the .zip) to increase the timeout delay to 20 seconds.

now i will do system restore and try to do all manualy
 
You are definitely possessing an overheating GPU. I would take the typical procedures of using compressed air to blast out the dust from the insides of your computer and from its fans, especially the GPU's fans.

Regarding the TDR fix check this out:

http://www.overclockers.com/forums/showthread.php?t=606750

Some guy's GTX 285 was doing something similar and posted his fix above. Change the values for clock speed according to your GPU of course.
 
You are definitely possessing an overheating GPU. I would take the typical procedures of using compressed air to blast out the dust from the insides of your computer and from its fans, especially the GPU's fans.

Regarding the TDR fix check this out:

http://www.overclockers.com/forums/showthread.php?t=606750

Some guy's GTX 285 was doing something similar and posted his fix above. Change the values for clock speed according to your GPU of course.

I GOT IT!!!!!!! I GOT IT!!!!!! :clap:

at least for tonight.. its now 1:18 A.M. and i played since 21:00 without any crash or damn BOSD .. NOTTHING..and i dont know what exactly i did but here is all what i did.

1.i did a clean i install of newest nvidia drivers (used a driver cleaner pro in safe mode)
2. i took out my graphic card completely unscew the fan.. it was all good and i couldn't separate a passive fan from the GPU so i said to my self , dont be stupid there is nothing wrong with your card (the guy from the hardware store today told me that maybe just maybe the passive fan has separated a little bit from the GPU and its not cooling enough.. anyway .. i put basic all screws and return the card .. close it.
3. i took that TDR fix, the same one that didnt worked this afternoon with value of 20 and i execute the 60 version
4. i took that famos DLL fix that never worked and i copyed it to FNW folder
5. i run up the game and left all as it was detected by FIX and just turn off vertical sync.

AND THE GAME WORKS!!!!!!!! .. HHAHAHAHAHAHAHAH ... SO it was not overheating!!!!!!! or at least i dont think it was... duno to tell you people the truth.. im cleaning the Primm village :D



p.d. I really hope that i will be able to play it tomorrow and if i dont report means that it all works!!!!

THANK YOU ALL for suggestions and support


Tindrli out :D
 
i had a fear that this might happen and
i think im cursed :crazy:
i have never been able to play this game for more than 7 or 8 mins.. usualy got that stupid BSOD after 30 sec or 1 min at most.. but yesterday after i did all this above i was suddenly able to play for 4 damn hours without any kind of freezing or crash or BSOD.
Today the game died again :swear: aproximatly 30 sec with same god damn symptoms.
i just dont know what to do more :crazy:
 
If you have any spare motherboards, processors, memory modules, video cards, etc., then I suggest you get to troubleshooting to find the guilty component. The easiest thing to test is your memory and hard drive (run Memtest86 and do a full chdsk), and stress tests on your processor (Prime95, Linpack) or video card (FurMark) can reveal instabilities. Be sure to keep a close eye on temperatures while running stress tests so things don't get out of hand - usually anything approaching 90-100 degrees is a warning sign. If you can't isolate the problem, it might be the motherboard itself, or your power supply. Make absolutely sure your PSU is capable of outputting the watts needed for your hardware - cheaper brands will often state numbers beyond what they are really capable of. Alternately, if anything is still under warranty, see about getting it replaced.

Saddly i dont own any spare parts :(
thanx for all this advices but since i have never ever had BSOD before and as i said before i played almost every mayor title without any serius problems i just couldnt accept that my hardware is failing so i didnt make any of those tests that you suggested above. exept the test with FurMark and since we re out of ideas for making FNW work with windows 7 on my system i decided to format and put windows XP back .. Currently im updating all nececary drivers on a clean XP install and then try to play.. If all this fail i will make all those tests that you mentioned to see if anything is damaged or near death..

I just dont understand how the fuck all from sudden im able to play for full 4 hours without a silgle glitch if for example my card is overheating.. just dont get it :crazy:
 
Ive been through a few burned out Video Cards and weirder things have happened.

Haha one was dying and i knew it so i opend the case and put a ziplock of ice on top of the card and played till they melted. Got a few more days at least before it finally had it. Never spilt a drop either!
 
ok.. clean format.. install only .net framework and mainboard, sound and graphic drivers..im playing again without any freeze glitch or nothing for more than two hours.. all good.. will keep you all updated tomorow
 
First thing: Sorry for my english, i'm just a Pollack ;)

I've got the same problem with THE SAME VIDEO CARD (+2GB 667 RAM, ASRock 1333 and E2180@2GHz). I'm sure this is not overheating card and I even know a recipe for BSOD in New Vegas:

some move and shooting/jumping + clicking a TAB (or another pipboy key) = BSOD after 5-60 seconds of this combo.

Clicking the TAB can be changed for starting a conversation with NPC.

I see 4 possibilities:

- problem with Nvidia drivers
- Obsidian are the biggest bunglers in the world (cuz they are?), New Vegas doesn't like 8800GT, and we must wait for a patch
- New Vegas doesn't like a mess in the system/HDD*
- New Vegas doesn't like an Avira, K2T, viruses, or another applications

The Fallout 3 hasn't got this problem, Oblivion too. So I think this is not fault of Gamebryo. Another games work great on my PC, so this is not overheating or broken video card.

*So, can you say dear tindrli what happend after your format? No BSODs, or format doesn't help?

Once again: Sorry for my english :x

Edit: My system: Windows XP SP3 PL. I will try to install 18X.xx drivers and just reinstall the game... :/

Edit2:Drivers 186.18 + reinstallation = bsod, bsod, bsod.
 
I've tried to play with gamebooster and Avira off - doesn't help.

But as far as I know, this problem IS RELATED with 8800GT. Reason? Other people with this card have the same BSODS too.

Maybe tindrli says his games works nice after format, but he was saying the same when he used the TDR fix. That's why I'm still waiting for answer - I just don't want to format my disk when it's not needed.

I'm going to use a trick with switching off ffdshow audio decoder for New Vegas...
 
Trick with ffdshow didn't help. I've checked the Bethesda Softworks Forums and some other people have the same problem.

Probably, I will format my PC tommorow. If it won't help, I'm going also to clean PC inside and use the arctic silver 5 on my GPU and CPU.

It's all what I can do, except waiting for a patch, because I think it's a fault of Obsidian and their game :/

Sorry for my english!
 
If it's overheating fault, it may change something. 65*C in firefox is not a good score, even for 8800GT :E

But I don't think so. If tindrli's game was "BSoDing" on ~55*C... :/

Maybe Obsidian will patch it... Maybe... In next year...
 
HDR -> Bloom

AAx4 -> AAx0

dxdiag sound acceleration -> from 4th to 1st degree

No BSoDs after 4 hours of playing.
 
Kotylion said:
First thing: Sorry for my english, i'm just a Pollack ;)

I've got the same problem with THE SAME VIDEO CARD (+2GB 667 RAM, ASRock 1333 and E2180@2GHz). I'm sure this is not overheating card and I even know a recipe for BSOD in New Vegas:

some move and shooting/jumping + clicking a TAB (or another pipboy key) = BSOD after 5-60 seconds of this combo.

Clicking the TAB can be changed for starting a conversation with NPC.

I see 4 possibilities:

- problem with Nvidia drivers
- Obsidian are the biggest bunglers in the world ({Beat me like a baby seal "cuz" I am STOOPID!} they are?), New Vegas doesn't like 8800GT, and we must wait for a patch
- New Vegas doesn't like a mess in the system/HDD*
- New Vegas doesn't like an Avira, K2T, viruses, or another applications

The Fallout 3 hasn't got this problem, Oblivion too. So I think this is not fault of Gamebryo. Another games work great on my PC, so this is not overheating or broken video card.

*So, can you say dear tindrli what happend after your format? No BSODs, or format doesn't help?

Once again: Sorry for my english :x

Edit: My system: Windows XP SP3 PL. I will try to install 18X.xx drivers and just reinstall the game... :/

Edit2:Drivers 186.18 + reinstallation = bsod, bsod, bsod.

Do you have installed ffdshow codecs on your system? :) If you have then add FalloutNV.exe to exception list (option "‘Dont use ffdshow in’") in ffdshow config (video and audio) ;) this should fix your problem
 
Kotylion wrote:
First thing: Sorry for my english, i'm just a Pollack

I've got the same problem with THE SAME VIDEO CARD (+2GB 667 RAM, ASRock 1333 and E2180@2GHz). I'm sure this is not overheating card and I even know a recipe for BSOD in New Vegas:

some move and shooting/jumping + clicking a TAB (or another pipboy key) = BSOD after 5-60 seconds of this combo.

Clicking the TAB can be changed for starting a conversation with NPC.

I see 4 possibilities:

- problem with Nvidia drivers
- Obsidian are the biggest bunglers in the world ({Beat me like a baby seal "{Beat me like a baby seal "cuz" I am STOOPID!}" I am STOOPID!} they are?), New Vegas doesn't like 8800GT, and we must wait for a patch
- New Vegas doesn't like a mess in the system/HDD*
- New Vegas doesn't like an Avira, K2T, viruses, or another applications

The Fallout 3 hasn't got this problem, Oblivion too. So I think this is not fault of Gamebryo. Another games work great on my PC, so this is not overheating or broken video card.

*So, can you say dear tindrli what happend after your format? No BSODs, or format doesn't help?

Once again: Sorry for my english

Edit: My system: Windows XP SP3 PL. I will try to install 18X.xx drivers and just reinstall the game... :/

Edit2:Drivers 186.18 + reinstallation = bsod, bsod, bsod.


Do you have installed ffdshow codecs on your system? If you have then add FalloutNV.exe to exception list (option "‘Dont use ffdshow in’") in ffdshow config (video and audio) this should fix your problem

sorry i was too busy with playing that i didnt notice that you people are still watching this post..

i found solution to my problem and sadly it was an OS. after i put back my old XP everything was great.. in 4 days more las i had 3 freezes most.. and i was playing more than 4 hours per day.. I JUST DONT GET CRASHES ANY MORE :clap: :clap:
and i didnt install any of codecs only this.. i dont even have antivirus!!!!

ok.. clean format.. install only .net framework and mainboard, sound and graphic drivers

and i did lowed the sound hardware acceleration to basic
thank you all for supporting.. im gona clime that black mountain!!!!
 
and i did lowed the sound hardware acceleration to basic

Yes, that was a reason of our problem. I've done the same (my previous post) and I'm able to play without any BSoDs too.
 
Back
Top