Windows 10: BSOD on Windows 10 after about 10 minutes idle, cyclic if unattended

Hello fellow members,

Since upgrading my vanilla Lenovo desktop to Windows 10, it freezes about 2 times per workday. The mouse won't move but the cursor is visible. The Caps Lock, Scroll Lock and Num Lock buttons won't toggle the keyboard indicators. I never get to a BSOD. The system needs a hard reset. No error events show up in Event Viewer. Windows Memory Diagnostic reports no issues. The CPU is under light load and nothing overheats on the motherboard.

However, since either KB3099406 or KB3097617 was intalled by Windows Update, the system BSODs every 10 minutes when unattended. My first reaction was to go to Power Options and choose the High Performance plan, removing all delayed power offs, but it still dies every 10 minutes. BSODs won't occur if I keep the system busy, but then it will eventually freeze as described above.

Thanks in advance for your suggestions. Here's my last ditch effort before I reinstall Windows 7, which worked flawlessly.

DM Collector logs: Attachment 43233.

Cheers,
.

:)

 

Windows 10 x64 BSOD irql not less or equal

Hi there!

I have Lenovo T460s UltraBook with Windows 10 x64 onboard and the same problem but...

BSOD's shows up in very random times. All my drivers are up to date (updated today from official Lenovo site).

Computer starts normally works fine and... BSOD. Last one was few minutes ago. Computer was idle. I've started Windows after BSOD, logged in and did nothing. After 3 or 4 minutes Windows crashed with BSOD.

All factory diagnostics passed.

Memory dump is here:

https://1drv.ms/u/s!An3BHu_b5TxXiP1kZ9m_ZWe-rJdRaQ

I hope that someone can help me.

Regards

SK

 

BlueScreen (system_service_exception) happening everytime my computer is idle

Everytime my computer is idle it gets a BSOD after a few minutes. It is running Windows 10. I don't think it is releated to sleep beacuse sleep is set to 'Never'. I have updated my NVIDIA drivers.

I uploaded a minidump file: https://db.tt/l00o3Xyo

Thanks for any help with this issue.

Bengt

 

Hi excelosaurs,

Welcome to the 10forums.

The 0x3B(SYSTEM_SERVICE_EXCEPTION) is usually caused by 3rd party drivers, there are however almost no drivers dating earlier then 2015.
A driver called point64 is dating 2013 and the only one not in 2015, please check Microsoft for driver updates.
Code: point64 point64.sys Thu Dec 12 14:16:17 2013 (52A9B721)[/quote]




Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Thanks. Update:

• point64.sys is at the latest version.
• Driver Verifier (DV) activated as per the linked tutorial. Note: since doing that, I've left my computer unattended on several occasions and it never BSOD'd. Will check back here after max 48 hours of DV. Also note that the system is performing nominally even with DV.

 

I'm having the same problem, (shut down every 10 minutes when idle) and have not been able to find a solution. I don't know if Driver Verifier will help. I believe DV will keep your machine from going idle since it is stressing the drivers.

 

Please read How to upload files

 

GaxUser,

24 hours into Driver Verifier, the system hasn't BSOD'd; it just froze once. Here are the drivers that DV verifies on my system. Anything in common with yours?

dump_diskdump.sys
dump_dumpfve.sys
dump_storahci.sys
e1i63x64.sys
hecix64.sys
igdkmd64.sys
ndis.sys
rtkvhd64.sys
vboxdrv.sys
vboxnetadp6.sys
vboxnetlwf.sys
vboxusbmon.sys

Thanks and good luck,
.

 

Yep, that is how verifier acts and why it is recommended to not use the PC activily.

 

I didn't run verifier since it seemed like a foolish suggestion. I will tell you what I did to work around the problem.
It seems that something is running after being in an idle state for 10 minutes that fails and you get the blue screen. Like you my first thought was to disable sleep. However, this is exactly the wrong thinking. What I did was tell the computer to go to sleep after 9 minutes, thereby short circuiting the nasty little bugger that's going to turn off the computer in a minute. Obviously not a real solution but good enough for me.

 

Why do you think that?

 

Update:
48 hours into Driver Verifier configured as requested, the system has not BSOD'd; it just froze solid twice, once under light load, and once at night after 4 hours of zero load. What I'd intuitively try now would be to run DV on each individual driver among those in the 1st run, trying to find which stress test makes the system work. But any suggestions are welcome.

 

That would be too much time consuming.

As you say it started when updates are installed, it is an option to check your system files.

 

sfc run as described, results attached.
Attachment 43954

 

I cannot find any problems, did SFC report that it couldn't solve violations?