BSOD can't figure out why

Apr 4, 2018
1
0
10
Hi I can't figure out why i keep blue screening could someone take a look at it?

==================================================
Dump File : 040418-4125-01.dmp
Crash Time : 2018-04-04 4:23:35 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff803`cd564577
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`c733e568
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+175510
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.16299.309 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+175510
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\040418-4125-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 16299
Dump File Size : 923,644
Dump File Time : 2018-04-04 4:26:09 PM
==================================================
 
Solution
c0000005 is a bad memory address being passed to windows kernel
00000000`c733e568 is the address that was used.

it is not a kernel mode address. I would be looking for a old driver

without the memory dump I can not tell you the driver name but as a generic fix you would
update the BIOS and motherboard drivers from the motherboard vendors website.


since the error code was 0xc0000005 you should also run memtest86 to test that your bios memory timings are correct and that you don't have a bad ram stick.

c0000005 is a bad memory address being passed to windows kernel
00000000`c733e568 is the address that was used.

it is not a kernel mode address. I would be looking for a old driver

without the memory dump I can not tell you the driver name but as a generic fix you would
update the BIOS and motherboard drivers from the motherboard vendors website.


since the error code was 0xc0000005 you should also run memtest86 to test that your bios memory timings are correct and that you don't have a bad ram stick.

 
Solution

TRENDING THREADS