Unknown frequent BSOD

Brandonium10

Honorable
Dec 16, 2013
52
0
10,630
I have recently reinstalled windows 10 on my desktop because it has been running very slowly in the past few months. I have had at least ten blue screens since I have done this, 5 being today. I have run memtest86 and had 1 pass no error after an hour of testing. I downloaded blue screen view and the files that have caused them include ntoskrnl.exe hal.dll and NTFS.sys. I've updated all of my drivers today and nothing is seeming to work. Please help, thanks!
 
Solution
Normally i would ask you for minidumps at this stage but the debugger isn't working for every version of Win 10 now, they broke it for the creators edition. I would suggest you read the posting instructions here and ask on this forum as they do have other tools they can use to figure our problems - https://www.tenforums.com/bsod-crashes-debugging/

this is similar to blue screen view but easier to read - 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 :)

ntoskrnl = Windows New Technology Operating System Kernel. The brains of windows, handles high lvl actions.
hal.dll = hardware abstraction layer. Sits between windows and hardware
ntfs.sys = New Technology File System. What every version of windows has used since XP. MIght be a sign of storage problems, might need sata drivers for instance. hard to say without seeing what errors are.
 


On Sun 5/14/2017 3:20:31 PM your computer crashed
crash dump file: C:\Windows\Minidump\051417-17109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801324381B4, 0xFFFFB58093296590, 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 Sun 5/14/2017 3:20:31 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!Win32AllocPoolImpl+0x2E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801324381B4, 0xFFFFB58093296590, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop 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 Sun 5/14/2017 2:45:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\051417-27187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801042D30C2, 0xFFFFB180D7EF22C0, 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 Sun 5/14/2017 1:02:07 PM your computer crashed
crash dump file: C:\Windows\Minidump\051417-42046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x321B4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80072CC31B4, 0xFFFFA7813032B4D8, 0xFFFFA7813032AD10)
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 Sun 5/14/2017 12:50:43 PM your computer crashed
crash dump file: C:\Windows\Minidump\051417-18609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802D7EC01B4, 0xFFFF96019B050E20, 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.



These all happened today, all being ntoskrnl.exe errors from bluescreenview.
 
Normally i would ask you for minidumps at this stage but the debugger isn't working for every version of Win 10 now, they broke it for the creators edition. I would suggest you read the posting instructions here and ask on this forum as they do have other tools they can use to figure our problems - https://www.tenforums.com/bsod-crashes-debugging/

 
Solution