Code:
lmvm fltmgr
start end module name
fffff880`0117f000 fffff880`011cb000 fltmgr (pdb symbols) c:\symcache\fltMgr.pdb\A008BBBF87CC421FA0E568076A16F4BA2\fltMgr.pdb
Loaded symbol image file: fltmgr.sys
Mapped memory image file: c:\symcache\fltmgr.sys\4CE7929C4c000\fltmgr.sys
Image path: \SystemRoot\system32\drivers\fltmgr.sys
Image name: fltmgr.sys
Timestamp: Sat Nov 20 03:19:24 2010 (4CE7929C)
CheckSum: 0005452D
ImageSize: 0004C000
File version: 6.1.7601.17514
Product version: 6.1.7601.17514
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: fltMgr.sys
OriginalFilename: fltMgr.sys
ProductVersion: 6.1.7601.17514
FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
FileDescription: Microsoft Filesystem Filter Manager
LegalCopyright: © Microsoft Corporation. All rights reserved.
This is a Microsoft Windows file and should cause no problems
Code:
lmvm MpFilter
start end module name
fffff880`01199000 fffff880`011db000 MpFilter T (no symbols)
Loaded symbol image file: MpFilter.sys
Image path: \SystemRoot\system32\DRIVERS\MpFilter.sys
Image name: MpFilter.sys
Timestamp: Tue Jan 14 17:55:38 2014 (52D5CE7A)
CheckSum: 0004C189
ImageSize: 00042000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
lmvm Wdf01000
start end module name
fffff880`00e84000 fffff880`00f46000 Wdf01000 (pdb symbols) c:\symcache\Wdf01000.pdb\03FC6AA4329F4372BE924775887225632\Wdf01000.pdb
Loaded symbol image file: Wdf01000.sys
Mapped memory image file: c:\symcache\Wdf01000.sys\51C51641c2000\Wdf01000.sys
Image path: \SystemRoot\system32\drivers\Wdf01000.sys
Image name: Wdf01000.sys
Timestamp: Fri Jun 21 22:13:05 2013 (51C51641)
CheckSum: 000CC9CA
ImageSize: 000C2000
File version: 1.11.9200.16648
Product version: 1.11.9200.16648
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: wdf01000.sys
OriginalFilename: wdf01000.sys
ProductVersion: 1.11.9200.16648
FileVersion: 1.11.9200.16648 (win8_gdr.130621-1503)
FileDescription: Kernel Mode Driver Framework Runtime
LegalCopyright: © Microsoft Corporation. All rights reserved.
This seems to be another OS file
Code:
lmvm aswSP
start end module name
fffff880`06469000 fffff880`064d7000 aswSP T (no symbols)
Loaded symbol image file: aswSP.sys
Image path: \SystemRoot\system32\drivers\aswSP.sys
Image name: aswSP.sys
Timestamp: Wed Jul 02 12:38:12 2014 (53B44384)
CheckSum: 0006A7F3
ImageSize: 0006E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
That is from Avast self protection driver
Jim, Do you have Avast as a AV program? the other files I am seeing right now are Microsoft system files, which never cause BSODs unless the system files are corrupted or the DVD used to install Windows have been tampered with.
I know you mentioned earlier that the computer in question is at another house. Do you have access to that computer now? Also, please tell me where you got the DVD or the ISO file that you used to installed Windows ? Also, are the system specs in the bottom left of your post yours or are they the computer in question? I need the system info, in detail, of the system having issues. In the mean time would you run a short system file checker for me?
Open a elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
The reason I am asking a lot of questions about your installation media is because I am seeing too many references to Microsoft Windows system drivers getting blamed or bring referenced with other drivers. In my experience, that is not normal. There seems that something else is going on there that isn't being told in the dump files.
