Experiencing Many Different BSODs

[Marquis1]

New PC, bluescreening a lot. Codes so far:
SYSTEM_SERVICE_EXCEPTION
KERNEL_SECURITY_CHECK_FAILURE
CRITICAL_STRUCTURE_CORRUPTION
MEMORY_MANAGEMENT

Need help, will provide more info on responses.

 

[Colif]

Try running the free version of memtest86 on ram sticks, 1 at a time. Any errors means stick needs to be replaced. It creates a bootable USB so can run outside windows

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

 

[Marquis1]

I'm not sure if this helps, but I also can't seem to run windows updater. Computer bluescreens every time I'm updating it.

 

[johnbl]

you would need to put your actual memory dump on a server like microsoft onedrive, share the files for public access and post a link.

The automated tools do not provide the required info to figure out the cause of this problem.

I would be looking at updating SATA drivers, and try to find out what file filters you have installed. If you have a SSD you might also look for udated firmware.

you might also consider putting your drive data cable on a different port or sata controller.

I would just update the BIOS and drivers to the current versions and see if you still bugcheck:
http://www.gigabyte.us/Motherboard/GA-B250M-DS3H-rev-10#support-dl

 

[Marquis1]

you would need to put your actual memory dump on a server like microsoft onedrive, share the files for public access and post a link.

The automated tools do not provide the required info to figure out the cause of this problem.

I would be looking at updating SATA drivers, and try to find out what file filters you have installed. If you have a SSD you might also look for udated firmware.

you might also consider putting your drive data cable on a different port or sata controller.

I would just update the BIOS and drivers to the current versions and see if you still bugcheck:
http://www.gigabyte.us/Motherboard/GA-B250M-DS3H-rev-10#support-dl

Here's a link for the DMP file:

https://1drv.ms/u/s!ArYICoQcWN1zgyjPkXShxAd77U8C

Hope this helps.

 

[Marquis1]

Try running the free version of memtest86 on ram sticks, 1 at a time. Any errors means stick needs to be replaced. It creates a bootable USB so can run outside windows

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

Here is the whocrashed:

Computer name: DESKTOP-GP0TF1N
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: B250M-DS3H, Gigabyte Technology Co., Ltd., B250M-DS3H-CF
CPU: GenuineIntel Intel(R) Pentium(R) CPU G4560 @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8547942400 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 4/15/2017 1:33:27 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041517-4890-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80F93E1AD30)
Bugcheck code: 0x50 (0xFFFFC600C654F2A8, 0x0, 0xFFFFF80F93E1AD30, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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 Sat 4/15/2017 1:33:27 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xFAD30)
Bugcheck code: 0x50 (0xFFFFC600C654F2A8, 0x0, 0xFFFFF80F93E1AD30, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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 Sat 4/15/2017 4:20:17 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041517-4031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x139 (0x3, 0xFFFFAA80A1C29930, 0xFFFFAA80A1C29888, 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 4/15/2017 3:54:42 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041517-6031-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR+0x78D4)
Bugcheck code: 0x34 (0x5117A, 0xFFFFE7809BB23028, 0xFFFFE7809BB22850, 0xFFFFF80F1B4078D4)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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.
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 Sat 4/15/2017 3:35:42 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041517-5250-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xAB655)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8028243B655, 0xFFFFE5012945A2A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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.





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

16 crash dumps have been found and analyzed. Only 5 are included in this report. 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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[Colif]

Bug Check 0x34: CACHE_MANAGER

Cause

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Resolution

To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

never seen a BSOD say BUY MORE RAM before...

I will let John answer as the dumps may show us more.

 

[johnbl]

you have to copy the full memory.dmp file up to the server, then post a link to the server here.
you copied just a link that points to your local machine which we can not access.

you would need to put your actual memory dump on a server like microsoft onedrive, share the files for public access and post a link.

The automated tools do not provide the required info to figure out the cause of this problem.

I would be looking at updating SATA drivers, and try to find out what file filters you have installed. If you have a SSD you might also look for udated firmware.

you might also consider putting your drive data cable on a different port or sata controller.

I would just update the BIOS and drivers to the current versions and see if you still bugcheck:
http://www.gigabyte.us/Motherboard/GA-B250M-DS3H-rev-10#support-dl

Here's a link for the DMP file:

https://1drv.ms/u/s!ArYICoQcWN1zgyjPkXShxAd77U8C

Hope this helps.

 

[Marquis1]

you have to copy the full memory.dmp file up to the server, then post a link to the server here.
you copied just a link that points to your local machine which we can not access.

you would need to put your actual memory dump on a server like microsoft onedrive, share the files for public access and post a link.

The automated tools do not provide the required info to figure out the cause of this problem.

I would be looking at updating SATA drivers, and try to find out what file filters you have installed. If you have a SSD you might also look for udated firmware.

you might also consider putting your drive data cable on a different port or sata controller.

I would just update the BIOS and drivers to the current versions and see if you still bugcheck:
http://www.gigabyte.us/Motherboard/GA-B250M-DS3H-rev-10#support-dl

Here's a link for the DMP file:

https://1drv.ms/u/s!ArYICoQcWN1zgyjPkXShxAd77U8C

Hope this helps.

Do you mean you want me to copy paste the text in the file into a word/notepad document?

 

[Paul NZ]

Thats a shortcut to it. No the file itself

If you installed Macdrive that can cause the cache manager stop error. Someone had the same crash the other day.

And Mediafour gave him an updated file (the file that was crashing)

 

[Marquis1]

you have to copy the full memory.dmp file up to the server, then post a link to the server here.
you copied just a link that points to your local machine which we can not access.

you would need to put your actual memory dump on a server like microsoft onedrive, share the files for public access and post a link.

The automated tools do not provide the required info to figure out the cause of this problem.

I would be looking at updating SATA drivers, and try to find out what file filters you have installed. If you have a SSD you might also look for udated firmware.

you might also consider putting your drive data cable on a different port or sata controller.

I would just update the BIOS and drivers to the current versions and see if you still bugcheck:
http://www.gigabyte.us/Motherboard/GA-B250M-DS3H-rev-10#support-dl

Here's a link for the DMP file:

https://1drv.ms/u/s!ArYICoQcWN1zgyjPkXShxAd77U8C

Hope this helps.

Thats a shortcut to it. No the file itself

If you installed Macdrive that can cause the cahe manager stop error. Someone had the same crash the other day.

And Mediafour gave him an updated file (the file that was crashing)

Sorry about that shortcut. Didn't even occur to me.
I uploaded a bunch of minidump files, I hope they are sufficient:

https://1drv.ms/f/s!ArYICoQcWN1zg0HqfFQ86uWB8sqc

 

[Paul NZ]

I would test the ram with memtest first.

If you havent tested it yet. If its faulty, thats probably the cause of most of these crashes

 

[Marquis1]

I would test the ram with memtest first.

If you havent tested it yet. If its faulty, thats probably the cause of most of these crashes

Is a USB drive the best way to do that? I'm new to this kind of stuff.

 

[Paul NZ]

yup you can get the installer off the site www.memtest.org

 

[Marquis1]

Currently running memtest. On the first pass, I got 252 errors on test 6 and 279 errors on test 9. This is sent from phone, while memtest is still running further passes. How long should I continue running memtest?

 

[Paul NZ]

Well it needs to be replaced then. You can stop it now

 

[Marquis1]

So i should contact the manufacturer of the sticks? Is it my fault that they are in this state or theirs?

 

[Paul NZ]

It can happen. Ring whoever you purchased it from

 

[Marquis1]

Alright thanks a lot! Just for clarification, this is guarenteed an issue with the ram, right?

 

[Paul NZ]

Well it showed errors didnt it? If it did, it's faulty

 

[johnbl]

memory was PSD44G213381
patriot 4gb signature line DDR4 2133 memory cl15 DIMM
1.2 V

you might look up the timing specs and confirm they are correctly set in your BIOS.
I would also check with gigabyte to see if there is a updated bios, often default memory timings are updated in the updates.
you have bios version f2, looks like there is a current version of f5 that just came out.

 

[Marquis1]

memory was PSD44G213381
patriot 4gb signature line DDR4 2133 memory cl15 DIMM
1.2 V

you might look up the timing specs and confirm they are correctly set in your BIOS.
I would also check with gigabyte to see if there is a updated bios, often default memory timings are updated in the updates.
you have bios version f2, looks like there is a current version of f5 that just came out.

Even after the memtest, could this still be the problem? Not the sticks themselves? If the BIOS rather than the sticks are the problem, how should I update my version from f2 to f5?

Edit: I checked the BIOS, and it is set for 2133.

 

[johnbl]

you have to check the manual for the motherboard, most often their is just a tool that will install the new BIOS version.

memory was PSD44G213381
patriot 4gb signature line DDR4 2133 memory cl15 DIMM
1.2 V

you might look up the timing specs and confirm they are correctly set in your BIOS.
I would also check with gigabyte to see if there is a updated bios, often default memory timings are updated in the updates.
you have bios version f2, looks like there is a current version of f5 that just came out.

Even after the memtest, could this still be the problem? Not the sticks themselves? If the BIOS rather than the sticks are the problem, how should I update my version from f2 to f5?

Edit: I checked the BIOS, and it is set for 2133.

 

[Marquis1]

you have to check the manual for the motherboard, most often their is just a tool that will install the new BIOS version.

memory was PSD44G213381
patriot 4gb signature line DDR4 2133 memory cl15 DIMM
1.2 V

you might look up the timing specs and confirm they are correctly set in your BIOS.
I would also check with gigabyte to see if there is a updated bios, often default memory timings are updated in the updates.
you have bios version f2, looks like there is a current version of f5 that just came out.

Even after the memtest, could this still be the problem? Not the sticks themselves? If the BIOS rather than the sticks are the problem, how should I update my version from f2 to f5?

Edit: I checked the BIOS, and it is set for 2133.

On the webpage, http://www.gigabyte.us/Motherboard/GA-B250M-DS3H-rev-10#support-dl There is a link to install f5. Should I download from there or is there a better way to do it? And is this even necessary? Could BIOS version impact the memtest enough to cause 521 errors on the first pass?

 

[Colif]

To upgrade the BIOS, use either the GIGABYTE Q-Flash or @BIOS utility.
• Q-Flash allows the user to quickly and easily upgrade or back up BIOS without entering the operating system.
• @BIOS is a Windows-based utility that searches and downloads the latest version of BIOS from the Internet
and updates the BIOS.

that is in your manual, I would suggest using Q Flash

What is Q-Flash™
Q-Flash is a BIOS flash utility embedded in Flash ROM. With Q-Flash you can update the system BIOS without having to enter operating systems like MS-DOS or Windows first.
(Not all motherboards support Q-Flash™, please use @BIOS™ or DOS flash utility to update BIOS if your motherboard does not have Q-Flash™.)
Features
With this utility, you can access Q-Flash by either pressing <End> key during the POST or pressing the <F8> key in BIOS setup menu. No need to enter operating systems like MS-DOS or Windows first.
Caution
Before using Q-Flash utility, go to GIGABYTE website to download the latest compressed BIOS update file that matches your motherboard model. Extract the file and save the new BIOS file to your floppy disk, USB flash drive, or hard drive. And be noted that the USB flash drive or hard drive must use FAT32/16/12 file system.
Warning:
Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system malfunction.

http://www.gigabyte.com.au/MicroSite/121/tech_qflash.htm - user guide at bottom of page in pdf form