[SOLVED] Frequent Blue Screen

Toggle sidebar Toggle sidebar
S

salpido

Prominent
Nov 3, 2019
15
0
510
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.





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

Specs : https://www.dropbox.com/s/hdek8cdaj62cmw9/SPECS?dl=0
 
Solution
Colif
if synaptics shows in apps, uninstall it.
if it doesn't, run auto runs and use it to stop it running at startup. if any program does need the driver, it can start it - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

i see you last crashed yesterday, those crash dumps are in the file you just uploaded above (Notes for @gardenman) in date order (file name = date ( I think... 030120-7000 might be 1/March 20) Ignore all the ones ending in 19)
proof. You converted this already - 110319-7640-01.dmp & its date in the dump is Sun Nov 3

I see you like 1 game there... SAN14_SC.exe sure crashes a lot. And its demo

I know you have already run SFC, but try this as well -
right click start button
choose powershell...
Sort by date Sort by votes
FYI, you could easily just list your specs like so:
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:

As opposed to having to give your email credentials to view specs from a stranger.

Second, you will also need to make sure you're update on your OS, we're currently on 1909. You're on 1903. Which BIOS version are you working with?
 
Upvote 0 Downvote
especially since the specs file is an unknown file type.

you did show us some -
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)

but the dumps can tell us that much, what are the other parts?

which memory test?
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

51 crash dumps? Seems you should have come here sooner :)
whocrashed almost always blames the windows kernel, as it is the process that crashed but its normally the victim
ntoskrnl & win32kbase.sys are both parts of the kernel
fltmgr.sys = File system Filter manager. its main duty in the operating system is make sure that the data written to the hard drive is correct and not corrupted.

a friend will comment later with a conversion of dump files so I might be able to help,
 
Upvote 0 Downvote
Hi, I ran the dump 10 most recent dump files (all from last year) through the debugger and got the following information: https://subdermalmonteiberiaeleuth.htmlpasta.com/
File information:110319-7640-01.dmp (Nov 3 2019 - 08:18:18)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: SteamService.exe)
Uptime:0 Day(s), 0 Hour(s), 29 Min(s), and 49 Sec(s)

File information:110319-7156-01.dmp (Nov 3 2019 - 07:47:57)
Bugcheck:PFN_LIST_CORRUPT (4E)
Probably caused by:memory_corruption (Process: steamwebhelper.exe)
Uptime:0 Day(s), 2 Hour(s), 18 Min(s), and 49 Sec(s)

File information:110319-7078-01.dmp (Nov 3 2019 - 05:28:36)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:dxgmms2.sys (Process: System)
Uptime:0 Day(s), 0 Hour(s), 06 Min(s), and 06 Sec(s)

File information:110319-12671-01.dmp (Nov 3 2019 - 04:25:12)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for CPEPMon.sys
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:20 Day(s), 19 Hour(s), 08 Min(s), and 26 Sec(s)

File information:101319-7796-01.dmp (Oct 13 2019 - 09:16:20)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Driver warnings:*** WARNING: Unable to verify timestamp for klifsdk.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 12 Min(s), and 05 Sec(s)

File information:101319-11093-01.dmp (Oct 13 2019 - 09:03:39)
Bugcheck:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:memory_corruption (Process: System)
Uptime:6 Day(s), 1 Hour(s), 41 Min(s), and 17 Sec(s)

File information:100719-7937-01.dmp (Oct 7 2019 - 07:21:48)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Probably caused by:ntkrnlmp.exe (Process: svchost.exe)
Uptime:1 Day(s), 1 Hour(s), 14 Min(s), and 32 Sec(s)

File information:100619-8062-01.dmp (Oct 6 2019 - 05:34:30)
Bugcheck:PFN_LIST_CORRUPT (4E)
Probably caused by:memory_corruption (Process: Three_Kingdoms.exe)
Uptime:0 Day(s), 0 Hour(s), 25 Min(s), and 48 Sec(s)

File information:100619-8000-01.dmp (Oct 5 2019 - 11:29:12)
Bugcheck:PFN_LIST_CORRUPT (4E)
Probably caused by:memory_corruption (Process: Three_Kingdoms.exe)
Uptime:0 Day(s), 2 Hour(s), 34 Min(s), and 38 Sec(s)

File information:100619-7906-01.dmp (Oct 6 2019 - 05:08:18)
Bugcheck:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 4 Hour(s), 54 Min(s), and 36 Sec(s)
Possible motherboard page: https://us.msi.com/Motherboard/H110I-PRO.html
BIOS version you have installed: American Megatrends Inc. - 3.70
If the above is correct, there are BIOS updates available for your system. The latest version being 3.B. Wait for additional information before updating as updating can be risky.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
Have you got any more recent dumps as these are all from October/November amd some of the problems may have been fixed via updates.

CPEPMon.sys is part of Endpoint security monitor
klifsdk.sys is part of Kapersky

dxgmms2.sys is DirectX. Most of the time I see it crash its caused by GPU drivers.. 2 of the ones GM scanned mention DirectX. If nvidia drivers weren't buggy themselves, I would suggest updating them.

Do you have a touchpad as these are normally for those
Jul 04 2018Smb_driver_Intel.sysSynaptics SMBus driver http://www.synaptics.com/


updating bios might help as your version of INtel Management Engine INterface is newer than both your BIOS and whats actually on your motherboards website.
 
Upvote 0 Downvote
Thank you for the analysis guys !

note taken on the format to provide.

I havnt been using my computer much because of how frequent the blue screens are. But if you still need the dump files, I can upload it.
I will update my windows to 1909
My bios version is 3.7 , do i go ahead and update it ?

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)

SSD: Samsung SSD 850 EVO 250GB
GPU: NVIDIA Geforce GTX 1060 6GB
PSU: Coolermaster Masterwatt Lite 600 230V
OS: Windows 10 home

no i do not have a touch pad and i have always been updating my nvidia graphic driver as soon as an update is available on the nvidia application.
 
Upvote 0 Downvote
How did you update your drivers? Did you use a 3rd party driver installer? As they can install weird drivers.

As otherwise those touchpad drivers don't make any sense. Do you have anything like a touch screen monitor? fingerprint scanner? I can see synaptics make a bunch of things but those drivers are for a touchpad. It might not be a cause but its odd.

can you run this? https://www.sysnative.com/forums/pages/bsodcollectionapp/

hold off on BIOS update until i can see more recent errors.
MSI at least have a video showing how
 
Upvote 0 Downvote
if synaptics shows in apps, uninstall it.
if it doesn't, run auto runs and use it to stop it running at startup. if any program does need the driver, it can start it - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

i see you last crashed yesterday, those crash dumps are in the file you just uploaded above (Notes for @gardenman) in date order (file name = date ( I think... 030120-7000 might be 1/March 20) Ignore all the ones ending in 19)
proof. You converted this already - 110319-7640-01.dmp & its date in the dump is Sun Nov 3

I see you like 1 game there... SAN14_SC.exe sure crashes a lot. And its demo

I know you have already run SFC, but try this as well -
right click start button
choose powershell (admin)
copy/paste this command into window:
Repair-WindowsImage -Online -RestoreHealth
and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

I noticed the game seemed to crash whenever either RPC Endpoint mapper or DCOM Launcher would have Critical Process faults. Some of them happened at same time as BSOD. Many of them go unnoticed as it might have recovered and windows just carried on.

Windows Defender crashes a fair bit too.
The above commands might help, as both the processes mentioned are part of windows. The RPC thing is used by so much that its not a good lead to figure out cause.

Its strange you have 2 problem devices, and both are things I don't have either... a standard PS2 Mouse/KB. It is strange it even thinks that is a problem.

Crash on 19th Feb looks like its Nvidia drivers. If you haven't already, try running DDU and instead of getting drivers direct from Nvidia, run windows update and let it find drivers for you. They older Nvidia drivers - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/
 
Upvote 0 Downvote
Solution
ok ! I will try it and test it for a bit to see if the problem goes away !

Thank you so much 😊


(update)
Path :
Online : True
ImageHealthState : Healthy
RestartNeeded : False

this was the result for
Repair-WindowsImage -Online -RestoreHealth
 
Last edited:
Upvote 0 Downvote
Colif said:
(file name = date ( I think... 030120-7000 might be 1/March 20)
Click to expand...
Correct. My software sorts the files by the filename (date & time) if I remember correctly. It's been a while since I worked on that part of it.

Results for the latest 10 dumps: https://gimmickymantaray.htmlpasta.com/
File information:030120-7000-01.dmp (Mar 1 2020 - 09:12:19)
Bugcheck:APC_INDEX_MISMATCH (1)
Probably caused by:ntkrnlmp.exe (Process: svchost.exe)
Uptime:0 Day(s), 1 Hour(s), 32 Min(s), and 48 Sec(s)

File information:022720-9171-01.dmp (Feb 27 2020 - 05:34:14)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: SAN14_SC.exe)
Uptime:4 Day(s), 3 Hour(s), 45 Min(s), and 33 Sec(s)

File information:022720-7015-01.dmp (Feb 27 2020 - 09:09:37)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:dxgmms2.sys (Process: System)
Uptime:0 Day(s), 3 Hour(s), 34 Min(s), and 59 Sec(s)

File information:022320-6921-01.dmp (Feb 23 2020 - 01:48:02)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Probably caused by:ntkrnlmp.exe (Process: svchost.exe)
Uptime:1 Day(s), 12 Hour(s), 55 Min(s), and 18 Sec(s)

File information:022220-7015-01.dmp (Feb 21 2020 - 12:52:17)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:Ntfs.sys (Process: svchost.exe)
Uptime:0 Day(s), 5 Hour(s), 16 Min(s), and 48 Sec(s)

File information:022120-7078-01.dmp (Feb 21 2020 - 07:35:06)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:ntkrnlmp.exe (Process: lsass.exe)
Uptime:0 Day(s), 23 Hour(s), 05 Min(s), and 23 Sec(s)

File information:022020-7281-01.dmp (Feb 20 2020 - 04:46:12)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Probably caused by:ntkrnlmp.exe (Process: svchost.exe)
Uptime:0 Day(s), 4 Hour(s), 01 Min(s), and 02 Sec(s)

File information:022020-7140-01.dmp (Feb 20 2020 - 00:44:36)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 19 Hour(s), 27 Min(s), and 53 Sec(s)

File information:022020-6921-01.dmp (Feb 20 2020 - 06:40:20)
Bugcheck:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 1 Hour(s), 32 Min(s), and 11 Sec(s)

File information:021920-7062-01.dmp (Feb 19 2020 - 04:27:25)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 17 Hour(s), 33 Min(s), and 45 Sec(s)
This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
Both crashes on 27th were caused by GPU drivers. Given that,over the last few months), your GPU drivers were crashing, it could be that the Nvidia drivers are the cause of much of it. Errors with Nvidia drivers rarely actually mention Nvidia, and you get a range of errors.

dxgkrnl!ADAPTER_RENDER DestroyDevice+0xd8
Click to expand...

Sure looks like a Video process. I like name of the Destroy function. Makes it sounds worse than it is. Its nothing to worry about.

See if running DDU helps at all. rest of the dumps don't really point at any one thing.
 
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