Torque3D BSoD
by Ehrlich · in Torque 3D Beginner · 02/27/2010 (10:58 pm) · 13 replies
Hello.
i've installed the demo of T3D, and whenever i try to run the demo app. i get a BSoD... i mean, EVERY TIME!!!... so, i installed the latest version of DX, the latest version of PhysX and the latest video card drivers, and NOTHING... i keep getting the same error again and again.
dont know what else to do, so if somebody can shed some light in this case, it'd be greatly appreciated.
i've installed the demo of T3D, and whenever i try to run the demo app. i get a BSoD... i mean, EVERY TIME!!!... so, i installed the latest version of DX, the latest version of PhysX and the latest video card drivers, and NOTHING... i keep getting the same error again and again.
dont know what else to do, so if somebody can shed some light in this case, it'd be greatly appreciated.
About the author
Computer Science Engineer, with interest in Graphicl Computing, unconventional I/O devices and Artificial Intelligence (for games)
#2
i got the problem solved tho, i formatted the machine, and reinstalled windows, and now it works... not sure what the problem was, but i happened to suspect it was the VRAM... now, i think it was some messy drivers or something.
02/28/2010 (1:33 pm)
the toolbox launches ok, but whenever i try to run one of the demoes, it just crashes...i got the problem solved tho, i formatted the machine, and reinstalled windows, and now it works... not sure what the problem was, but i happened to suspect it was the VRAM... now, i think it was some messy drivers or something.
#3
Anyway, glad to hear you got it working.
03/01/2010 (6:20 am)
I actually just dealt with a similar, non-Torque related, odd BSOD at my day job. I wasn't sure what caused it either but a reformat did the trick for me as well.Anyway, glad to hear you got it working.
#4
i did the procedure i mentioned on the 1st post again, and no luck... something's up with either this or my system (most likely my system), if somebodey could shed some light, i guess it could save me a ton of time of formatting and getting windows back on track.
03/01/2010 (4:23 pm)
so, i installed a couple things to get my windows going as usual, you know, Winrar, 7Zip, Unlocker and Foxit Reader... and the problem came back.i did the procedure i mentioned on the 1st post again, and no luck... something's up with either this or my system (most likely my system), if somebodey could shed some light, i guess it could save me a ton of time of formatting and getting windows back on track.
#5
Is it possible that your machine is overheating? Check your fans (on the CPU and the video card). Are they working?
Have you changed any bios settings, to overclock or anything? If so, change them back to the defaults.
Check your RAM - run Windiag and make sure you don't have a bad stick: oca.microsoft.com/en/windiag.asp
You said you updated your video card drivers, but have you done the same for your sound card? Try running with a null sound device.
03/01/2010 (5:25 pm)
Blue screens are usually caused by hardware or drivers. Did anything that you install include some sort of driver?Is it possible that your machine is overheating? Check your fans (on the CPU and the video card). Are they working?
Have you changed any bios settings, to overclock or anything? If so, change them back to the defaults.
Check your RAM - run Windiag and make sure you don't have a bad stick: oca.microsoft.com/en/windiag.asp
You said you updated your video card drivers, but have you done the same for your sound card? Try running with a null sound device.
#6
its not because of overheating, because... well, i have my reasons to believe its not that.
im inclined to believe its because of messy drivers, or something like that... im gonna make some tests on friday, when i have time for that... right now, i just need this b!tch to work.
03/01/2010 (7:01 pm)
i didnt have enough time to try all those... i went ahead and did a fresh windows install.its not because of overheating, because... well, i have my reasons to believe its not that.
im inclined to believe its because of messy drivers, or something like that... im gonna make some tests on friday, when i have time for that... right now, i just need this b!tch to work.
#7
03/24/2010 (2:34 am)
Same exact thing is happening to me :/ I tried doing a new project, load up existing project, uninstall and reinstall, I just can't get the sucker to work
#8
for some reason, i got to the conclusion that the problem is actually the T3D installer... i say this, because last time it happened to me, i had a fresh windows install, and installed T3D again, just to suffer the above mentioned consecuences.
03/24/2010 (7:28 am)
well, if you dont want that to happen again, jsut dont install T3D again ... just leave the directory where you installed it, where you installed it... and when you install windows again, you can use it with no problems.for some reason, i got to the conclusion that the problem is actually the T3D installer... i say this, because last time it happened to me, i had a fresh windows install, and installed T3D again, just to suffer the above mentioned consecuences.
#9
Can't really even begin to trouble shoot with out knowing the BSoD error or atleast the filename included on the error, other than to say it's probably a RAM/Driver error. (Since most of the time it is.)
04/01/2010 (5:36 am)
Well considering it works for 99.9% of people I'm going to venture out on a limb and say it's not the installer...Can't really even begin to trouble shoot with out knowing the BSoD error or atleast the filename included on the error, other than to say it's probably a RAM/Driver error. (Since most of the time it is.)
#10
04/17/2010 (12:13 am)
Hrm...if you could catch what module the crash is in, that may tell you. If it's got an "nv" it's likey NVIDIA. Otherwise you might see an "Ati". Lastly, I've seen odd OS BSODs in graphics apps caused by programs like Windows Blinds.
#11
Another problem was with NVidias network driver, and the names could lead you to believe it was the display driver bugging out. Note down any DLLs in the bluescreens if the names don't mean anything to you. Find some diagnostic tools/websites to figure out where they all belong.
04/17/2010 (3:45 am)
Just a warning: The bluescreens can be misleading. While running XP and still foolishly trying to use Creative's own drivers, I got bluescreens hinting at nvdisp.dll being the problem. Fast-forward past much wasted time, and I started using open source replacement sound drivers. No more problems. True Heisenbugs :)Another problem was with NVidias network driver, and the names could lead you to believe it was the display driver bugging out. Note down any DLLs in the bluescreens if the names don't mean anything to you. Find some diagnostic tools/websites to figure out where they all belong.
#12
anyway try to run this software after the bsod(ofcourse restart first :)):http://www.nirsoft.net/utils/blue_screen_view.html , to find the exact cause which kernel driver(*.sys) causing it,it helped me before to tracking down avast 5 beta kernel driver incompatibility with others my security software setup.
which os do you run?
05/26/2010 (9:12 am)
I believe as others said,either it's overheating,faulty ram,vga,antivirus,firewall or even trojan/virus with rootkit on it,anyway try to run this software after the bsod(ofcourse restart first :)):http://www.nirsoft.net/utils/blue_screen_view.html , to find the exact cause which kernel driver(*.sys) causing it,it helped me before to tracking down avast 5 beta kernel driver incompatibility with others my security software setup.
which os do you run?
#13
11/08/2010 (4:39 am)
I had the same problem and installing the Omega drivers solved the problem.
Associate Scott Burns
GG Alumni