Hey everyone, first post. I apologize in advance; I've looked everywhere for an answer.
The problem first started last weekend with a BSOD while Hitman Absolution stopped responding. I tried opening task manager to quit the program, and the blue screen popped up.
Fast forward, with random blue screens every day. The surest way to reproduce the blue screen is by opening up Task Manager immediately after logging in to the account. The task manager will "hang" with a loading circle for about 2 seconds, before blue screening. This happens 7/10 times with opening the task manger.
The other way to reproduce the blue screen is to open a ton of applications all at once (Steam, Origin, Chrome, etc.).
I did a re-install of Windows 8.1 today and the blue screens went away until I did windows update.
Here is an excerpt of WhoCrashed logs. Minidump files available through PM. Thanks in advance!
Edit: I only have Microsoft Defender; it's a new computer (less than 2 months), I'm very careful, and I would VERY surprised if there was malware. No torrent programs running, ever. I updated my LAN driver and wifi drivers (I'm on ethernet) through the Asus Maximus 7 Impact official product page, and also updated the BIOS. still crashes.
Edit2: I've also found that the GeForce Experience has gone completely crazy. It won't detect any of the games I have on the computer anymore, and it always crashes when I try to open it up from the tray minimized. I suspect it has to do with the update search connecting to the internet, causing a tcpip.sys crash. However, a search on incompatibilities yields nothing.
----------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: ====
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VII IMPACT
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8530198528 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 3/19/2015 8:35:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031915-7250-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x4BAC2)
Bugcheck code: 0xD1 (0x3C, 0x2, 0x1, 0xFFFFF800638A7AC2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 3/19/2015 12:29:58 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031815-10531-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF800420667B7)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF800420667B7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
10 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
The problem first started last weekend with a BSOD while Hitman Absolution stopped responding. I tried opening task manager to quit the program, and the blue screen popped up.
Fast forward, with random blue screens every day. The surest way to reproduce the blue screen is by opening up Task Manager immediately after logging in to the account. The task manager will "hang" with a loading circle for about 2 seconds, before blue screening. This happens 7/10 times with opening the task manger.
The other way to reproduce the blue screen is to open a ton of applications all at once (Steam, Origin, Chrome, etc.).
I did a re-install of Windows 8.1 today and the blue screens went away until I did windows update.
Here is an excerpt of WhoCrashed logs. Minidump files available through PM. Thanks in advance!
Edit: I only have Microsoft Defender; it's a new computer (less than 2 months), I'm very careful, and I would VERY surprised if there was malware. No torrent programs running, ever. I updated my LAN driver and wifi drivers (I'm on ethernet) through the Asus Maximus 7 Impact official product page, and also updated the BIOS. still crashes.
Edit2: I've also found that the GeForce Experience has gone completely crazy. It won't detect any of the games I have on the computer anymore, and it always crashes when I try to open it up from the tray minimized. I suspect it has to do with the update search connecting to the internet, causing a tcpip.sys crash. However, a search on incompatibilities yields nothing.
----------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: ====
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VII IMPACT
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8530198528 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 3/19/2015 8:35:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031915-7250-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x4BAC2)
Bugcheck code: 0xD1 (0x3C, 0x2, 0x1, 0xFFFFF800638A7AC2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 3/19/2015 12:29:58 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031815-10531-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF800420667B7)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF800420667B7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
10 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Facebook
Twitter
Instagram