[RESOLVED] BSOD Normally After 15 Minutes from StartUP
I'm been getting BSOD errors (Win 7 - Pro - x86) almost daily after about 15 minutes of up time. Today took about 5 hours before BSOD today.
Hardware remains the same as from Original build.
No software changes other than Microsoft Updates and Firefox Up date. Thought Firefox so changed to IE, but BSOD continues.
Only other system change is deletion of register entry for Library Special folders because MS (my opinion bug) and impact on Win-Explorer.
Register entry change made years ago prior to BSOD.
Attached is a mini-dump file. Hoping someone may be able to assist.
Is your system overclocked at all? That could explain instability...
It could also be down to failing hardware or memory, it might be worth trying to remove anything you have connected via USB as that device is in the error log and a hardware problem could cause kernel level errors.
The NPFS.Sys is a networking component (Named Pipes specifically) so it could be a network related issue, I don't suppose you have any networking devices connected by USB as that could be an easy solution.
Other than that I would consider the RAM, it might be worth either removing a RAM chip (if possible) and seeing if the error happens again, if so replace it and remove a different RAM chip - you might be able to identify a faulty chip this way.
When did the problem start occurring? It might be caused by a faulty driver, worth seeing if there are any updates available either on Windows Update or the device manufacturer's site.
anything you have connected via USB as that device is in the error log
Nothing running from USB. Just standard ports (2.0 and 3.0) connected to MOBO.
Not sure how you determined this - or- if I missed it if readily identified.
Will double check.
Other than that I would consider the RAM
Will pull and use pencil to clean contacts and reinstall and see what happens.
When did the problem start occurring?
Several weeks ago.
Forgot to mention I did hide KB2952664, so not installed to my knowledge (not in list).
Thanks:
Have run:
1) WD Data Lifeguard Extexted - HD came back good
2) Windows Memory Checker - Memory Good (have not run Mem86 yet)
3) Extended Malicious Software Removal Tool -- Not infected. (one thing odd about this was I checked on MSRT around 3/4 way through and it said 52 files infected, yet upon completion reported Not infected.)
4) Temperatures (all cores running around 31C - 36C.
What's odd is once I get past the first BSOD and reboot, system runs good for rest of day. Only once (one day) did I have multiple BSODs.
The text file in the 1st post is BlueScreenView results. Several different files listed including NPFS.sys depending on the particular day BSOD occurred. Today no BSOD so far.
Just BSOD a minute ago just after saving this post (Paragraph above). Have noticed several BSOD have occurred while on this forum. Whether coincidental ?? BlueScreenView says NPFS.sys.
Any suggestions?
Last edited by vb6forever; May 3rd, 2018 at 11:18 AM.
After looking at the attached text file, those all look like memory issues. If MemTest86 from the UBCD passes, it could be a motherboard memory controller issue. The Windows memory test does not test all areas.
The text file in the 1st post is BlueScreenView results. Several different files listed including NPFS.sys depending on the particular day BSOD occurred. Today no BSOD so far.
Just BSOD a minute ago just after saving this post (Paragraph above). Have noticed several BSOD have occurred while on this forum. Whether coincidental ?? BlueScreenView says NPFS.sys.
Any suggestions?
It could be something network related, either a driver issue or possibly a failing network card.
Hopefully got this resolved. As good for last couple days.
What I did:
1) Pulled the only two daughter cards (serial and parallel) and cleaned the contacts and reinserted.
2) Found 1 debug statement not remmed in a program normally running.
Commented out the debug and recomplied. My understanding compiler should ignore anyway but who knows.
Still received a BSOD and Microsoft's troubleshooting dialog.
3) Ran MemTest86. Memory came back OK.
4) Removed router and connected system directly to modem. After running a day with no BSOD, did a factory reset on the modem and put back on-line.
So far everything good to go.
If the router was sending some corrupted packets (or if it was letting hackers send them through), that could definitely have been the cause of the issue.
Note: I always put my networking equipment, especially modems/routers, on a UPS system to avoid issues. A power glitch, even one that you won't even notice, can cause modem/router issues.
Interesting your using UPS to supply these.
Put router back on line and ran most of day but BSOD end of day.
Took router off-line today and just using modem for few days so will report back.
That was an excellent router in its day, but totally obsolete now, unfortunately. If it does turn out to have failed, it won't be a huge loss at this point.
Sadly, BSOD yesterday with Router offline.
Just for kicks, looked at modem electronics this A.M.
and found a bad cap. Replaced cap and up and running rest of day.
Will post back in day or two with outcome.
Been over drivers multiple times and always indicated good.
================================
5/15/2018
As noted in previous post, replaced bad cap in modem but still experienced BSODs.
Ran last couple days and got several BSOD's.
Last night, did the following:
1) Defragmented Hard Drive (only at 1%).
2) Increased page file to 1.5 * RAM and moved it to a separate disk partition.
3) Restored the registry to again allow "Libraries".
Today ran great and no BSOD. Will give a couple days and post back.
I'm going to declare this resolved.
Not sure exactly what corrected it -- possibly -- one of three things.
1) Cable people were over at my neighbors the other day.
Have not talked to them yet, so don't know why.
But maybe something they did resolved the issue.
2) Changed the following settings:
CP > Power Options
a) Require Password for WakeUp (Yes > No)
b) Allow Hybrid Sleep (On > Off)
c) USB Selective Suspend Settings (On > Off)