Constant BSOD on custom pc

sammg

Prominent
Oct 6, 2017
8
0
520
Bsod on custom pc windows 10
, i have tried sfc no issues found, memory diagnostic tool, no issues found. When starting the tools in windows it often BS on me with either bad_pool_header or memory_managment seems like a sort of roulette between the two. Started last night around 11. Worked fine during the day. And now when logging in it’ll crash within minutes. Please help guys!
 
Solution
i think i may have found it. Not 100% sure yet still running some tests. i tried testing the memory by using one stick and swapping them out. one of them seems to not cause any BSOD.. So im guessing it must be that faulty ram stick.

PC Tailor

Glorious
Ambassador
Firstly i would download whocrashed and have it analyse the minidump from the last crash. This will give a clearer indication as to what the problem is. This sounds like a RAM issue. What is your full system spec, and how is your RAM configured?

Do you still encounter the crash in safe mode?
 

sammg

Prominent
Oct 6, 2017
8
0
520
Hi,
im in no way an expert, but i will try that.
no it doesnt crash in safe mode so far.

System:
Intel 6600k (not overclocked)
Gigabyte B150-HD3p
(2x8gb) Crucial Ballistix Sport LT BLS2C8G4D240FSB
Gigabyte GTX1060 6Gb windforce
Crucial MX300 ssd
2x 1tb 7200rpm sata hard drives dont know models or anything
corsair cx450m

The weird thing is, it all started since last night, as of my knowledge i have not installed anything new, drivers or software.

UPDATE: I have uninstalled my antivirus and now the system BSOD everytime i try to install an antivirus, and also the start up repair does not work
 

sammg

Prominent
Oct 6, 2017
8
0
520
iv checked whocrashed and found alot of errors labelled perflib. im not reall ysure what else to do

the Bad_pool_Header and Memory_management are being described as a ntoskrnl.ext error. where do i go from here?
 

sammg

Prominent
Oct 6, 2017
8
0
520
I have the crash report here:



Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 06/10/2017 13:20:22 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100617-8203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1A (0x41793, 0xFFFFA400E643D0B0, 0x6, 0x5)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 06/10/2017 13:20:22 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: 0x1A (0x41793, 0xFFFFA400E643D0B0, 0x6, 0x5)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 06/10/2017 13:16:26 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100617-8062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1A (0x41201, 0xFFFFF3812345D080, 0xB7, 0xFFFFC80A83298010)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 06/10/2017 13:05:38 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100617-7031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x19 (0x3, 0xFFFFBA078068A6A0, 0xFFFFAA0F77641E20, 0xFFFFAA0F77641E20)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 06/10/2017 12:31:41 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100617-6718-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR+0x36D16)
Bugcheck code: 0x19 (0xD, 0xFFFFD907A04C6800, 0xF080CB713D71E383, 0xF080CB713D71E380)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. This problem might also be caused because of overheating (thermal issue).
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
--------------------------------------------------------------------------------

33 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

avgsnx.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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.
 

sammg

Prominent
Oct 6, 2017
8
0
520


i cant. when i try to run it i get a 'bad_pool_header'
 

sammg

Prominent
Oct 6, 2017
8
0
520
i think i may have found it. Not 100% sure yet still running some tests. i tried testing the memory by using one stick and swapping them out. one of them seems to not cause any BSOD.. So im guessing it must be that faulty ram stick.
 
Solution

sammg

Prominent
Oct 6, 2017
8
0
520


sorry i did not try this as a solution. I really couldnt understand what to do. Thank you though! maybe if i was a little more capable i wouldve been able to do it