Constant BSODs since upgrade to Windows 10

Toggle sidebar Toggle sidebar
C

Cerebella

Prominent
Jun 10, 2017
11
0
520
Hi all,

I upgraded my machine from Win7 to Win10 recently, and have suffered regular BSODs upon start up. I'm seeing a range of errors and stop codes and I can't seem to make sense of them.

PC specs:

i5-4690K CPU @ 3.50GHz
Corsair - Vengeance LP 16GB (2 x 8GB) DDR3-1600 Memory
MSI - Z97S SLI Krait Edition ATX LGA1150 Motherboard
XFX - Radeon R9 390X 8GB Double Dissipation Black Edition
Samsung - 850 EVO-Series 250GB 2.5" Solid State Drive
2 x Western Digital - Caviar Blue 1TB 3.5" 7200RPM Internal Hard Drive

I'd really appreciate if anyone is able to take a look at and translate the crash info from Who Crashed:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 10/06/2017 09:23:35 your computer crashed
crash dump file: C:\Windows\Minidump\061017-12828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x139 (0x3, 0xFFFF9D00E6B55210, 0xFFFF9D00E6B55168, 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 Sat 10/06/2017 09:23:35 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltGetEcpListFromCallbackData+0x69E)
Bugcheck code: 0x139 (0x3, 0xFFFF9D00E6B55210, 0xFFFF9D00E6B55168, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Tue 06/06/2017 23:54:01 your computer crashed
crash dump file: C:\Windows\Minidump\060717-11921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xFC (0xFFFFFA030792D010, 0x8A00000003900121, 0xFFFFCD817BD68FC0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 Tue 06/06/2017 07:09:38 your computer crashed
crash dump file: C:\Windows\Minidump\060617-11296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x63C9E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801D78FBC9E, 0xFFFFB48148631FA8, 0xFFFFB481486317E0)
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 Mon 05/06/2017 10:55:34 your computer crashed
crash dump file: C:\Windows\Minidump\060517-10140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x50 (0xFFFFFFFFFBFF0000, 0x0, 0xFFFFF801E8C2B3FB, 0x2)
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.



 
Solution
C


I think this may have solved it. I started a strip down with the RAM, mainly because every error message has something to do with memory in it. My PC boots and runs absolutely fine with the 'defective' one removed. As soon as I plug it back in, instant BSOD loop on boot, stating SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. This is with moving the two sticks around in the four DIMM...
Sort by date Sort by votes
can you upload your memory.dmp file to Onedrive (or another file sharing site), show us a link and someone will have a look at it and help fix problems :)

Did you run MSI Live update 6 and see if you had latest drivers, especially since you did an upgrade from win 7.
 
Upvote 0 Downvote
Upvote 0 Downvote


Here we go -



Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
140032 file records processed. File verification completed.
3539 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
199866 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 573 unused index entries from index $SII of file 0x9.
Cleaning up 573 unused index entries from index $SDH of file 0x9.
Cleaning up 573 unused security descriptors.
Security descriptor verification completed.
29918 data files processed. CHKDSK is verifying Usn Journal...
35702624 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
140016 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
46946527 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

243617791 KB total disk space.
55503760 KB in 106288 files.
77508 KB in 29919 indexes.
0 KB in bad sectors.
250411 KB in use by the system.
65536 KB occupied by the log file.
187786112 KB available on disk.

4096 bytes in each allocation unit.
60904447 total allocation units on disk.
46946528 allocation units available on disk.

Internal Info:
00 23 02 00 1b 14 02 00 2f 34 04 00 00 00 00 00 .#....../4......
7c 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 |...............

Windows has finished checking your disk.
Please wait while your computer restarts.

Edit: sfc completed - Windows Resource Protection did not find any integrity violations.

 
Upvote 0 Downvote


I've followed the instructions and so far, no BSODs. I've only shut down and restarted once so far, so I'll test it for a day or two before checking in again.
 
Upvote 0 Downvote
I spoke too soon! Here's what's happened in less than 24 hours of running a clean boot:

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

Computer name: ISIS-MAINFRAME
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\Windows
Hardware: MS-7922, MSI, Z97S SLI Krait Edition (MS-7922)
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17126240256 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 20/06/2017 07:29:26 your computer crashed
crash dump file: C:\Windows\Minidump\062017-8906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0xC1 (0xFFFFD7066AEF6F00, 0xFFFFD7066AEF6D3D, 0xBD4100, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 driver wrote to an invalid section of the special pool.
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 Tue 20/06/2017 07:29:26 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: 0xC1 (0xFFFFD7066AEF6F00, 0xFFFFD7066AEF6D3D, 0xBD4100, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
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 Mon 19/06/2017 07:55:01 your computer crashed
crash dump file: C:\Windows\Minidump\061917-6937-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xAA520)
Bugcheck code: 0xC1 (0xFFFFFB8F5C2EAFD0, 0xFFFFFB8F5C2EA5BD, 0xB74030, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
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 18/06/2017 08:24:32 your computer crashed
crash dump file: C:\Windows\Minidump\061917-7250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0xC4 (0x13A, 0xFFFFF20220B42F40, 0xFFFFAA8BFA4A7540, 0xFFFFF20220B42010)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver has called ExFreePool and Driver Verifier detects an error in one of the internal values that is used to track pool usage. 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.

 
Upvote 0 Downvote
Sometimes who crashed is helpful, other times it just points at ntoskrnl and says.. it did it. ntoskrnl = new technology operating system kernel. Its brains of windows, handles all executive actions, handles memory management, handles driver requests.

I would probably do this again:


as the results may be more helpful in the long run :)

any errors, recreate the dump files and link here if who crashed just blames ntoskrnl again.
 
Upvote 0 Downvote


This isn't looking healthy, is it?

Here's the link - https://1drv.ms/u/s!ArJae_XKHUOwgzlMUl9vreEkKdvP



 
Upvote 0 Downvote
It looks to me like either the system is corrupted or there is a hardware problem.
We checked most of the parts of the system (SFC and chkdsk), you could try below command in an admin command prompt if you want or try a repair install.

Command, keep the spaces: DISM /online /cleanup-image /restorehealth

Date: 2017-06-05T10:56:13.664: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\config\DRIVERS' was corrupted and it has been recovered. Some data might have been lost.
Click to expand...
 
Upvote 0 Downvote

Since running this command, I've had the following occur:

On Wed 21/06/2017 22:46:02 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE0807549B004)
Bugcheck code: 0xD1 (0xFFFFE0807549B004, 0x2, 0x0, 0xFFFFF80039996C50)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 21/06/2017 09:55:59 your computer crashed
crash dump file: C:\Windows\Minidump\062117-8500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0xC1 (0xFFFF898E86B74FF0, 0xFFFF898E86B742FD, 0x954008, 0x23)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 driver wrote to an invalid section of the special pool.
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'm thinking you're right about a hardware issue. During this week, I've had problems turning my PC off. Windows will shutdown, but the actual computer remains powered on, fans running, case lights on etc. I've also had issues with my Razer peripherals not being recognised when booting up, and a BSOD error of rzrudd.sys showing on the BSOD error screen.
 
Upvote 0 Downvote
Try removing the razor software and see if it stops the errors. https://insider.razerzone.com/index.php?threads/rzudd-sys-bsod-when-driver-verifier-is-enabled.22256/

I assume PC isn't overclocked?
driver verifer found nothing
memtest found nothing
chckdsk found nothing
dism didn't fix it
sfc didn't fix it...
clean boot didn't fix it

yet latest error blames a driver. I hate Unknown modules...

try booting into safe mode and see if it still happens
go to settings/update & security/recovery
under Advanced startup, click restart now button
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode with networking
PC will restart and load safe mode

you shouldn't get bsod in safe mode as it only uses windows drivers.
 
Upvote 0 Downvote
I recommend to stripdown the hardware to identify what part causes the issues.
www.carrona.org/strpdown.html

Although in safe mode only the minimum of a system is used, it is no 100% bullet proof test as there happen to be systems that have such a high corruption in Windows that even safe mode fails. The only solution for that is a clean reinstallation.
 
Upvote 1 Downvote
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

you have a third party device driver that is corrupting pool. (data in memory used by device drivers)

go to your motherboard vendors website, update your motherboard drivers, update the bios
update firmware for devices that can have firmware updates. (solid state drives, mouse,...)


the memory dump that shows the pool corruption should also show the pool tag, you can use the pool take and search for the driver that is using that tag.

 
Upvote 0 Downvote


I've carried out all of the above very recently. I think the Razer issue might have been because I only had one of two keyboard USB cables plugged in for some daft reason, and I tried to hit the DEL key a lot on boot.
 
Upvote 0 Downvote


I think this may have solved it. I started a strip down with the RAM, mainly because every error message has something to do with memory in it. My PC boots and runs absolutely fine with the 'defective' one removed. As soon as I plug it back in, instant BSOD loop on boot, stating SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. This is with moving the two sticks around in the four DIMM slots my motherboard has.

 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom