| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 123261 | 2012-02-14 05:45:00 | Odd things happening | pcuser42 (130) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1259051 | 2012-02-14 05:45:00 | Earlier today my computer had a BSOD, but not the usual one: the entire screen went dark blue, no text or anything, and the reset button wouldn't work. Just a few minutes ago, Aero switched itself off and back on again, with no Windows messages at all. I have also had the occasional usual BSOD, but didn't take note of the error code. Could they be related, and what's a probable cause? | pcuser42 (130) | ||
| 1259052 | 2012-02-14 05:49:00 | Get bluescreenview and see what that says | Speedy Gonzales (78) | ||
| 1259053 | 2012-02-14 06:46:00 | I have also had the occasional usual BSOD A normally working PC doesn't get "occasional usual BSOD" If you get BSODs periodically there is probably something wrong with your system. |
Agent_24 (57) | ||
| 1259054 | 2012-02-14 06:58:00 | Bluescreenview gave me this when I copied the most recent dump: 020412-13400-01.dmp 4/02/2012 8:01:22 p.m. 0x00000109 a3a039d8`98bf851a b3b7465e`eb3d6354 fffff880`014e6430 00000000`00000001 ndis.sys ndis.sys+3f430 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\020412-13400-01.dmp 4 15 7601 275,952 A normally working PC doesn't get "occasional usual BSOD" If you get BSODs periodically there is probably something wrong with your system. Usual BSOD in this case refers to the Windows BSOD with text, not that they're a normal part of my computer's operation. :p Actually, here's what the completely blank BSOD looked like: 3581 |
pcuser42 (130) | ||
| 1259055 | 2012-02-14 07:10:00 | Ndis.sys belongs to the network drivers. These maybe crashing. Mcafee isnt on this PC is it?? If it is uninstall it. It's known to crash this file | Speedy Gonzales (78) | ||
| 1259056 | 2012-02-14 08:27:00 | Mcafee isnt on this PC is it?? Hell no :p |
pcuser42 (130) | ||
| 1259057 | 2012-02-14 08:31:00 | What firewall is installed (besides windows firewall)? | Speedy Gonzales (78) | ||
| 1259058 | 2012-02-14 08:44:00 | That error code can also mean General cause of stop 0x00000109 error: - 1.viruses 2.spyware 3.conflict in registry or due to corruption in registry 4.Due to outdated device driver 5.Due to hardware malfunctioning :2cents: If its W7, click start, type in Reli Open the view reliability history, look at the times if played up and see if there are any errors relating to drivers, hardware etc. What security is on the PC ? |
wainuitech (129) | ||
| 1259059 | 2012-02-14 09:18:00 | Windows Firewall, MSE, that's about it. :p The only thing Reliability Monitor is saying is that Windows wasn't shut down properly, but doesn't give any reasons as to why... Windows Update gives no updates at all. |
pcuser42 (130) | ||
| 1259060 | 2012-02-14 09:41:00 | If its W7, click start, type in Reli Open the view reliability history, look at the times if played up and see if there are any errors relating to drivers, hardware etc. What security is on the PC ? Ah, I'd never stumbled across Reliability Monitor. Thanks muchly for that. Interesting, how the vast majority of the blips in reliability are related to Steam, or Steam games. |
Paul.Cov (425) | ||
| 1 2 | |||||