Windows 10: BSOD Intermittent when turning PC on

Hello,

I've been having BSODs intermittently for a while now, as far as I can remember they just happen when my PC is booting up. I have tried to pinpoint the problem using Whocrashed software to no avail. At the beginning the software was identifying a Panda antivirus driver as the culprit, I uninstalled Panda and installed Avira. When I run the analysis it says it was not able to determine the culprit, even with Windows collecting full dumps.

Once the computer has booted successfully I haven't had any problems or BSODs. I am able to run memory and processing intensive software without any issues. Let me know if you need any further information.

Thank you,

:)

 

No help with fixing KB4013418 update!!

Robear

Opened new thread....

Intermittent BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL

It should be located at......



Intermittent BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL



The further I look at this thing the uglier it gets.

 

Too many BSODS to count... Pointing towards memory corruption.

Well, when I run verifier, no .dmp files are saved. Not in the minidump folder or where MEMORY.DMP is located.

When my pc bsods when using verifier, It bsods before my pc loads into windows. About 7 seconds into the bios loading screen is when it bsods. If I put my pc into safe mode with verifier turned on, it doesn't bsod.

 

Latest dump indicates a problem with jnprns.sys.
Code: ffffdc81`4fc999b8 fffff802`fea68f95*** WARNING: Unable to verify timestamp for jnprns.sys *** ERROR: Module load completed but symbols could not be loaded for jnprns.sys jnprns+0x8f95[/quote] Driver Description: Juniper Network Agent driver
Driver Update Site: Download Software - Support - Juniper Networks
The one you have is fairly old: 10/30/2014 2:38:20 PM C:\WINDOWS\system32\DRIVERS\jnprns.sys
Code: Name [00000000] Juniper Networks Virtual Adapter Manager Adapter Type Not Available Product Type Juniper Networks Virtual Adapter Manager Installed Yes PNP Device ID ROOT\JNPRVAMGR\0000 Last Reset 3/20/2017 12:18 PM Index 0 Service Name IP Address Not Available IP Subnet Not Available Default IP Gateway Not Available DHCP Enabled No DHCP Server Not Available DHCP Lease Expires Not Available DHCP Lease Obtained Not Available MAC Address Not Available Driver c:\windows\system32\drivers\jnprvamgr.sys (5.2.0.6009, 44.29 KB (45,352 bytes), 2/12/2016 9:36 AM)[/quote] Update or revmove it, see if that resolves the problem.

 

Thank you for the fast reply. That driver was a vestige of an old virtual network adapter software, which was previously uninstalled. Went ahead and removed all traces of it. It usually takes a couple of boots for the problem to appear, so I'll keep you posted if anything comes up. So far I have restarted a couple of times without getting a BSOD.

 

After a couple of weeks without any issues, today I got a BSOD when starting Windows. I have attached the zip files with the log.

Thank you,

 

Nothing useful in the new dump, but I did find this in the event log:
Code: Event[28007]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-04-10T12:36:32.950 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Darth-Helmet Description: Windows failed fast startup with error status 0xC0000001.[/quote] Disable Fast Startup. see if that makes any difference: How to Turn On or Off Fast Startup in Windows 10

See this article on HowToGeek.com: The Pros and Cons of Windows 10’s “Fast Startup” Mode

 

Thank you, that fixed the problem for a while. After the latest Windows 10 updates, I have new crashes during boot up. Attached is my zip file.

Thank you so much for all the help

 

Looks like Fast startup got enabled with the update:
Code: Event[1400]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-04-30T12:22:20.531 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Darth-Helmet Description: Windows failed fast startup with error status 0xC0000001.[/quote] Disable Fast startup again and see if that helps.