Multiple Blue Screen Errors

Toggle sidebar Toggle sidebar
H

hawk424

Prominent
Jul 26, 2017
7
0
510
Hi, I have recently been getting multiple blue screen errors such as:
SYSTEM_SERVICE_EXCEPTION
PAGE_FAULT_IN_NONPAGED_AREA
KMODE_EXCEPTION_NOT_HANDLED
IRQL_NOT_LESS_OR_EQUAL
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

I have no idea how to fix these, and they have been occurring pretty often lately. Any help is greatly appreciated, thanks!
 
Sort by date Sort by votes
Colif

Colif

Win 11 Master
Moderator
Jun 12, 2015
65,261
6,464
168,090
1. Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do :)

2. Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here

someone with right software to read them will help you fix it :)
 
Upvote 0 Downvote
H

hawk424

Prominent
Jul 26, 2017
7
0
510



On Thu 7/27/2017 11:59:50 AM your computer crashed
crash dump file: C:\Windows\Minidump\072717-9843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5DAE8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801CF6DCAE8, 0xFFFFB60010132208, 0xFFFFB60010131A40)
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 7/27/2017 11:59:50 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF801CF6DCAE8, 0xFFFFB60010132208, 0xFFFFB60010131A40)
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.



On Thu 7/27/2017 11:53:06 AM your computer crashed
crash dump file: C:\Windows\Minidump\072717-6218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803909694C7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 Wed 7/26/2017 8:15:27 PM your computer crashed
crash dump file: C:\Windows\Minidump\072617-6765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)
Bugcheck code: 0x50 (0xFFFFC389F50268D8, 0x0, 0xFFFFF803590D8DE7, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Wed 7/26/2017 2:49:00 PM your computer crashed
crash dump file: C:\Windows\Minidump\072617-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8031A817C25, 0xFFFFA480A14D9DF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
 
Upvote 0 Downvote
gardenman

gardenman

Splendid
Moderator
Jun 16, 2016
4,250
495
26,090
Hi, I ran the 22 dump files through the debugger and got the following information: https://pastebin.com/A9gHpiw8

File: 072617-6765-01.dmp (Wed Jul 26 20:15:27.867 2017)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)] {ffffc389f50268d8, 0, fffff803590d8de7, 2}
Probably caused by: memory_corruption (Process: Steam.exe)

File: 072617-6796-01.dmp (Wed Jul 26 01:56:06.170 2017)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)] {c0000005, fffff8033b84acc2, ffff9c80739f9d70, 0}
Probably caused by: win32kfull.sys (Process: csrss.exe)

File: 072617-6968-01.dmp (Wed Jul 26 01:32:30.194 2017)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)] {ffffffffc0000005, fffff80240e4d5c1, ffff918193fa27f8, ffff918193fa2030}
Probably caused by: dxgmms2.sys (Process: System)

File: 072617-7406-01.dmp (Wed Jul 26 14:06:48.725 2017)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)] {c0000005, fffff8019c5b2680, ffffae0041e45e60, 0}
Probably caused by: memory_corruption (Process: TslGame.exe)

File: 072617-8484-01.dmp (Wed Jul 26 14:43:57.544 2017)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)] {3, fffff803663877f0, fffff80366387748, 0}
Probably caused by: ntkrnlmp.exe (Process: System)

File: 072617-9140-01.dmp (Wed Jul 26 01:29:26.467 2017)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)] {c0000005, fffff803c4036232, ffffd48036b59fb0, 0}
Probably caused by: memory_corruption (Process: audiodg.exe)

File: 072617-9421-01.dmp (Wed Jul 26 01:23:07.396 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)] {200000002, 2, 0, fffff8008deb472c}
Probably caused by: Unknown_Image (Process: System)

File: 072717-6218-01.dmp (Thu Jul 27 11:53:06.107 2017)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)] {ffffffffc0000005, fffff803909694c7, 0, ffffffffffffffff}
Probably caused by: memory_corruption (Process: chrome.exe)

File: 072717-9843-01.dmp (Thu Jul 27 11:59:50.375 2017)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)] {ffffffffc0000005, fffff801cf6dcae8, ffffb60010132208, ffffb60010131a40}
Probably caused by: memory_corruption (Process: chrome.exe)

File: 013017-4968-01.dmp (Mon Jan 30 16:22:47.787 2017)
BugCheck: [VIDEO_TDR_ERROR (116)] {ffffae8b48f273d0, fffff80a3763f284, 0, d}
Warning: Unable to verify timestamp for: atikmpag.sys
Probably caused by: atikmpag.sys (Process: System)

File: 020817-5312-01.dmp (Wed Feb 8 02:40:44.772 2017)
BugCheck: [VIDEO_TDR_ERROR (116)] {ffffa78058ad0260, fffff809d68bf284, 0, d}
Warning: Unable to verify timestamp for: atikmpag.sys
Probably caused by: atikmpag.sys (Process: System)

File: 070617-6781-01.dmp (Thu Jul 6 19:05:37.087 2017)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)] {ffffffffc0000005, fffff802dbae2c68, 0, ffffffffffffffff}
Probably caused by: ntkrnlmp.exe (Process: System)

File: 071317-6890-01.dmp (Thu Jul 13 18:26:32.170 2017)
BugCheck 119, {1, 8a6a, b, ffffc48fbc7ef180}
Warning: Unable to verify timestamp for: atikmpag.sys
Probably caused by: dxgmms2.sys (Process: Discord.exe)

File: 071717-9109-01.dmp (Mon Jul 17 03:09:28.559 2017)
BugCheck 119, {1, 5b094c, 5b094d, ffff918d55fb8010}
Warning: Unable to verify timestamp for: atikmpag.sys
Warning: Unable to verify timestamp for: atikmdag.sys
Probably caused by: dxgmms2.sys (Process: audiodg.exe)

File: 071917-6343-01.dmp (Wed Jul 19 00:20:33.908 2017)
BugCheck: [VIDEO_TDR_ERROR (116)] {ffffca8bd9fa44a0, fffff80a6df0f654, 0, d}
Warning: Unable to verify timestamp for: atikmpag.sys
Probably caused by: atikmpag.sys (Process: System)

File: 072017-6937-01.dmp (Thu Jul 20 22:22:10.067 2017)
BugCheck: [VIDEO_TDR_ERROR (116)] {ffffbf83ff477100, fffff804c366f654, 0, d}
Warning: Unable to verify timestamp for: atikmpag.sys
Probably caused by: atikmpag.sys (Process: System)

File: 072117-6843-01.dmp (Fri Jul 21 11:40:05.615 2017)
BugCheck: [VIDEO_TDR_ERROR (116)] {ffffcb03757be010, fffff80ae1c0f654, 0, d}
Warning: Unable to verify timestamp for: atikmpag.sys
Probably caused by: atikmpag.sys (Process: System)

File: 072217-7046-01.dmp (Sat Jul 22 06:19:02.990 2017)
BugCheck: [VIDEO_TDR_ERROR (116)] {ffffbc88348514a0, fffff80210bef654, 0, d}
Warning: Unable to verify timestamp for: atikmpag.sys
Probably caused by: atikmpag.sys (Process: System)

File: 072617-6109-01.dmp (Wed Jul 26 01:58:24.649 2017)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)] {ffffffffc0000005, fffff803041e74c7, 0, ffffffffffffffff}
Probably caused by: memory_corruption (Process: explorer.exe)

File: 072617-6218-01.dmp (Wed Jul 26 14:08:49.811 2017)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)] {c0000005, fffff8004c0f059b, ffffb38024f9c460, 0}
Probably caused by: memory_corruption (Process: KillerService.exe)

File: 072617-6500-01.dmp (Wed Jul 26 14:49:00.164 2017)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)] {c0000005, fffff8031a817c25, ffffa480a14d9df0, 0}
Probably caused by: memory_corruption (Process: ShellExperienceHost.exe)

File: 072617-6703-01.dmp (Wed Jul 26 04:29:12.540 2017)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)] {ffffdd00dc6c4048, 0, fffff803212e5de7, 2}
Probably caused by: memory_corruption (Process: GameOverlayUI.exe)
Dump Analysis time: 47 mins

Some of the crashes seem to be caused by your graphics driver. Consider doing a full uninstall with DDU in safe mode then re-install of the graphics driver. [More Information].

I can't help you with more this. Wait for Colif or someone else to reply. Good luck.
 
Upvote 0 Downvote
H

hawk424

Prominent
Jul 26, 2017
7
0
510



Just tried this and my computer is still crashing, thanks for the help though!

 
Upvote 0 Downvote
H

hawk424

Prominent
Jul 26, 2017
7
0
510
here are the most recent crashes:

On Thu 7/27/2017 2:37:44 PM your computer crashed
crash dump file: C:\Windows\Minidump\072717-6312-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801CB44BCC2, 0xFFFFBE01B25ADD70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 7/27/2017 2:22:26 PM your computer crashed
crash dump file: C:\Windows\Minidump\072717-5406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801CBCFB015, 0xFFFFA6006A340DD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 7/27/2017 1:43:29 PM your computer crashed
crash dump file: C:\Windows\Minidump\072717-6531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801A6043232, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 7/27/2017 1:38:35 PM your computer crashed
crash dump file: C:\Windows\Minidump\072717-6312-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x565D1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF011725E65D1, 0xFFFF8F800A722070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 7/27/2017 11:59:50 AM your computer crashed
crash dump file: C:\Windows\Minidump\072717-9843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5DAE8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801CF6DCAE8, 0xFFFFB60010132208, 0xFFFFB60010131A40)
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.
 
Upvote 0 Downvote
Colif

Colif

Win 11 Master
Moderator
Jun 12, 2015
65,261
6,464
168,090
other drivers that might be partly to blame:

e22w10x64.sys (dated Fri Aug 28 2015) - Killer e2200 PCI-E Gigabit Ethernet Controller - get latest drivers here: http://www.killernetworking.com/driver-downloads
MBfilt64.sys (dated Thu Jul 30 2009) - Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013. Download latest drivers here: https://www.tenforums.com/drivers-hardware/5993-latest-realtek-hd-audio-driver-version.html
lgcoretemp.sys (dated Tue Jun 9 2015) - Logitech CPU Core Temp module... what version of LGS tracks CPU temps?
IOMap64.sys (dated Wed Oct 22 2014) - Asus Input Output map driver, can be part of AI Suite or Asus GPU Tweak, update or remove it.

Killer Ethernet and Asus software well known to crash PC, not likely to cause the GPU errors though.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom