Windows 10: BSOD watching video

Running Win 10 pro 64 bit 14393.105
new build intel i7 6770k
ASUS Z170 pro gaming
【Kingston】HyperX Predator DDR4 DDR4-3333 8GBx2枚 1.35V

This is the 2nd time I have had a BSOD in the last couple of days. It's pretty hot in Japan right now. Might be a heat issue, but I don't know.

please advise,

Thanks
Sam

more crashes, added new file documenting those too

:)

 

"WHEA_UNCORRECTABLE_ERROR" BSOD while watching video in browsers (Google Chrome, Mozilla Firefox)

Here are the bsod_minidumps, MSInfo32_export, Speccy_export.

It's very strange that this behaviour is random - it appears from time to time. Sometimes I watch video and there is nothing, sometimes there are several BSODs in a row. I didn't find a straight corellation between watching videos in a browser and BSODs,
but I have noticed that BSOD doesn't appear when I do all the other things (watching video in a local desktop player, playing games, working with Office, etc.).

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (Netwbw02.sys)

BSOD while using Youtube or watching videos on IE or Chrome. I'm using Windows 10. I bought Dell i7567 Inspiron. I had this BSOD and got my laptop replaced. After one week of use the new laptop has same BSOD. This happens only while watching Videos.

I tried reinstalling OS, Updating Drivers, contacted Dell and they updated drivers manually and nothing has worked. Any idea on how to resolve this ?

 

don't know if I should keep updating the zip file as I get more BSOD or not.... keeps happening.

 

Three of the dumps show
Code: BugCheck D1, {0, ff, e1, 0} Probably caused by : Unknown_Image ( nt!KiPageFault+247 )[/quote] the other
Code: BugCheck A, {b0, ff, b7, fffff80053621627} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+247 )[/quote] All 4 are
Code: IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.[/quote] Start by testing your PC memory:
===================================================
RAM:

Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums



Information


MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

If nothing found then try Driver Verifier, see if it shows us anything:
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to


PART TWO


and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.

 

11 passes with memtest 86+ and no errors

Loaded verifier according to the instructions and got a BSOD on my first boot attempt. 2nd time booted into OS. Don't know where to look for a report from verifier to upload. I ran the initial diagnostic again.

 

The dump indicates a problem with AsIO.sys.
Code: BugCheck 1A, {1233, bdf8c, 0, 0} *** WARNING: Unable to verify timestamp for AsIO.sys *** ERROR: Module load completed but symbols could not be loaded for AsIO.sys Probably caused by : memory_corruption[/quote] The one installed is very old: Wed Aug 22 05:54:47 2012

Stop it in Services and see if that allows you to boot with Verifier active.

 

I think the BSODs might have been caused by awebCam driver problem that's happening with the new Microsoft anniversary update. I've unplugged my USB from my WebCam, uninstall the software, and haven't had a BSOD since

 

That's good to know. Hope that's it.
Is there a driver update for it?

 

Not that I know of. People with advanced preview versions of Windows 10 pro say that there's a fix, but those of us who don't have that yet don't have a fix

 

Hopefully the fix will get rolled out in one of the updates to teh Anniversary edition.

 

Yeah me too. Funny, all the stress tests I was doing on my new overclock that failed before, are now working fine. So that's nice to know

 

Well that was too good to be true. I guess the computer had a BSOD while I was asleep last night....woke up and everything was back to initial login stage... Here's the report.

I have the webcam USB unplugged.

What should I do at this point?

 

I can run verifier for all non-Microsoft items now. Logged in and running it currently.

 

The latest dump infdicates a problem with dfsc.sys
Code: BugCheck A, {b0, ff, e5, fffff8034664e627} *** WARNING: Unable to verify timestamp for dfsc.sys *** ERROR: Module load completed but symbols could not be loaded for dfsc.sys[/quote] This belongs to Microsoft Distributed File System Namespace Client. Unlikely to be the actual cause of a problem.
I know nothing about it other than what I can find via Google. DFS and AD (Active Directory) work together. What each does I have no idea. Maybe this is pointing to a possible hard drive problem. Might want to test it:
===================================================


HDD Test





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

Run the following tests

• Short Drive Self Test
• Short generic
• Long generic

If the short generic fails, no need for the long generic.



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

Post screenshots/photos of the test results