New
#11
So i crashed again, and Automatic Restart is off, but it automatically restarted. I had no blue screen. Also, no minidump folder in my Windows folder even though it is set to "%SystemRoot%\Minidump"
something isn't right here..
So i crashed again, and Automatic Restart is off, but it automatically restarted. I had no blue screen. Also, no minidump folder in my Windows folder even though it is set to "%SystemRoot%\Minidump"
something isn't right here..
Ok, i've crashed twice since I wrote that, one immediately restarted and one froze on a bluescreen- neither of them created a minidump folder in my windows folder... so my minidumping isn't working for some reason?
Can't blame you at all for trying, I wouldn't want to go through the hassle of sending it back either until I exausted every possible solution.
You might want to see what the CPU and GPU temps are around the time of the crash, there are a bunch of programs you can do that with.
The fact that this seems to be happening with games after a certain amount of time tends to point the finger at a cooling problem of some sort.
It sounds like your machine is gaming just long enough to overheat at which point it crashes which is fairly typical for an overheating problem.
Because you are running the GTX260 you can run precision software from EVGA. You can keep track of temps and more importantly turn the fan up if you suspect a heating problem, you can also clock the card down a bit which has been known to fix this type of problem in the past.
You can get it here> http://www.evga.com/PRecision/
definitely isn't over heating, temps are perfectly fine... :\
What i have noticed is that I tend to blue screen during similar "locations" in WoW that are maybe graphic or memory intensive?
Please do this to help us look into the dump file issue:
MSINFO32
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO\" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.
http://www.files.failedmiserably.com/data/msinfo32.zip
There is my msinfo32 file
here are some of the BSODs i've gotten recently
http://img188.imageshack.us/img188/3312/pc291315.jpg
http://img97.imageshack.us/img97/2327/pc291316.jpg
http://img97.imageshack.us/img97/2742/pc291317.jpg
http://img686.imageshack.us/img686/8651/pc301318.jpg
http://img686.imageshack.us/img686/2007/pc301319.jpg
I've noticed that my crashes all do seem to happen at the same locations within WoW, hopefully that's a helpful peice of info
ps: I still haven't been able to find any visible minidumps
Last edited by duckstaped; 23 Dec 2009 at 23:18.
Just passing thru.... I have not read this threadd. I suspect John (usamsa) coulduse the acrual DMP file use these instructiions to find etc https://www.sevenforums.com/crash-loc...d-problem.html
Ken J_+
Nope, no crashes noted in the MSINFO32 file.
Many different reasons for this, most of which I was able to rule out with the MSINFO32 file
So, the question is, how comfortable are you with editing the registry?
I've recently read some articles on some Win7 registry issues (with regards to crash dumps) and would like to take a look at them on your system.
I'll edit my registry if you honestly recommend it... you guys are the ones who have a better idea about it than me.
Honestly, if I jack something up, i'll just clean format the computer I guess...
I mean... if you think editing registry is worth a try then i'll do it!