I reformatted my PC 3 weeks ago since then have had 4 sporadic BSOD. I didn't think much of them individually since each occurrence seemed explainable. One from trying to install my Razer Naga Drivers (without having the right chipset drivers), one from playing in SWTOR Beta and a couple other similar type situations. Today I updated my WOW launcher for 4.3 and went to open Firefox and then blam, BSOD. Now it seems like an issue to resolve.
specs:
Windows 7 64bt
Intel Core2 Quad CPU Q6600 @ 2.4GHz
4GB RAM
ATI Radeon HD 3800 Series
Here is what my event manager reported...
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 30/11/2011 12:43:44 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Crashlove-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
41
2
1
63
0
0x8000000000000002
11921
System
Crashlove-PC
278
0xfffffa800517a2d0
0xfffff880042c780c
0x0
0x2
false
0
I have my .dmp file zipped if it will help anyone wants to see it (can't attach files).
I have tested my memory with Windows memory diagnostic and it came up clean. I do think too much memory is being used somehow though (Task Manager always has memory at or near 1/2 way (1.43GB or higher)).
Anything else I can provide to help let me know. My system is almost 3 years old now, I had no BSOD problems before the reformat.
- Follow via:
- RSS
- Email Alert
Question
0
Votes
Can you solve my BSOD issues (W7)?
29th Nov 2011
Answers (4)
0
Votes
That event is already after the crash.
That's to do with the error displayed on reboot.
What is actually needed are the BSOD error codes and messages. And from what you say, this isn't a problem, but several unrelated problems causing completely different BSODs. Of the two incidents you explicitly mention, the first has a very obvious cause for the BSOD, the second has a very likely cause: beta software.
So if FF or something else crashes the system again, get his license plate number.
edit: I expect your crash after installing the new WOW launcher may have been like this:
http://us.battle.net/wow/en/forum/topic/3657606108
What is actually needed are the BSOD error codes and messages. And from what you say, this isn't a problem, but several unrelated problems causing completely different BSODs. Of the two incidents you explicitly mention, the first has a very obvious cause for the BSOD, the second has a very likely cause: beta software.
So if FF or something else crashes the system again, get his license plate number.
edit: I expect your crash after installing the new WOW launcher may have been like this:
http://us.battle.net/wow/en/forum/topic/3657606108
Updated - 29th Nov 2011
Replies
Is there a way to find out the cause? Event viewer doesn't seem to report it. I have the .dmp file I guess but I don't know otherwise.
And I agree with that the previous BSOD seem explainable as I posted earlier. This one wasn't really explainable which is why I got worried. There were 5 BSOD overall but 3 were from the Naga drivers before I realised I hadn't installed the chipset drivers (I know right). I guess the fact that my memory usage is always high bothers me too.
And I agree with that the previous BSOD seem explainable as I posted earlier. This one wasn't really explainable which is why I got worried. There were 5 BSOD overall but 3 were from the Naga drivers before I realised I hadn't installed the chipset drivers (I know right). I guess the fact that my memory usage is always high bothers me too.
luketigers@...
29th Nov 2011
0
Votes
sounds to me like you might have double loaded your video drivers
could have picked up a virus and corrupted your regestry,id do clean install and make sure your drivers are all up to date beta are test drivers in run whql till it get certified chek your bios might need a rollback and reflash good luck bud
30th Nov 2011
0
Votes
"Is there a way to find out the cause?"
Yes. But as we have determined, most of those events had different causes.
To determine the cause for any BSOD, take note of what the BSOD says, specifically the
STOP code and message. You can then look it up yourself and/or post the info here. The BSOD is telling you what the problem is. One can't possibly begin to guess the cause without the information.
If you don't see it again, then there's nothing to fix.
To determine the cause for any BSOD, take note of what the BSOD says, specifically the
STOP code and message. You can then look it up yourself and/or post the info here. The BSOD is telling you what the problem is. One can't possibly begin to guess the cause without the information.
If you don't see it again, then there's nothing to fix.
30th Nov 2011
0
Votes
Obviously you should
Run Linux.
30th Nov 2011
