« Reply #68 on: March 03, 2010, 10:14:44 PM »
Suggest you either replace the power supply or buy some popcorn and watch the YouTube video...
Either replace the power supply or watch the video again and again until you understand it. Clearly you missed several key points...
Core Windows files are "rarely" responsible for a crash, e.g. "
ntkrnlkpa.exe" (unless they are "corrupt"); because they are thoroughly tested by Microsoft. When blue screens identify several different modules, it's either power, hardware, (not sure about heat), or
another driver that is corrupting the memory space or data structures of the blue screen modules. The modules named in your blue screens are probably not the underlying cause; they are the "victims".
You want to target the underlying cause, not the "victim" drivers. While it's not necessarily wrong to "verify" the victims, that only confirms what you already know. They're faulting. You need to catch the driver behaving badly
before another driver comes along and trips over its corrupting influence. The video illustrates how you may use driver "verifier" to do this.
If your diagnostic testing indicates blue screens only occur when your
network software is "active", then take a closer look at the network drivers.
a. Are your network drivers "signed"?
b. Are they the correct driver for your operating system?
c. Are there "updated" network drivers available?
d. Are you using a "wired" or "wireless" network adaptor?
Take a look at your
security software. Many of them operate at a low level within the operating system (and actively screen network input/outputs). You could use "
msconfig" to perform diagnostic startups (selectively disable "
non-Microsoft" security software applications and services).
Perhaps you should boot to "
Safe Mode with Networking" to test. In this mode, most if not all of your security software is not started.
Or you could replace the
power supply... Expensive I know, but it might resolve your issue.
