Windows 10: BSOD when playing youtube videos (SYSTEM_SERVICE_EXCEPTION)

Thanks, all of my drivers were actually installed from my motherboards website very recently, I did uninstall all of the failing ones however (got a BlueScreenView so I could fallow through) except for the nvidia driver because I really need it. My system boots now with the verifier on and all drivers except for nvidia graphics driver checked.

I will post again when I see another blue screen, for now here is the latest log dump.

 

How long are you running driver verifier?

 

Nvidia audio driver has caused the 2 most recent crashes.
Code: *** WARNING: Unable to verify timestamp for nvhda64v.sys *** ERROR: Module load completed but symbols could not be loaded for nvhda64v.sys 11: kd> lmvm nvhda64v start end module name fffff801`844f0000 fffff801`84524000 nvhda64v T (no symbols) Loaded symbol image file: nvhda64v.sys Image path: \SystemRoot\system32\drivers\nvhda64v.sys Image name: nvhda64v.sys Timestamp: Thu Apr 16 21:03:16 2015 (55300774) CheckSum: 0003E696 ImageSize: 00034000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Update link
Nvidia audio driver

 

I first started it on 10/30/2015 around 11:30 after I got my System_service_exception BSOD.

I am still running it, but I was not using my computer much after resolving all the Driver_verifier_detection_violation failures since I was fast asleep.

Before I ran verifier my blue screens were a few days apart so it might be a while until I hit another one.

In other words the first 3 dumps (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED; MEMORY_MANAGEMENT and SYSTEM_SERVICE_EXCEPTION) happened prior to me running a verifier.

 

Updating nvidia drivers still fails the to boot with verifier. *Sad

I also got this massege when rebooting (during the windows shutdown screen)

"explorer.exe

The instruction at 0x..... reference memory at 0x .....

The memory could not be read.

Does that shed some light on my problem ??

 

I have seen that quite some times, it means either driver problems or hardware problems, not really that clear.
Please test your memory using MemTest86+





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

I ran 11 passes of memtest86 last night ... no errors *Sad

 

Please disable driver verifier

• Open an admin command prompt
• Enter "verifier/reset" (without quotes)

 

Done. I will post again once I see a new issue.

 

Took a while but I got a brand new BSOD *Sad

 

Update following Logitech drivers
Driver Reference Table - lvuvc64.sys
Driver Reference Table - lvrs64.sys
Driver Reference Table - lvbflt64.sys

 

I did download the latest drivers from logitech website couple of days ago *Sad

I unplugged my webcam and uninstalled all of the drivers for now to eliminate this as a possible source of errors.

 

As this installation is an upgrade from Windows 7, it is an option to do a clean install.
With an upgrade, Windows is installed above another Windows, this causes problems and is also the reason why there is a folder 'Windows.Old' created.
Windows 10 - Clean Install - Windows 10 Forums

 

Hey I did a clean install of windows on thursday ... got a new bsod today.

New logs attached.

 

A 0x1A with hardware module name
Code: SYMBOL_NAME: ONE_BIT FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: memory_corruption[/quote] Please verify the voltage and frequency values of the RAM are as they should be in the BIOS.






Diagnostics Test

HDD & SSD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk Disk Check - Windows 7 Help Forums

If all above hasn't helped, try running driver verifier.
Read the instructions carefully!





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.