New
#11
another BSOD, always seems to happen in games (world of warcraft)
Just ran the driver verifier as per the instructions on your link, letting it run 24 hours. Here is a minidump though.
QFTThere is a whole lot in there to learn! I learn every single day.
Hi there
The minidump file didn't tell me much. You said that you got that usually while playing wow. I used to be wow player and I got BSODs a lot of times when I had the game patched. Have you ever tried to re-installed the game.
In the meantime, you might wanna check this article, and you can discuss your problem in there too (World of war craft BSODs "victim")
World of Warcraft - English (NA) Forums -> Blue screen and restart
Regard
Tuan
I've not tried to reinstall the game, I may have to try that though. I'm going to try running the repair tool first to see if anything obvious pops out. I never really considered WoW as the culprit until it BSODed on me last night.
I've been playing other things lately and haven't had any issues, I suppose Age of Conan BSODed once or twice, but not nearly as frequently as wow.
I've noticed that there is always ntkrnlmp.exe in the dump files. Some google searching didn't reveal very much, just that it has to do with the NT kernel like J has mentioned.
I'm going to do some poking around today and see if I can't come up with anything new. Thank you for the response T!
ntkrnlmp.exe is a widows core file. It is not likely to be a problem; most likely to be a victim of a problem.
Just as an experiment for trouble shooting, uninstall AVG > Info > Tool (32bit) - Tool (64 bit) and AVG Identity protection (if you have it installed)> Info > Tool. AVG is known to cause BSOD's on some Win 7 systems. You can always reinstall it if it is not the problem. If the BSOD's go away after you uninstall AVG, then you found the problem.
I recommend that you install either MSE or Avast (free). Both work smoothly with Windows 7.
Last edited by CarlTR6; 23 Jun 2010 at 15:24.
heres an updated total list of my bsods if this helps
edit
also, here is a dxdiag.txt if it helps
Last edited by nickh186; 24 Jun 2010 at 20:56.
The newest minidump point to intelppm.sys, which is Intel Processor driver, I would recommend to download and install fresh copy of it
Also, you might want to run this free stress test
Prime95
bugcheck:
~TuanCode:BugCheck A, {21ea, d, 1, fffff80002ad0830} Probably caused by : intelppm.sys ( intelppm!C1Halt+2 ) Followup: MachineOwner ---------
I installed AVG last week which is why I hadn't tried it, and the BSODs had been going on long before that.
I can try it though if things don't improve.
The intelppm.sys was one of the first problem files that were in the bsods, then it became the ntoskrnl.exe primarily.
Yes, thank you for considering remove AVG as Carl suggested. We all like to help you and we hope you follow our instructions because we will be very happy if it solve you problem
For the intelppm.sys, it was the most recent BSODs that check from the zip file you uploaded
Try what Carl suggest first and see how things go
~Tuan