• PC Games Crash to Desktop/BSOD
    31 replies, posted
Basically, when I'm in a game my computer goes either to BSOD or it crashes to desktop. This is just speculation, but depending on the performance level the game needs, it seems to crash faster. Games such as Garry's Mod haven't crashed on me yet. But, like I said, I don't know how accurate I would be to say that. Sometimes faster than other times but it almost always does it before a play session is over. I downloaded new drivers last night for my Graphics Cards. I thought it could be overheating so I downloaded everest and here are the temps it gave me: Field Value Sensor Properties Sensor Type Fintek F71882F (ISA A00h) GPU Sensor Type Analog Devices ADT7473, Volterra VT1165 (NV-I2C 2Eh, 70h) Temperatures Motherboard 34 °C (93 °F) CPU 34 °C (93 °F) CPU #1 / Core #1 48 °C (118 °F) CPU #1 / Core #2 48 °C (118 °F) CPU #1 / Core #3 46 °C (115 °F) CPU #1 / Core #4 46 °C (115 °F) Aux 46 °C (115 °F) GPU1: GPU 48 °C (118 °F) GPU1: GPU Memory 40 °C (104 °F) GPU1: GPU Ambient 42 °C (108 °F) GPU1: GPU VRM 37 °C (99 °F) GPU2: GPU 47 °C (117 °F) GPU2: GPU Memory 40 °C (104 °F) GPU2: GPU Ambient 40 °C (104 °F) GPU2: GPU VRM 37 °C (99 °F) WDC WD3000HLFS-75G6U1 [ TRIAL VERSION ] Cooling Fans CPU 990 RPM GPU1 1371 RPM (40%) GPU2 1393 RPM (40%) Voltage Values CPU Core 1.17 V +3.3 V 3.33 V +5 V 5.09 V +12 V [ TRIAL VERSION ] +3.3 V Standby 3.31 V VBAT Battery 3.23 V GPU1: GPU Vcc [ TRIAL VERSION ] GPU1: GPU VRM [ TRIAL VERSION ] GPU2: GPU Vcc [ TRIAL VERSION ] GPU2: GPU VRM [ TRIAL VERSION ] Current Values GPU1: GPU VRM [ TRIAL VERSION ] GPU2: GPU VRM [ TRIAL VERSION ] Here are my specs: Processor: Intel(R) Core(TM) i7 CPU 965 @ 3.20GHz (8 CPUs), ~3.7GHz Memory: 6134MB RAM Hard Drive: 297 GB Video Card: SLi NVIDIA GeForce GTX 280 (x2) Monitor: Dell 1704FPT (Analog) Sound Card: Digital Output Device (HDMI) (Creative SB X-Fi) Speakers/Headphones: Turtle Beach HPA2 Keyboard: Razer Lycosa Mouse: Logitech G5 Operating System: Windows Vista™ Home Premium (6.0, Build 6001) Service Pack 1 (6001.vistasp1_ldr.081020-1655) [b]NOTE: THIS IS OLDER INFO. SINCE THIS WAS ORIGINALLY NAMED, I DOWNLOADED SERVICE PACK 2, ALONG WITH OTHER UPDATES. I HAVE NOT TESTED ANY GAMES SINCE THEN. [/b] I now EVGA Precision and can max out my GPU fans now, so the temps for the GPU should be lower than what Everest picks up. [u]Any ideas on how to fix the problem? I would rather not do a reformat but if I have I guess I have to. Any help would really be appreciated.[/u]
* ‏*  ‏
Okay, I'll be sure to do that. but if I remember right it was something like 0x00000006 that's IF I remember right. Like I said, I'll get back to you ;). Thanks for the reply!
* ‏*  ‏
Okay, thank you. I actually tried the verifier first. I'll post updated info on the tests asap. Thanks for your help! Oh, and I love how people go through threads and rate everything "Dumb". Edit/Add: Oh and is this supposed to only verify when I'm in a game? I set all the settings as you said to put them, though I don't know what else to do so I'm assuming that the problem will identify itself if I'm in a game. But please correct me if I'm wrong :P
I had this same problem for the past month, If your symptoms are anything like mine, which i think they are, You need some more RAM.
* ‏*  ‏
[QUOTE=ImOnTheBall;16718891] 6GB of RAM is plenty to run just about any game on the market today. I see no problem there. [/QUOTE] Nah i meant that one of your sticks may be dodgy, and thus will need replacing, poor choice of wording in retrospect.
* ‏*  ‏
[QUOTE=ImOnTheBall;16718891]No, it constantly verifies the driver gaming or not. If you do not get a crash after enabling special pool then you can leave it like that until NVIDIA releases another driver. Pool tracking should detect problems like the pool being leaked or freed. If that happens I'm not sure what you could do, perhaps roll back driver. Special Pool will ensure that the drivers will still be stable if they try to allocate a larger memory pool than it's access permissions allow. Roll back driver is likely to fix this problem or at least show that it's highly unlikely that NVIDIA's drivers are causing the problem. So since you did the driver verifier try gaming again and see if you crash. The whole dumb thing is a greasemonkey script I believe. 6GB of RAM is plenty to run just about any game on the market today. I see no problem there. EDIT: Oh boy it seems 5 wiseasses are running that script now (or just from 5 accounts) EDIT2: I just realized I misread your OP, I thought you said the crashes happened after you updated the driver. It could still be the driver but if the driver verifier does nothing then disable it and give the details of the BSOD you get when you start gaming again.[/QUOTE] Kay I ran it and I have crashed to desktop since then after a few minutes of playing Arma 2. So, should I turn that off and rollback and see if that works? Edit/Add: Oh and I have ran Memtest for about 10 hours and Windows Memory Diagnostic and some tune up stuff and nothing was detected. So idk if it's my RAM or not. Edit/Add 2: Oh- lol- I was also running two copies of Memtest partitioned to smaller blocks of memory.
* ‏*  ‏
[QUOTE=ImOnTheBall;16725361]Well just disable the Driver verifier (start > run > verifier > delete existing settings), reboot, let it crash, give details about BSOD. It could be the graphics driver but it might be something else. Roll back might work but error details of the BSOD would be really helpful. Just a driver name and an error code will do. Even just an error code is fine.[/QUOTE] My PC crashed to BSOD just a few moments ago. While I did write down the code, I'm not sure how accurate I was because it did the physical memory dump thing before I could really check that. So here's what I have: Edit: Wrote down the wrong thing, it's actually 0x000000BE
* ‏*  ‏
[QUOTE=ImOnTheBall;16729449]0xBE is when a device driver is tries to write to read-only memory. Have you tried the usual "Last Known Good Configuration?" You could try Driver Verifier on all drivers (use all settings except low resources simulation and maybe not special pool) if last known good configuration doesn't work to perhaps see what driver is causing the problem. Also, 0xBE is common when upgrading hardware, have you done so lately? Edit: the BSOD didn't happen to mention the driver did it?[/QUOTE] I think it actually could be more than one error. The other one was 0x000003b, I just thought I had read it wrong the first time, which is still possible. and is there a way to look up any errors after I crash??? Because it's hard to read them during the physical memory dump. and ill try that.
* ‏*  ‏
yes, I tried last known good config after I did that error check thing because my PC wouldn't launch after that lol.
* ‏*  ‏
Yeah. I did the changes to Driver verifier and it kept going to BSOD everytime it launched and would restart the PC and repeat (after it gave me the option of continuing normally or reverting back to last known good config etc etc). So I did last known good config after I tried launch normally 2 or 3 times. Edit/Add: Crashed again. Got the error 0x000000124.
* ‏*  ‏
Yeah crashed again and got 0x000007F. Idk. I'll try safemode then if not that I really don't know what the fuck else to do. I don't know what hardware is broken if any and I'm not going to go out and buy new stuff if I don't need to. Shit is expensive.
* ‏*  ‏
Your ram is bad, well 1 stick is loading the info off the southbridge improperly
* ‏*  ‏
[QUOTE=ImOnTheBall;16804488]I was asking for a real second opinion not a troll's silly opinion :smile:.[/QUOTE]Are you calling JE a troll? [editline]12:59AM[/editline] lurk more
[QUOTE=ImOnTheBall;16804488]I was asking for a real second opinion not a troll's silly opinion :smile:.[/QUOTE] Oh wow I have been called a troll, look into my post history for more trolling madness [quote]Divide by zero error A divide by zero is caused when a DIV instruction is executed and the divisor is 0. [highlight][b]Memory corruption[/b] (or other hardware problems)[/highlight] or software failures can cause this. [/quote] [quote]This fault is generated when the processor attempts to execute an invalid instruction. This is generally caused when the instruction pointer has become corrupted and is pointing to the wrong location. [highlight][b]The most common cause of this is hardware memory corruption.[/b] [/highlight][/quote] [quote]A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. [highlight][b]Hardware problems are usually related to CPU, RAM, or bus. [/b[/highlight]]Kernel stack overflows are almost always caused by faulty kernel-mode drivers. [/quote] see a connection here? 0X(numbers here) is usually a pin address on the ram stick the southbridge will give info off the hard drive load it into ram then the cpu will ask for memory dump in ram stick A pin 0X000275 but there is an error on the stick of ram and it sends the wrong info causing an instability in the program and finally a BSOD
* ‏*  ‏
So many BSODS. JE's got the answer OP. Even if the memtests come up clean, they're not perfect. Try taking out the RAM sticks and swapping them or putting them into different slots. If it still happens, then find some new ones.
Okay, I'll try that. I actually just took out all my cards and vacuumd out my computer. But, that didn't work. So, I found this program called BlueScreen Viewer. (I recently refromatted so it doesn't show the ones previous to yesterday. Here's the screen:[URL=http://filesmelt.com/][IMG]http://filesmelt.com/downloader/saioethaiowehfwioeh.jpg[/IMG][/URL] So, yeah, I don't know if it's my ram or what. I looked up a few of the errors like ntoskrnl.exe and that's like a keyboard error. and mfeavfk.sys is mcafee, lol. Any other ideas?
* ‏*  ‏
[QUOTE=ImOnTheBall;16890142]Hmm, I still think that it's hardware. I'm pretty sure it isn't RAM (for what it's worth, JohnEdwards and SteeleCratos both said on another topic that the problem was RAM and it turned out to be a driver error, this does not necessarily discredit them though, I just don't think it's a good idea to jump to a conclusion too fast. Really what I don't want you to do is buy new hardware that you don't have to). You could try using one of the sticks and if you still get a crash try a different one and if you get another crash try the 3rd one and if you still get a crash that it is that much more unlikely that it is your RAM. You could also try Microsoft support. By the way, ntoskrnl.exe is the windows kernel, the core of the operating system. One more thing, did you run driver verifier on all the drivers at once? Try that if you haven't (all options except low resources simulation). There might be one driver allocating memory that is meant for other essential kernel mode drivers. It might be McAfee.[/QUOTE] I believe I was going to do that, but then I had to revert to last good config I believe. Also, wouldn't reformatting fix any driver issues? But I'll try it. Once again, thanks for all your guys' help! I really appreciate it. Really. I'll get back to you with the driver verifier asap.
Sorry, you need to Log In to post a reply to this thread.