Blue screen of death.

[imanyenkov]

Hey Guys,
I have been looking into this problem for a long time already and it seens that i can not pin point the problem.
As the title says, i am having issues with BSOD.

i have i7- 4790k, Gigabyte Z97x - gaming 5 Mobo, MSI GTX-970 GPU and 2 8 Gig RAM.

It mainly happens while chrome is on and rarely when i wake up the PC. I suspected that it might be the Mobo or the CPU but i i still have no clue.

Thanks for the help in advance.

 

[CountMike]

Make note of message at the bottom of blue screen of what caused it. Without it can't even start guessing.
This: http://www.majorgeeks.com/files/details/whocrashed_free_home_edition.html can also show what it was.

 

[jr9]

If you can find a crash dump file in C:\Windows\Minidump and upload it, it can tell us a lot about what is causing the crashing.

The most common cause of BSOD on gaming machines is malfunctioning graphics card drivers. You don't even have to be gaming for them to crash your PC. Updating them is a good idea.

 

[imanyenkov]

Make note of message at the bottom of blue screen of what caused it. Without it can't even start guessing.
This: http://www.majorgeeks.com/files/details/whocrashed_free_home_edition.html can also show what it was.

Thank you for the reply, as you know now my PC won't crash so i can not see what's the cause but as soon as i'll have i can give more info.
I downloaded what you suggested and try to see what might be the problem.

 

[jr9]

As a side note, if you get a crash and then load that program and see no dump files, then you need to enable crash dump logging.

Windows key -> sysdm.cpl -> Enter -> Advanced tab -> Startup and Recovery area, settings -> Write debugging information to 256KB small memory dump -> OK -> OK on previous page

 

[imanyenkov]

so my PC crashed after trying to wake him up and i got this...

from Windows its this:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80003121292
BCP3: FFFFF8800D1AF858
BCP4: FFFFF8800D1AF0B0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

from the WhoCrashed software it's this:

On Thu 15/03/2018 19:26:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031518-7222-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x10D292)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003121292, 0xFFFFF8800D1AF858, 0xFFFFF8800D1AF0B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 15/03/2018 19:26:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlGetNextRange+0x334)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80003121292, 0xFFFFF8800D1AF858, 0xFFFFF8800D1AF0B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




any clue to how to continue? i have been reading some threads but they lead to verious things.

 

[jr9]

That won't tell you anything. The Windows debugger blamed ntoskrnl.exe which tells you basically nothing. Since WhoCrashed works though that means the log files are there and you can access and upload some. We'd need a copy of the dmp file to have a chance at seeing what's going on by running them through a proper debugger. Sometimes WhoCrashed tells you the culprit but other times you have to dig deeper.

 

[imanyenkov]

That won't tell you anything. The Windows debugger blamed ntoskrnl.exe which tells you basically nothing. Since WhoCrashed works though that means the log files are there and you can access and upload some. We'd need a copy of the dmp file to have a chance at seeing what's going on by running them through a proper debugger. Sometimes WhoCrashed tells you the culprit but other times you have to dig deeper.

ok, i am trying to figure out how to find it and post it, sorry that it take time but it's hard for me.
is this right?

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23796.amd64fre.win7sp1_ldr.170427-1518
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`03294730
Debug session time: Thu Mar 15 23:07:15.993 2018 (UTC - 4:00)
System Uptime: 0 days 13:02:13.789
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880017a0cd6, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fe100
GetUlongFromAddress: unable to read from fffff800032fe1c8
0000000000000028 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
NETIO!NetioAdvanceNetBufferList+26
fffff880`017a0cd6 3b4828 cmp ecx,dword ptr [rax+28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: vsserv.exe

TRAP_FRAME: fffff80000b9f930 -- (.trap 0xfffff80000b9f930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000030
rdx=0000000000000030 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880017a0cd6 rsp=fffff80000b9fac0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffffa800cfce280
r11=fffff80000b9fb10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
NETIO!NetioAdvanceNetBufferList+0x26:
fffff880`017a0cd6 3b4828 cmp ecx,dword ptr [rax+28h] ds:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030c0a69 to fffff800030c14c0

STACK_TEXT:
fffff800`00b9f7e8 fffff800`030c0a69 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9f7f0 fffff800`030bf6e0 : 00000000`00000002 fffffa80`14a26280 fffff800`00b9fb30 fffffa80`12b63970 : nt!KiBugCheckDispatch+0x69
fffff800`00b9f930 fffff880`017a0cd6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9fac0 fffff880`0189626b : fffffa80`12b63840 00000000`00000000 00000000`00000030 fffffa80`0e0cfd50 : NETIO!NetioAdvanceNetBufferList+0x26
fffff800`00b9faf0 fffff880`018847b7 : 00000000`00000000 fffffa80`0e0cfd50 fffffa80`0e0cfd50 00000000`00000001 : tcpip!WfpPreprocessInboundMcastBcastIndication+0x47
fffff800`00b9fb20 fffff880`0185f008 : fffffa80`00000011 fffff800`00b90017 fffffa80`1264eb14 00000000`00007ef6 : tcpip!WfpProcessInTransportStackIndication+0x207
fffff800`00b9fcb0 fffff880`01888bc9 : 00000000`00000028 fffffa80`0d037820 00000000`00000000 fffff880`018898b4 : tcpip!InetInspectReceiveDatagram+0x1d8
fffff800`00b9fd50 fffff880`018892d4 : fffffa80`0d1e5c60 fffffa80`124a4440 fffffa80`0d432a00 00000000`00000000 : tcpip!UdpBeginMessageIndication+0x89
fffff800`00b9fe70 fffff880`018833de : fffffa80`0ca13000 00000000`00000028 fffffa80`00000000 fffff800`00b9ffa0 : tcpip!UdpDeliverDatagrams+0x2f4
fffff800`00b9ff50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!UdpReceiveDatagrams+0x18f


STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!NetioAdvanceNetBufferList+26
fffff880`017a0cd6 3b4828 cmp ecx,dword ptr [rax+28h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: NETIO!NetioAdvanceNetBufferList+26

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 58e3b357

FAILURE_BUCKET_ID: X64_0xD1_NETIO!NetioAdvanceNetBufferList+26

BUCKET_ID: X64_0xD1_NETIO!NetioAdvanceNetBufferList+26

Followup: MachineOwner

 

[jr9]

The file that you uploaded to that site, you can take the dmp file also also upload it to a place like OneDrive so we can look at it ourselves. What's posted there doesn't tell everything. Based on that piece of information, I would consider using Display Driver Uninstaller to remove your display drivers in safe mode. After that, boot into normal Windows and reinstall them. Only install your display drivers and Physx and leave everything else unselected.

 

[imanyenkov]

The file that you uploaded to that site, you can take the dmp file also also upload it to a place like OneDrive so we can look at it ourselves. What's posted there doesn't tell everything. Based on that piece of information, I would consider using Display Driver Uninstaller to remove your display drivers in safe mode. After that, boot into normal Windows and reinstall them. Only install your display drivers and Physx and leave everything else unselected.

ok, so i uploaded the file and here is the link :
https://1drv.ms/u/s!AshN7xMGudB6gUgdTWlDRArSEXMR
does this help?
but how come i need to uninstall the display graphics, is that what might cause the problem?
if it does then i'll uninstall.

 

[jr9]

The most common cause of this type of error is a malfunctioning graphics card driver or software conflict.

 

[imanyenkov]

The most common cause of this type of error is a malfunctioning graphics card driver or software conflict.

I'm so sorry for nagging you but i can not enter Safe mode without it crashing....
i'm trying to find articales about why but i don't seem to find why..

 

[jr9]

If it crashes when you try to enter safe mode through advanced boot options menu (F8) then display drivers likely aren't to blame for the issue as nVIDIA display drivers aren't loaded in safe mode as well as all startup items. Safe mode crashes are generally either caused by OS corruption or failing hardware. DDU can also be run in normal Windows although it's less effective that way so I would try that. If you cannot get into either normal or safe mode, I'd consider simply backing up and reinstalling Windows. If it crashes after a Windows reinstall then it is definitely a hardware issue.

 

[imanyenkov]

If it crashes when you try to enter safe mode through advanced boot options menu (F8) then display drivers likely aren't to blame for the issue as nVIDIA display drivers aren't loaded in safe mode as well as all startup items. Safe mode crashes are generally either caused by OS corruption or failing hardware. DDU can also be run in normal Windows although it's less effective that way so I would try that. If you cannot get into either normal or safe mode, I'd consider simply backing up and reinstalling Windows. If it crashes after a Windows reinstall then it is definitely a hardware issue.

Thank you for the reply.
I will try to to uninstall with DDU on normal mode.
You might be right about the hardware, I have a hard drive which is old and I think that it might be the problem. I unplugged it and now I'll wait.
But in case the hard drive is not the issue could it be the Mobo or the CPU or I need to still try some test to see which hardware it is?
And if it's hardware then why it said in WhoCrashed that it's a driver issue?

 

[jr9]

With troubleshooting you want to start at the highest level and them go down methodically. User -> Application -> OS - > Hardware. Right now we are at application/OS. If stripping out the drivers doesn't work then you can either troubleshoot Windows with methods like diagnostic startup mode or CHKDSK or various other quick fix tools. I think it would be easier to reinstall Windows if it crashes in safe mode with no GPU drivers. Another alternative to this is to install Windows on another drive, boot from that, and see if it crashes. After a Windows reinstall is complete and it still crashes, that means you are at the lowest level which is hardware as a new OS eliminates application and OS.

All WhoCrashed tells you is what Windows blamed for the crash. Often it gets it wrong (NTOSKRNL being the most notable example). My more advanced debugger only can give me clues sometimes and mine pointed towards an application misusing NETIO.SYS.

 

[imanyenkov]

With troubleshooting you want to start at the highest level and them go down methodically. User -> Application -> OS - > Hardware. Right now we are at application/OS. If stripping out the drivers doesn't work then you can either troubleshoot Windows with methods like diagnostic startup mode or CHKDSK or various other quick fix tools. I think it would be easier to reinstall Windows if it crashes in safe mode with no GPU drivers. Another alternative to this is to install Windows on another drive, boot from that, and see if it crashes. After a Windows reinstall is complete and it still crashes, that means you are at the lowest level which is hardware as a new OS eliminates application and OS.

All WhoCrashed tells you is what Windows blamed for the crash. Often it gets it wrong (NTOSKRNL being the most notable example). My more advanced debugger only can give me clues sometimes and mine pointed towards an application misusing NETIO.SYS.

Again, Thank you for the fast reply.
as for reinstalling the OS i did it a year ago and i still have the problem so it might be some hardware.
give me a few days to try and do all the checks and i'll get back to you.

 

[jr9]

Some things to try if it crashes after a new Windows installation:

- Don't let Windows updates download. Sometimes they are to blame for problems
- Try removing the graphics card and just using the integrated graphics (motherboard video ports)
- Run MEMTEST86 from a bootable flash drive or CD/DVD. It's featured in Ultimate Boot CD.
- If you have multiple hard drives, try disconnecting the ones that are not essential (non OS drives)

 

[johnbl]

most likely a bug in this driver:
Killer e2200 PCI-E Gigabit Ethernet Controller
e22w7x64.sys Wed Mar 20 14:35:41 2013
look here under the lan driver for the update:
https://www.gigabyte.com/Motherboard/GA-Z97X-Gaming-5-rev-10#support-dl
you should also pick up other updates they provide

best to go to the gigabyte website and get a update or maybe look at the killer website:
https://www.killernetworking.com/driver-downloads

machine info:
BIOS Version F6
BIOS Starting Address Segment f000
BIOS Release Date 04/21/2015
Manufacturer Gigabyte Technology Co., Ltd.
Product Name Z97X-Gaming 5
Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4000MHz

 

[imanyenkov]

Some things to try if it crashes after a new Windows installation:

- Don't let Windows updates download. Sometimes they are to blame for problems
- Try removing the graphics card and just using the integrated graphics (motherboard video ports)
- Run MEMTEST86 from a bootable flash drive or CD/DVD. It's featured in Ultimate Boot CD.
- If you have multiple hard drives, try disconnecting the ones that are not essential (non OS drives)

so i'm still trying all the things and i unplugged my old hard drive but now i can not get into the advance boot options such as Safe Mode...it seems that it was there.

 

[imanyenkov]

most likely a bug in this driver:
Killer e2200 PCI-E Gigabit Ethernet Controller
e22w7x64.sys Wed Mar 20 14:35:41 2013
look here under the lan driver for the update:
https://www.gigabyte.com/Motherboard/GA-Z97X-Gaming-5-rev-10#support-dl
you should also pick up other updates they provide

best to go to the gigabyte website and get a update or maybe look at the killer website:
https://www.killernetworking.com/driver-downloads

machine info:
BIOS Version F6
BIOS Starting Address Segment f000
BIOS Release Date 04/21/2015
Manufacturer Gigabyte Technology Co., Ltd.
Product Name Z97X-Gaming 5
Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4000MHz

Thank you for the help.
Have you downloaded my dump file and manage to look at it?
I downloaded the Killer performance suite and then i downloaded the Bigfoot killer but it does not let me install it after i installed the Killer performance suite...it asks me to uninstall the Qualcomm.....so i'm going in circles...

 

[johnbl]

uninstall the killer performance software and install the lan driver from the motherboard vendor
then see if you still get the bugcheck.

yes, I got the info from the memory dump. old versions of the killer driver tend to have lots of problems.

most likely a bug in this driver:
Killer e2200 PCI-E Gigabit Ethernet Controller
e22w7x64.sys Wed Mar 20 14:35:41 2013
look here under the lan driver for the update:
https://www.gigabyte.com/Motherboard/GA-Z97X-Gaming-5-rev-10#support-dl
you should also pick up other updates they provide

best to go to the gigabyte website and get a update or maybe look at the killer website:
https://www.killernetworking.com/driver-downloads

machine info:
BIOS Version F6
BIOS Starting Address Segment f000
BIOS Release Date 04/21/2015
Manufacturer Gigabyte Technology Co., Ltd.
Product Name Z97X-Gaming 5
Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4000MHz

Thank you for the help.
Have you downloaded my dump file and manage to look at it?
I downloaded the Killer performance suite and then i downloaded the Bigfoot killer but it does not let me install it after i installed the Killer performance suite...it asks me to uninstall the Qualcomm.....so i'm going in circles...

 

[imanyenkov]

Hey guys. sorry for the late response.
I have been waiting for the BSOD and i still didn't get it.
I have plugged out my old hard driver out and after sorting some old files i have all the files on another hard driver after that i have also updated the Lan driver but that was a pain in the ass because the driver in Gigabytes website is from 2016 while the one from the Killer website is from 2017 so i updated to 2017 and for now everything seems to work. now i can put the PC on sleep mode without it waking up randomly or restarting due to BSOD.