Question Frequent Blue Screen

Nov 3, 2019
3
0
10
0
Wonder if there is any kind soul that can help me look at this.
PC has been crashing for a long time now.

updated all my drivers, ran SFC/Scannow, memory test

still cant find the problem.

Any help is much appreciated

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-KB930GF
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: MS-7995, MSI, H110I PRO AC (MS-7995)
CPU: GenuineIntel Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 17142063104 bytes (16.0GB)




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sun 3/11/2019 8:47:57 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110319-7156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x4E (0x99, 0x27C2B8, 0x3, 0xA0000000027A3AF)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 3/11/2019 8:47:57 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: win32kbase.sys (win32kbase!bDeleteSurface+0x5C)
Bugcheck code: 0x4E (0x99, 0x27C2B8, 0x3, 0xA0000000027A3AF)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a 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 3/11/2019 6:28:36 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110319-7078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x139 (0x3, 0xFFFFE18875227430, 0xFFFFE18875227388, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 3/11/2019 5:25:12 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110319-12671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x50 (0xFFFF9B0F7D942D80, 0x0, 0xFFFFF8066FA4A201, 0x0)
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 Sun 13/10/2019 10:16:20 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101319-7796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x139 (0x1D, 0xFFFFC880A332EEB0, 0xFFFFC880A332EE08, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 13/10/2019 10:03:39 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101319-11093-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF8027A8C84F0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8027A8C84F0, 0xFFFF8C0FD67370C8, 0xFFFF8C0FD6736910)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 7/10/2019 8:21:48 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100719-7937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0xEF (0xFFFF9E8B6E6B60C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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 6/10/2019 12:29:12 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100619-8000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x4E (0x99, 0x10B228, 0x2, 0x20003E0003E9327)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 6/10/2019 6:34:30 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100619-8062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x4E (0x2, 0x390949, 0x46EFFF, 0x1)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 6/10/2019 6:08:18 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100619-7906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x44086)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80513B02086, 0xFFFF9007F0F3F408, 0xFFFF9007F0F3EC50)
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

On your computer a total of 51 crash dumps have been found. Only 10 have been 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.
 

PC Tailor

Distinguished
Herald
Welcome to the forums my friend!

updated all my drivers, ran SFC/Scannow, memory test
  • How did you update your drivers and what kind of drivers were they? (hopefully not updated using a driver updater app)
  • What memory test have you performed? This in built windows diagnostic?
Can you post your full system spec (actual RAM model, PSU etc.)
Can you also post the dump files so that we can download them? Just upload them onto a file sharing site.
 
Nov 3, 2019
3
0
10
0
Thank you for your reply !

Unfortunately yes , my drivers were updated through driver booster :(
However the blue screens started before i updated them. I updated them as i though it would solve the problem.

I have done memtest64, and the windows memory diagnostic.

Mini Dump : https://www92.zippyshare.com/v/48nZqL9M/file.html
Computer Specs : https://www61.zippyshare.com/v/LLrCdE29/file.html

Hopefully this information is enough, Let me know if theres any more information i need to provide.

Thank you
 

PC Tailor

Distinguished
Herald
Unfortunately yes , my drivers were updated through driver booster
I say so because driver update apps have a notorious habit of installing incorrect and outright unecessary drivers and can cause various issues. Just it's always best practice to download directly from the manufacturer of the hardware / software.

I am getting a 403 forbidden on the links. Can you upload them onto something like google drive for example?
 
Nov 3, 2019
3
0
10
0
I say so because driver update apps have a notorious habit of installing incorrect and outright unecessary drivers and can cause various issues. Just it's always best practice to download directly from the manufacturer of the hardware / software.

I am getting a 403 forbidden on the links. Can you upload them onto something like google drive for example?
I have deleted driver booster after i came to this forum :/ hopefully its not too late

Minidump : https://www.dropbox.com/s/ecc6rx7hablwiyb/Minidump.rar?dl=0

Specs : https://www.dropbox.com/s/hdek8cdaj62cmw9/SPECS?dl=0
 

ASK THE COMMUNITY

TRENDING THREADS