Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD ntoskrnl.exe (nt+0x75C40) & fltmgr.sys (fltmgr+0x22751)

01 Mar 2013   #1
sidebottom

Windows 7 64 bit home premium.
 
 
BSOD ntoskrnl.exe (nt+0x75C40) & fltmgr.sys (fltmgr+0x22751)

The BSODs do not seem to happen at any specific time.

The computer is an HP with a Pegatron 2A86 Mobo.

I plan on running MemTest86 and will have images uploaded tonight.

For now, here are my WhoCrashed logs and (attached) is the SF files.

Thank you in advance for any help. My feeling right now is bad RAM, but I'm hoping it's just a driver issue I can easily fix.

Edit: one quick edit, the previously configuration had minidumps. I've changed it to kernel dumps, so if I BSOD again in the future, there will, hopefully, be more information.

--------- BEGIN WHOCRASHED DUMP -----------

System Information (local)

computer name: HPDESKTOP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 9654304768 total
VM: 2147352576, free: 1881632768



Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 2/28/2013 9:18:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022813-41355-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x22751)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000108CF8, 0xE240000072C54867, 0xFFFFFA800BF31180)
Error: MEMORY_MANAGEMENT
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 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.
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 Thu 2/28/2013 5:25:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-39717-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680000582F0, 0xF95000024A5D2867, 0xFFFFFA800D76D3E0)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2/27/2013 10:56:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-40076-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030D3B45, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 Sun 2/24/2013 2:43:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022313-53133-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x4E (0x99, 0x22FADF, 0x2, 0x1C73DE)
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 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.
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 2/11/2013 3:11:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021013-65380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x1F7F42, 0x26FFFF, 0x2900)
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 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.
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 2/8/2013 6:39:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020813-45255-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x8886, 0xFFFFFA8005D7D6D0, 0xFFFFFA8006B4FF00, 0x503)
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.
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 2/8/2013 1:14:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-38594-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x21D19C, 0x26FFFF, 0x2500)
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 1/17/2013 6:57:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-47299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x41, 0x2, 0x1, 0xFFFFF800030AC468)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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

8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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 actually 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.


My System SpecsSystem Spec
.
01 Mar 2013   #2
Dsprague

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

Hello sidebottom and welcome to the forums, I had a look through your files and it looks like your BSOD is stemming from AVG:

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {2, 21d19c, 26ffff, 2500}

*** WARNING: Unable to verify timestamp for avgidsfiltera.sys
*** ERROR: Module load completed but symbols could not be loaded for avgidsfiltera.sys
Probably caused by : avgidsfiltera.sys ( avgidsfiltera+37ae )

Followup: MachineOwner
---------
http://carrona.org/drivers/driver.ph...idsfiltera.sys

please remove AVG with the AVG Removal Tool and replace it with a combination of MSE and Mbam. Tip: be sure to uncheck the box asking you to start a free trial when installing Mbam. let us know if this solves your problem.
My System SpecsSystem Spec
Reply

 BSOD ntoskrnl.exe (nt+0x75C40) & fltmgr.sys (fltmgr+0x22751)




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD with dxgmms1.sys, atimdag.sys, ntoskrnl.sys, fltmgr.exe,and more
Hi Guys, my comp has blue screened at-least 2 times a day pretty solid from just watching movies to playing games. It dosent mater what task I am doing it blue screens on everything. It even blue screened when I pushed the shut down button once lol. Im thinking there is a conflict between...
BSOD Help and Support
BSOD random, memory_management, ntoskrnl.exe fltmgr.sys
I am receiving random BSOD with two different bug check strings. MEMORY_MANAGEMENT PAGE_FAULT_IN_NONPAGED_AREA I have updated all of my drivers. I have checked the memory with memcheck both by running it with both sticks installed and one stick installed (both sticks singly). I have checked...
BSOD Help and Support
BSOD, windbg say caused by fltmgr.sys (fltmgr!FltpDispatch+72)
Hi all. I had a BSOD today, but it's not the first. I'm uploading the files, tried inspecting with winDBg but I have only two dmp files (cleared all few weeks ago): The one from 09/08 says it's win32k.sys and the one from today says it's fltmgr.sys. Tried using BlueScreenView, but no real...
BSOD Help and Support
Random BSOD ntoskrnl.exe fltmgr.sys
Hello, i'm having random bsod on my pc since I bought it 2 years ago. Some of the BSOD errors are IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe, NTFS_FILE_SYSTEM Ntfs.sys and BAD_POOL_CALLER fileinfo.sys. The frequency is random, sometimes it runs fine for over a week, and sometimes i have 2 bsod a day....
BSOD Help and Support
Random BSOD, DRIVER_IRQL_NOT_LESS_OR_EQUAL fltmgr.sys and ntoskrnl.exe
Hi, I have been randomly receiving BSODs for quite some time however it appears to be occurring with more frequency now. There hasn't been a specific program running that appears to be linked to the BSOD. Through Event Viewer, the report blames fltmgr.sys and ntoskrnl.exe for the BSOD with a bug...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 13:24.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App