BSOD same time every day

On a normal reboot, the logs only have warnings about Windows Media Center, which Windows 10 gets rid of, but apparently not completely.

"One of the things I've learned is that there's a lot of baggage my PC has been carrying around for the last 6 years. There's a string of about 20 error messages in the log (some critical errors) and a whole bunch of warnings each time I boot up"

This would have been great info at the first post. Is there any reason not to have fixed what was causing the error msgs in the first place? Now I take back all my suggestions for fixing the BSOD.

"Being retired is serious business :)"

that's a fact. your bsod issue is fascinating. i like your workaround. hope the new install works.

Unfortunately I haven't had any time to look into it for the last week. Being retired is serious business :)

What I HAVE done is schedule an automatic restart at 1pm every day that eliminates the crash. If I'm using the PC at 1pm, at least I get an orderly shutdown and all work is saved.

One of the things I've learned is that there's a lot of baggage my PC has been carrying around for the last 6 years. There's a string of about 20 error messages in the log (some critical errors) and a whole bunch of warnings each time I boot up. Having said that, my PC runs just fine other than the stoopid BSOD every day.

I feel I may have to do a clean install to clear this problem.

joebedford wrote:
Picking up from another thread:

Since I upgraded from Windows 7 to Windows 10, my PC crashes every day at 2:21pm. Not 2:20. Not 2:22. 2:21.

I've updated all my drivers (2 of about 30 were not the absolute latest driver) and removed my (non-MS) antivirus.

I have run every diagnostic I can find - all pass.

Nothing has made a difference.

Other than if I restart after about 1pm, it doesn't BSOD until the next day. Today, I rebooted around noon, and it BSOD'd later - say 4pm.

It did not do this under Windows 7.

Very odd.

wondering how you resolved this problem?

joe, my question about turning off the internet is prompted by numerous complaints by W7 owners who get lockups from the ceip data uploads back to MS from the 4 updates i quoted in the W8.1 thread. these started in 7 and 8 even before 10, and no matter what steps are taken to block MS from uploading diagnostics and telemetry (most call it spying), the scheduled data uploads continue to initiate and then crash.

maybe users' attempts to stop these KBs are conflicting w/ MS's override actions? i thought the software might reschedule the data transfer to MS if it sees no internet.

ReadyToGo wrote:
I did a search on bsod and time. Found one that suggested Norton AV doing a check for updates. This goes along with others suggestion about sonething starting up.

You may be on to something. When is Norton set to do a daily scan? I've heard of BSOD when AV scans certain system files in the past. You may want to try another FREE AV software as a check to see if you have the same issues. Panda AV Free and Bitdefender Free are highly rated. You can always re-install Norton as you have a valid license.

I doubt its some hardware issue as it wouldn't know to fault exactly the same time each day.

BSOD can cause the critical Kernal Power message, so that in itself is not the cause. It just means that WIN didn't cleanly shutdown. What happened before that 2:20 critical log message?

joebedford wrote:
Well, here's a hint - the log event at 2:21 says the crash was actually at 1:45. I know for a fact that the system was still running until 2:21 but maybe something broke about a half hour before and didn't take out the system until later??? I know the BSOD dump says something like "this program was running when the crash occurred but may not have caused the corruption". Maybe time to refocus my investigation to 1:45.



BTW, yesterday I rebooted at 12:26 (just under 2 hours before zero hour) and machine ran just fine - no BSOD.

That error marked CRITICAL at 2:20 in the event viewer is most likely the cause which trips the "bugcheck" then the BSOD..

You will note that the critical error mentions KERNAL-POWER, this could be anything from the system board going to sleep, hybernate, faulty power supply, bad memory (drivers are loaded into memory and bad memory can corrupt the drivers in that memory), bad MB caps and so on..

Potentially Win10 may even have a compatibility issue with Power management of your system board since as you say it was working fine when you had Win7 running on it..

1492 wrote:
Did you check if any WIN service is set to run @2:21 pm in Services? If you're not going to do so, then check Event Viewer, and find the log entry for BSOD listed at 2:21 pm. What does it say? Could be some faulty system or hardware driver being called at the same time each day?

Services doesn't list any scheduled activities.

Task scheduler lists lots, but none around BSOD time.