BSOD during a game and at startup

XplicitMind said:

zigzag3143 said:

XplicitMind said:

I don't. The BSOD I just had said it wrote a DMP but I'm looking at the folder right now and it's not there. Can it be somewhere else?

EDIT: Noticed it was set to Kernal Memory Dump. I set it back to Small Memory Dump. Usually around this time I don't suffer any BSODs but when I do I'll post one up. I just woke next time it saves the next DMP.

You can search for *.DM, and they are sometimes in c:\windows and may be called MEMORY.dmp

This MEMORY.dmp file is over 400MB and it won't let me put it into a .zip

How can I go about this?

wont let you? You can upload it to a file sharing service like rapidshare.

Okay yeah the reason why it didn't let me cause it needed permission, took me a while to figure out. But here it is, the dmp from the BSOD after startup today.

https://rapidshare.com/files/1741014655/12182011-1.zip

XplicitMind said:

Okay yeah the reason why it didn't let me cause it needed permission, took me a while to figure out. But here it is, the dmp from the BSOD after startup today.

https://rapidshare.com/files/1741014655/12182011-1.zip

Two problems


I do notice Symantec which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_...080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

What the... I don't have symantec installed at all. The only Anti virus I have installed is MSE.

XplicitMind said:

What the... I don't have symantec installed at all. The only Anti virus I have installed is MSE.

Do yourself a favor and run the removal tool. If you dont have it, it wont run. I am fairly sure it was there but cant reach rapidshare atm to re-do it.

Alright ran norton removal tool, it ran then restarted. Cleaned out my computer using an air compressed can and saw the temp significantly go down but its at it's normal right now around 41C cpu and 66C gpu.

Let's see how this goes for now.

XplicitMind said:

Alright ran norton removal tool, it ran then restarted. Cleaned out my computer using an air compressed can and saw the temp significantly go down but its at it's normal right now around 41C cpu and 66C gpu.

Let's see how this goes for now.

Good luck and let us know if you need help

Ken

Okay so today I just recently gotten 2 BSOD's in a row. It's been an hour and so far no BSOD left. I was just thinking overheating but not sure.

Just got another BSOD while playing SW:TOR, with driver verifier on. Hopefully this will pinpoint the cause of the BSOD. irql_not_less_or_equal

Thanks.