Im having problems with my Windows 10 (Again)

Status
Not open for further replies.

Dree__

Prominent
Mar 7, 2017
16
0
510
0
Sooo Im having some problems with my PC again, but this time I am getting some blues screens while gaming mostly. I ran Who Crashed and got this:
On Thu 04/05/2017 21:34:04 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: 0x3B (0xC000001D, 0xFFFFF8023DC29C53, 0xFFFFB980D2A15D40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Wed 03/05/2017 21:36:23 your computer crashed
crash dump file: C:\Windows\Minidump\050417-23218-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Wed 03/05/2017 17:40:08 your computer crashed
crash dump file: C:\Windows\Minidump\050317-20296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800AFA7BD7D, 0xFFFF828038DD4CC0, 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 Wed 03/05/2017 16:54:19 your computer crashed
crash dump file: C:\Windows\Minidump\050317-19125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8012E90BD57, 0xFFFFC40FAD3E5080, 0xFFFFFFFFF)
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 04/05/2017 21:34:04 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: 0x3B (0xC000001D, 0xFFFFF8023DC29C53, 0xFFFFB980D2A15D40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Wed 03/05/2017 21:36:23 your computer crashed
crash dump file: C:\Windows\Minidump\050417-23218-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Wed 03/05/2017 17:40:08 your computer crashed
crash dump file: C:\Windows\Minidump\050317-20296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800AFA7BD7D, 0xFFFF828038DD4CC0, 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 Wed 03/05/2017 16:54:19 your computer crashed
crash dump file: C:\Windows\Minidump\050317-19125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8012E90BD57, 0xFFFFC40FAD3E5080, 0xFFFFFFFFF)
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 04/05/2017 21:34:04 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: 0x3B (0xC000001D, 0xFFFFF8023DC29C53, 0xFFFFB980D2A15D40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Wed 03/05/2017 21:36:23 your computer crashed
crash dump file: C:\Windows\Minidump\050417-23218-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Wed 03/05/2017 17:40:08 your computer crashed
crash dump file: C:\Windows\Minidump\050317-20296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800AFA7BD7D, 0xFFFF828038DD4CC0, 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 Wed 03/05/2017 16:54:19 your computer crashed
crash dump file: C:\Windows\Minidump\050317-19125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8012E90BD57, 0xFFFFC40FAD3E5080, 0xFFFFFFFFF)
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.

I alredy also used SFC/scannow on the prompt and it said there wasnt any issues. Does anyone now how to solve this? I alredy tried re-installing windows a few times, but that didnt work. Ive got all my drivers updated and these are my configs:
Hardware: ASUSTeK COMPUTER INC., P8Z77-M
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8543305728 bytes total
GTX 670 zotac
Corsair TX850
Windows 10 pro with the most recent update.
 
When was the last time you did a memory diagnostic? The problem with the kernal errors you're getting is they're pointing to a number of possible issues. Since you just updated drivers, I'd check the hardware and see what you get.
 

Dree__

Prominent
Mar 7, 2017
16
0
510
0


While playing any game I always get the same issues.
I am running the Windows 10 pro 64 bits
 

Dree__

Prominent
Mar 7, 2017
16
0
510
0


There isnt any problems with memory(Just made a diagnost) and I dont believe there isnt any rpoblems with hardaware since I just sent it to a store and they said there isnt anything wrong.
 

Dree__

Prominent
Mar 7, 2017
16
0
510
0


Yes, I have everything updated to the latest version
 
Status
Not open for further replies.

ASK THE COMMUNITY