BSOD
-
- 2StarLounger
- Posts: 177
- Joined: 25 Jan 2010, 00:50
- Location: Swanzey, NH
BSOD
Lately, I have been getting random BSOD, most always when the machine is idle. The minidump gives little to nothing that I can see to try and find out why this is happening.
WhoCrashed report appears to give more information, but it doesn't make much sense to me.
I have attached both the minidump and the WhoCrashed reports hoping someone can figure out what is happening and what remedies there are to fix things. :)
WhoCrashed report appears to give more information, but it doesn't make much sense to me.
I have attached both the minidump and the WhoCrashed reports hoping someone can figure out what is happening and what remedies there are to fix things. :)
You do not have the required permissions to view the files attached to this post.
Jeff
Artificial Intelligence is no match for natural stupidity!
Artificial Intelligence is no match for natural stupidity!
-
- Administrator
- Posts: 79520
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
-
- 2StarLounger
- Posts: 177
- Joined: 25 Jan 2010, 00:50
- Location: Swanzey, NH
Re: BSOD
No overheating... 36° C (according to Speccy), which is what I would expect with the cooling system I have.HansV wrote:A quick search turns up overheating of the CPU as a possible cause of the errors you get, but that seems unlikely if the machine is idle before the blue screen occurs. Still, does a hardware profiler such as Speccy (free) reveal anything unusual?
As you might/should expect, I've Googled myself dizzy trying to find something similar but nothing really helpful. I suppose I could try running MEMTEST 86 again, which I have done periodically in the past and everytime the RAM passes. Of course, RAM can go bad, albeit not typically.
Anything else you can suggest?
Perhaps totally unrelated:
1. Using IE9 when doing image searches, the browser will slow to a crawl until the page loads. Firefox and SeaMonkey have no problems whatsoever. It seems that IE can't handle heavy graphic displays... graphic card perhaps?
2. PayPal website cannot be displayed properly. A few images/icons can be seen but 99% of the text is jibberish, e.g., uppercase K and V, short verticle lines, dashes, etc. This is cross browsers. There was one other site that had the same problem, but other than that one time (can't remember what site it was, hahaha), no such problems anywhere else.
Jeff
Artificial Intelligence is no match for natural stupidity!
Artificial Intelligence is no match for natural stupidity!
-
- PlutoniumLounger
- Posts: 16268
- Joined: 24 Jan 2010, 23:23
- Location: brings.slot.perky
Re: BSOD
I used to get machine crashes from overheating when the machine was doing nothing but struggling to push air with a dust-encrusted fan. Over the years I have "fixed" several system with a powerful vacumn cleaner.HansV wrote:... but that seems unlikely if the machine is idle before the blue screen occurs.
I'm just saying .. "Vista" sounds old, so maybe the machine is old, so maybe the machine has bred dust-bunnies ...?
If it isn't one thing it's another, and very often both. E.F.Benson
-
- Administrator
- Posts: 79520
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: BSOD
I agree that 36°C is nothing to worry about.
I assume that you have found Stop error message on a Windows Vista or Windows Server 2008-based computer that has multiple processors installed: "Stop error code 0x00000101 (CLOCK_WATCHDOG_TIMEOUT)" and the corresponding Hotfix Windows Vista and Windows Server 2008 do not correctly audit all the privilege use events.
I assume that you have found Stop error message on a Windows Vista or Windows Server 2008-based computer that has multiple processors installed: "Stop error code 0x00000101 (CLOCK_WATCHDOG_TIMEOUT)" and the corresponding Hotfix Windows Vista and Windows Server 2008 do not correctly audit all the privilege use events.
Best wishes,
Hans
Hans
-
- 2StarLounger
- Posts: 177
- Joined: 25 Jan 2010, 00:50
- Location: Swanzey, NH
Re: BSOD
1. Yes, the machine is rather "old" compared to what has come along since Vista was release. However, I just happen to really like Vista and it has been great since the day I built the machine.ChrisGreaves wrote:I used to get machine crashes from overheating when the machine was doing nothing but struggling to push air with a dust-encrusted fan. Over the years I have "fixed" several system with a powerful vacumn cleaner.HansV wrote:... but that seems unlikely if the machine is idle before the blue screen occurs.
I'm just saying .. "Vista" sounds old, so maybe the machine is old, so maybe the machine has bred dust-bunnies ...?
2. I am rather meticulous when it comes to "clean". Regular cleaning inside and out is practiced. There are no dust bunnies, cat hair, or anything else in the box. :)
Good suggestion nonetheless. I clean out the inside of every machine I work on and it's amazing sometimes to see what has accumulated.
Jeff
Artificial Intelligence is no match for natural stupidity!
Artificial Intelligence is no match for natural stupidity!
-
- PlatinumLounger
- Posts: 5685
- Joined: 24 Jan 2010, 19:16
- Location: Cape Cod, Massachusetts,USA
Re: BSOD
In the Who Crashed Report it suggests that a ntkrpamp.exe file may be corrupt or need updating. Have you checked this out?
Also:
http://www.geekstogo.com/forum/topic/33 ... ots-bsods/" onclick="window.open(this.href);return false;
Also:
http://www.geekstogo.com/forum/topic/33 ... ots-bsods/" onclick="window.open(this.href);return false;
BOB
______________________________________
If I agreed with you we'd both be wrong.
______________________________________
If I agreed with you we'd both be wrong.
-
- 2StarLounger
- Posts: 177
- Joined: 25 Jan 2010, 00:50
- Location: Swanzey, NH
Re: BSOD
I do not have "multiple processors"... just the one AMD 64 Athlon X2 6000. Thus, the article would be irrevelant, no?HansV wrote:I agree that 36°C is nothing to worry about.
I assume that you have found Stop error message on a Windows Vista or Windows Server 2008-based computer that has multiple processors installed: "Stop error code 0x00000101 (CLOCK_WATCHDOG_TIMEOUT)" and the corresponding Hotfix Windows Vista and Windows Server 2008 do not correctly audit all the privilege use events.
Jeff
Artificial Intelligence is no match for natural stupidity!
Artificial Intelligence is no match for natural stupidity!
-
- 2StarLounger
- Posts: 177
- Joined: 25 Jan 2010, 00:50
- Location: Swanzey, NH
Re: BSOD
Yep, read that thread but that too is irrevelant since I do not have nor ever have had Avast installed on this system. I keep leaning toward hardware vs. software as the culprit. But I certainly wouldn't disregard the possibility that it is software related. It would surely make it easier to fix.viking33 wrote:In the Who Crashed Report it suggests that a ntkrpamp.exe file may be corrupt or need updating. Have you checked this out?
Also:
http://www.geekstogo.com/forum/topic/33 ... ots-bsods/" onclick="window.open(this.href);return false;
Jeff
Artificial Intelligence is no match for natural stupidity!
Artificial Intelligence is no match for natural stupidity!
-
- 2StarLounger
- Posts: 177
- Joined: 25 Jan 2010, 00:50
- Location: Swanzey, NH
Re: BSOD
I'm going to take it as applying to "multiple processors" vs. a single "multi-core" processor.HansV wrote:Not sure whether it applies to multi-core processors too - the AMD 64 Athlon X2 6000 has two cores...
Jeff
Artificial Intelligence is no match for natural stupidity!
Artificial Intelligence is no match for natural stupidity!
-
- Administrator
- Posts: 79520
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: BSOD
The drivers mentioned in the crash report are system drivers, so you cannot simply download and install updated versions (apart from that, I don't trust 'generic' sites offering driver updates). If the problem keeps occurring you might consider running
sfc /scannow
from a command prompt window.
sfc /scannow
from a command prompt window.
Best wishes,
Hans
Hans
-
- 2StarLounger
- Posts: 177
- Joined: 25 Jan 2010, 00:50
- Location: Swanzey, NH
Re: BSOD
Agree on both items: I do not trust generic sites offering driver updates. I always go to the original manufacturer.HansV wrote:The drivers mentioned in the crash report are system drivers, so you cannot simply download and install updated versions (apart from that, I don't trust 'generic' sites offering driver updates). If the problem keeps occurring you might consider running
sfc /scannow
from a command prompt window.
Yep, scandsk seems like a good plan.
Jeff
Artificial Intelligence is no match for natural stupidity!
Artificial Intelligence is no match for natural stupidity!
-
- PlatinumLounger
- Posts: 5685
- Joined: 24 Jan 2010, 19:16
- Location: Cape Cod, Massachusetts,USA
Re: BSOD
Where did it mention Avast?Pilgrim wrote:Yep, read that thread but that too is irrevelant since I do not have nor ever have had Avast installed on this system. I keep leaning toward hardware vs. software as the culprit. But I certainly wouldn't disregard the possibility that it is software related. It would surely make it easier to fix.viking33 wrote:In the Who Crashed Report it suggests that a ntkrpamp.exe file may be corrupt or need updating. Have you checked this out?
Also:
http://www.geekstogo.com/forum/topic/33 ... ots-bsods/" onclick="window.open(this.href);return false;
That .exe file was developed by Microsoft and is associated with MSDN Disk 2443.4 ( whatever that is? ) but the point is, it's apparently used by many other programs including video, audio types.
Do a search for that file name on your system.
Run the System File Checker on your machine.
Start>Run>Cmd, type sfc \scannow. Let it run.
BOB
______________________________________
If I agreed with you we'd both be wrong.
______________________________________
If I agreed with you we'd both be wrong.
-
- 2StarLounger
- Posts: 177
- Joined: 25 Jan 2010, 00:50
- Location: Swanzey, NH
Re: BSOD
1. ntkrpamp.exe doesn't exist on my system. (yes, I disabled hide hidden protected system files)viking33 wrote:Where did it mention Avast?Pilgrim wrote:Yep, read that thread but that too is irrevelant since I do not have nor ever have had Avast installed on this system. I keep leaning toward hardware vs. software as the culprit. But I certainly wouldn't disregard the possibility that it is software related. It would surely make it easier to fix.viking33 wrote:In the Who Crashed Report it suggests that a ntkrpamp.exe file may be corrupt or need updating. Have you checked this out?
Also:
http://www.geekstogo.com/forum/topic/33 ... ots-bsods/" onclick="window.open(this.href);return false;
That .exe file was developed by Microsoft and is associated with MSDN Disk 2443.4 ( whatever that is? ) but the point is, it's apparently used by many other programs including video, audio types.
Do a search for that file name on your system.
Run the System File Checker on your machine.
Start>Run>Cmd, type sfc \scannow. Let it run.
2. Definitely will run the scannow utility. :)
Jeff
Artificial Intelligence is no match for natural stupidity!
Artificial Intelligence is no match for natural stupidity!