BSOD even after updating graphics drivers!!

[hungryrag]

Hi guys,
I've been using windows 10 on my desktop for couple of months now, it was running smoothly. But for the past few day I've been getting BSOD. I did my research and narrowed it down to windows update, outdated BIOS or outdated graphics driver. First I reset my pc but the problem still was there so then I got the latest BIOS update(my motherboard is gigabyte ab350-gaming 3) and also got the latest graphics driver from Nvidia(my card is GTX 1060 6gb). But even after all this, I'm still facing BSOD. So, I installed bluescreenview and got the following:

101017-4578-01.dmp 10-Oct-17 11:46:20 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 ffff9f00`b9313d40 81000002`6cb56867 ffffa202`7d6068f0 ntoskrnl.exe ntoskrnl.exe+16c580 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.674 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c580 C:\WINDOWS\Minidump\101017-4578-01.dmp 12 15 15063 726,084 10-Oct-17 11:47:13 PM

101017-5578-01.dmp 10-Oct-17 11:16:40 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 ffffd680`bf295980 87000002`6c8ac867 ffffa68a`4651eaa0 ntoskrnl.exe ntoskrnl.exe+16c580 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.674 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c580 C:\WINDOWS\Minidump\101017-5578-01.dmp 12 15 15063 786,980 10-Oct-17 11:17:27 PM

101017-4937-01.dmp 10-Oct-17 11:01:18 PM APC_INDEX_MISMATCH 0x00000001 00007ffa`bc9b5804 00000000`00000000 00000000`0000ffff ffff9a81`7b1ceb80 ntoskrnl.exe ntoskrnl.exe+16c580 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.674 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c580 C:\WINDOWS\Minidump\101017-4937-01.dmp 12 15 15063 710,244 10-Oct-17 11:02:11 PM

101017-4609-01.dmp 10-Oct-17 10:33:52 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffff922d`50852ca0 00000000`00000000 ffff920a`ec8ce311 00000000`00000002 hal.dll hal.dll+1c986 Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.502 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c580 C:\WINDOWS\Minidump\101017-4609-01.dmp 12 15 15063 822,036 10-Oct-17 10:34:26 PM

101017-4640-01.dmp 10-Oct-17 10:06:15 PM BAD_POOL_HEADER 0x00000019 00000000`0000000e ffff8b0a`ff9b80a0 ae9bd5df`9b762051 ae9bd5df`bb762051 ntoskrnl.exe ntoskrnl.exe+16c580 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.674 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c580 C:\WINDOWS\Minidump\101017-4640-01.dmp 12 15 15063 780,668 10-Oct-17 10:06:45 PM


P.S: I also ram a memory test using the windows memory diagnostic tool but found no errors.
Please help me resolve this issue.
Thank you all, looking forward for your answers.

 

[Colif]

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

Try running memtest86 (free version) on your ram, 1 stick at a time. Any errors are too many, only score you want is 0. Anything higher and need to replace the stick

those could be memory errors or just drivers

can you go to c:\windows\minidump
copy files to desktop
upload copies from desktop to a file sharing web site and share a link here

 

[hungryrag]

The previous problem was solved by resetting the ram to default frequency, but today I again faced BSOD. You can find the dump files in the link below:

https://www.dropbox.com/sh/g5epqgmdxf65fnn/AADusEThAsIMQ22OBSrjexVSa?dl=0

Thanks for the help.

 

[gardenman]

Hi, I'm having problems with the debugger and the recent dump files. It might be that the latest Windows update has messed things up. I was able to get a little info from the first dump file and that was it. Maybe this will help, maybe not.

101317-5250-01.dmp

*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000080000028
Arg2: 0000000000000002
Arg3: 0000000000000000n
Arg4: fffff808aa713a23

I can't help with this. Wait for more answers from others. Good luck.

 

[axe0axe0]

The dumps are corrupted.

Run the memtest Colif suggested.

 

[johnbl]

try to run the windows updates. the debugger complained about a old netio.sys file.
I can not tell if it is old because all of the dates are messed up in the debugger.

you might consider running cmd.exe or powershell as an admin then
turn on verifier functions to check for driver problems.

verifier.exe /standard /all
then reboot, and wait for the next bugcheck.
note: be sure you know how to get into safe mode so you can turn off verifier when done testing. via
verifier.exe /reset

 

[Colif]

Driver verifer tends to get you stuck in boot loops

driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.
note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again. Also helps to run system restore before hand to create a backup to roll back to if necessary. Download the Windows 10 media creation tool and use it to make a win 10 installer on USB

The instructions to stop it looping are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode
Now open command Prompt
type verifer /reset and press enter
restart PC