This is starting to happen more and more recently usually preceded by applications crashing (Google Chrome or Football Manager), but on occasion just out of nowhere.
I ordered this computer new about a month ago from Overclockers UK with Windows 7 Home Premium 64-bit preloaded, and have not had to do any system restores or re-installations.
Thanks for your help.
Memory corruption caused by an as yet un-named driver (probably your Sftredirlh.sys)
I would run memtest and driver verifier
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Beyond that, please run Verifier with these settings:
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Using Driver Verifier to identify issues with Windows drivers for advanced usersCode:Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050611-17191-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`0329be50 Debug session time: Fri May 6 16:21:26.394 2011 (GMT-4) System Uptime: 0 days 0:02:21.017 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff68004032408, 0, fffff800031d4f07, 2} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff68004032408, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff800031d4f07, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033060e0 fffff68004032408 FAULTING_IP: nt!MiCaptureAndResetWorkingSetAccessBits+97 fffff800`031d4f07 488b5d00 mov rbx,qword ptr [rbp] MM_INTERNAL_CODE: 2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88003139850 -- (.trap 0xfffff88003139850) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000098000000000 rbx=0000000000000000 rcx=0000000004032408 rdx=fffff6fb40000190 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800031d4f07 rsp=fffff880031399e0 rbp=fffff68004032408 r8=0000000000000001 r9=0000000000000014 r10=0000000000000000 r11=00000000000000f4 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy nt!MiCaptureAndResetWorkingSetAccessBits+0x97: fffff800`031d4f07 488b5d00 mov rbx,qword ptr [rbp] ss:0018:fffff680`04032408=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000314d8f2 to fffff800030ce740 STACK_TEXT: fffff880`031396e8 fffff800`0314d8f2 : 00000000`00000050 fffff680`04032408 00000000`00000000 fffff880`03139850 : nt!KeBugCheckEx fffff880`031396f0 fffff800`030cc82e : 00000000`00000000 84600000`2c93d847 00000000`00001000 fffff800`03202bfe : nt! ?? ::FNODOBFM::`string'+0x40ec0 fffff880`03139850 fffff800`031d4f07 : 00000003`00000000 7c400000`2c9fb867 fffff6fb`40000190 fffff700`010942a8 : nt!KiPageFault+0x16e fffff880`031399e0 fffff800`03150a70 : 00000000`00000000 00000000`0000000a fffff880`03139ba0 fffff880`03139bb0 : nt!MiCaptureAndResetWorkingSetAccessBits+0x97 fffff880`03139ae0 fffff800`030e2ee2 : 00000000`0000008d 00000000`00000000 fffffa80`00000000 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x496e8 fffff880`03139b80 fffff800`030e30e8 : 00000000`00000008 fffff880`03139c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`03139bd0 fffff800`033717c6 : fffffa80`03a03680 00000000`00000080 fffffa80`03967b30 00000000`00000001 : nt!KeBalanceSetManager+0x138 fffff880`03139d40 fffff800`030acc26 : fffff800`03248e80 fffffa80`03a03680 fffff800`03256c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03139d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiCaptureAndResetWorkingSetAccessBits+97 fffff800`031d4f07 488b5d00 mov rbx,qword ptr [rbp] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiCaptureAndResetWorkingSetAccessBits+97 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MiCaptureAndResetWorkingSetAccessBits+97 BUCKET_ID: X64_0x50_nt!MiCaptureAndResetWorkingSetAccessBits+97 Followup: MachineOwner ---------
Ok I have gotten it to crash and got back into Windows, but when you say locate and zip up the memory dump file, where do I find this? Or did you want me to repeat what I did in the opening post?Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
Ok, the dump file is uploaded. I did get some errors whilst running memtest but I do not have time tonight to check each stick.
Ok you can disable the Driver Verifier now then uninstall Zone Alarm for a while to see if the BSOD would stop.
If the problem persist, the you must test your RAM each sticks individually until you find out which are the bad and good sticks.
Then test with a known good stick on every slot to find out whether there is any bad motherboard slot.
Log
Code:Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`03007000 PsLoadedModuleList = 0xfffff800`03244e50 Debug session time: Fri May 6 16:03:19.624 2011 (GMT-8) System Uptime: 0 days 0:00:12.154 Loading Kernel Symbols ............................................................... ............................ Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {3, 2, 0, fffff80003097436} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000003, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80003097436, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032af0e0 0000000000000003 CURRENT_IRQL: 2 FAULTING_IP: nt!IopCompleteRequest+c73 fffff800`03097436 488b09 mov rcx,qword ptr [rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System IRP_ADDRESS: ffffffffffffff88 TRAP_FRAME: fffff88002fe7060 -- (.trap 0xfffff88002fe7060) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff88002fe7c80 rbx=0000000000000000 rcx=0000000000000003 rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80003097436 rsp=fffff88002fe71f0 rbp=fffff88002fe7340 r8=fffff88002fe72f8 r9=fffff88002fe72f0 r10=0000000000000002 r11=fffff800030967d0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy nt!IopCompleteRequest+0xc73: fffff800`03097436 488b09 mov rcx,qword ptr [rcx] ds:f000:00000000`00000003=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003076ca9 to fffff80003077740 STACK_TEXT: fffff880`02fe6f18 fffff800`03076ca9 : 00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`02fe6f20 fffff800`03075920 : 00000000`033ed121 fffff980`02d2cee0 fffffa80`0009bc70 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`02fe7060 fffff800`03097436 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`02fe80f8 : nt!KiPageFault+0x260 fffff880`02fe71f0 fffff800`030540b7 : 00000000`00000000 00000000`00000000 fffff880`00000000 00000000`00000000 : nt!IopCompleteRequest+0xc73 fffff880`02fe72c0 fffff800`03054477 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7 fffff880`02fe7340 fffff800`030b0695 : fffff800`03017ac7 00000000`0002f790 00000000`00000000 fffff880`02fe7600 : nt!KiApcInterrupt+0xd7 fffff880`02fe74d8 fffff800`03017ac7 : 00000000`0002f790 00000000`00000000 fffff880`02fe7600 00000000`000758b4 : nt!MiIsAddressValid+0x75 fffff880`02fe74e0 fffff800`03017967 : fffffa80`0414ae18 fffff880`00000011 00000000`00000000 fffff800`00000004 : nt!RtlpWalkFrameChain+0x13f fffff880`02fe7b80 fffff800`0313ac3b : 00000000`00000003 fffffa80`0414ae18 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x73 fffff880`02fe7bb0 fffff800`0350f02c : fffffa80`0414ae00 00000000`00000050 00000000`00000003 fffff800`0316e171 : nt!RtlCaptureStackBackTrace+0x4b fffff880`02fe7be0 fffff800`0351133a : fffff880`02fe3000 fffff880`02fe9000 00000000`00000000 00000000`00000000 : nt!IovpLogStackCallout+0x1c fffff880`02fe7c10 fffff800`03513c9a : fffff8a0`03a64340 00000000`00000005 00000000`00000001 00000000`00000003 : nt!ViPoolLogStackTrace+0x8a fffff880`02fe7c40 fffff800`00000000 : 00000000`00000008 00000001`000000d0 00000000`00000003 00000000`00000001 : nt!VfFreePoolNotification+0x4a fffff880`02fe7c70 00000000`00000008 : 00000001`000000d0 00000000`00000003 00000000`00000001 fffff880`02fe7da0 : 0xfffff800`00000000 fffff880`02fe7c78 00000001`000000d0 : 00000000`00000003 00000000`00000001 fffff880`02fe7da0 00000000`000007ff : 0x8 fffff880`02fe7c80 00000000`00000003 : 00000000`00000001 fffff880`02fe7da0 00000000`000007ff 00000000`00000000 : 0x1`000000d0 fffff880`02fe7c88 00000000`00000001 : fffff880`02fe7da0 00000000`000007ff 00000000`00000000 fffff880`03f6ae32 : 0x3 fffff880`02fe7c90 fffff880`02fe7da0 : 00000000`000007ff 00000000`00000000 fffff880`03f6ae32 fffff8a0`03a62d28 : 0x1 fffff880`02fe7c98 00000000`000007ff : 00000000`00000000 fffff880`03f6ae32 fffff8a0`03a62d28 fffffa80`04602000 : 0xfffff880`02fe7da0 fffff880`02fe7ca0 00000000`00000000 : fffff880`03f6ae32 fffff8a0`03a62d28 fffffa80`04602000 fffff8a0`03a626c0 : 0x7ff STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`03075920 440f20c0 mov rax,cr8 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiPageFault+260 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd FAILURE_BUCKET_ID: X64_0xA_VRF_nt!KiPageFault+260 BUCKET_ID: X64_0xA_VRF_nt!KiPageFault+260 Followup: MachineOwner --------- 1: kd> lmtsmn start end module name fffff880`00e55000 fffff880`00eac000 ACPI ACPI.sys Mon Jul 13 15:19:34 2009 (4A5BC106) fffff880`03c61000 fffff880`03ceb000 afd afd.sys Mon Jul 13 15:21:40 2009 (4A5BC184) fffff880`03fb1000 fffff880`03fc6000 amdppm amdppm.sys Mon Jul 13 15:19:25 2009 (4A5BC0FD) fffff880`01183000 fffff880`0118e000 amdxata amdxata.sys Fri Mar 19 08:18:18 2010 (4BA3A3CA) fffff880`03f83000 fffff880`03f8b000 AppleCharger AppleCharger.sys Mon Apr 26 19:54:05 2010 (4BD65FDD) fffff880`03f61000 fffff880`03f83000 avipbb avipbb.sys Mon Feb 22 02:08:50 2010 (4B8257B2) fffff880`0199b000 fffff880`019a2000 Beep Beep.SYS Mon Jul 13 16:00:13 2009 (4A5BCA8D) fffff880`03f50000 fffff880`03f61000 blbdrive blbdrive.sys Mon Jul 13 15:35:59 2009 (4A5BC4DF) fffff880`01968000 fffff880`01992000 cdrom cdrom.sys Mon Jul 13 15:19:54 2009 (4A5BC11A) fffff880`00c82000 fffff880`00d42000 CI CI.dll Mon Jul 13 17:32:13 2009 (4A5BE01D) fffff880`018ce000 fffff880`018fe000 CLASSPNP CLASSPNP.SYS Mon Jul 13 15:19:58 2009 (4A5BC11E) fffff880`00c24000 fffff880`00c82000 CLFS CLFS.SYS Mon Jul 13 15:19:57 2009 (4A5BC11D) fffff880`0105e000 fffff880`010d1000 cng cng.sys Mon Jul 13 15:49:40 2009 (4A5BC814) fffff880`018fe000 fffff880`0190c000 crashdmp crashdmp.sys Mon Jul 13 16:01:01 2009 (4A5BCABD) fffff880`03f32000 fffff880`03f50000 dfsc dfsc.sys Mon Jul 13 15:23:44 2009 (4A5BC200) fffff880`03f23000 fffff880`03f32000 discache discache.sys Mon Jul 13 15:37:18 2009 (4A5BC52E) fffff880`018b8000 fffff880`018ce000 disk disk.sys Mon Jul 13 15:19:57 2009 (4A5BC11D) fffff880`03e49000 fffff880`03e8c000 dtsoftbus01 dtsoftbus01.sys Thu Jan 13 00:27:08 2011 (4D2EB75C) fffff880`0190c000 fffff880`01916000 dump_diskdump dump_diskdump.sys Mon Jul 12 19:32:05 2010 (4C3BDE35) fffff880`01955000 fffff880`01968000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 15:21:51 2009 (4A5BC18F) fffff880`01916000 fffff880`01955000 dump_nvstor64 dump_nvstor64.sys Fri Apr 09 01:22:41 2010 (4BBEF1E1) fffff880`06c3c000 fffff880`06d30000 dxgkrnl dxgkrnl.sys Tue Jan 25 20:22:56 2011 (4D3FA1A0) fffff880`06d30000 fffff880`06d76000 dxgmms1 dxgmms1.sys Tue Jan 25 20:22:12 2011 (4D3FA174) fffff880`011da000 fffff880`011ee000 fileinfo fileinfo.sys Mon Jul 13 15:34:25 2009 (4A5BC481) fffff880`0118e000 fffff880`011da000 fltmgr fltmgr.sys Mon Jul 13 15:19:59 2009 (4A5BC11F) fffff880`0122b000 fffff880`01235000 Fs_Rec Fs_Rec.sys Mon Jul 13 15:19:45 2009 (4A5BC111) fffff880`0187e000 fffff880`018b8000 fvevol fvevol.sys Fri Sep 25 18:34:26 2009 (4ABD7DB2) fffff880`01400000 fffff880`0144a000 fwpkclnt fwpkclnt.sys Mon Jul 13 15:21:08 2009 (4A5BC164) fffff880`06b5b000 fffff880`06b68000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 04:17:04 2009 (4A1151C0) fffff800`035e4000 fffff800`0362d000 hal hal.dll Mon Jul 13 17:27:36 2009 (4A5BDF08) fffff880`06ae3000 fffff880`06b07000 HDAudBus HDAudBus.sys Mon Jul 13 16:06:13 2009 (4A5BCBF5) fffff880`01875000 fffff880`0187e000 hwpolicy hwpolicy.sys Mon Jul 13 15:19:22 2009 (4A5BC0FA) fffff800`00bc3000 fffff800`00bcd000 kdcom kdcom.dll Sat Feb 05 04:21:45 2011 (4D4D40D9) fffff880`01200000 fffff880`0121a000 ksecdd ksecdd.sys Mon Jul 13 15:20:54 2009 (4A5BC156) fffff880`015cf000 fffff880`015fa000 ksecpkg ksecpkg.sys Thu Dec 10 22:03:32 2009 (4B21E0B4) fffff880`00c03000 fffff880`00c10000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 17:29:09 2009 (4A5BDF65) fffff880`00f85000 fffff880`00f9f000 mountmgr mountmgr.sys Mon Jul 13 15:19:54 2009 (4A5BC11A) fffff880`01800000 fffff880`0180b000 Msfs Msfs.SYS Mon Jul 13 15:19:47 2009 (4A5BC113) fffff880`00eb5000 fffff880`00ebf000 msisadrv msisadrv.sys Mon Jul 13 15:19:26 2009 (4A5BC0FE) fffff880`01000000 fffff880`0105e000 msrpc msrpc.sys Mon Jul 13 15:21:32 2009 (4A5BC17C) fffff880`03f18000 fffff880`03f23000 mssmbios mssmbios.sys Mon Jul 13 15:31:10 2009 (4A5BC3BE) fffff880`01863000 fffff880`01875000 mup mup.sys Mon Jul 13 15:23:45 2009 (4A5BC201) fffff880`0147d000 fffff880`0156f000 ndis ndis.sys Mon Jul 13 15:21:40 2009 (4A5BC184) fffff880`03c00000 fffff880`03c0f000 netbios netbios.sys Mon Jul 13 16:09:26 2009 (4A5BCCB6) fffff880`03ceb000 fffff880`03d30000 netbt netbt.sys Mon Jul 13 15:21:28 2009 (4A5BC178) fffff880`0156f000 fffff880`015cf000 NETIO NETIO.SYS Thu Apr 08 18:43:59 2010 (4BBE946F) fffff880`0180b000 fffff880`0181c000 Npfs Npfs.SYS Mon Jul 13 15:19:48 2009 (4A5BC114) fffff880`03f0c000 fffff880`03f18000 nsiproxy nsiproxy.sys Mon Jul 13 15:21:02 2009 (4A5BC15E) fffff800`03007000 fffff800`035e4000 nt ntkrnlmp.exe Tue Oct 26 18:43:09 2010 (4CC791BD) fffff880`01254000 fffff880`013f6000 Ntfs Ntfs.sys Thu Mar 10 19:39:25 2011 (4D79996D) fffff880`01992000 fffff880`0199b000 Null Null.SYS Mon Jul 13 15:19:37 2009 (4A5BC109) fffff880`10b4a000 fffff880`10b4b180 nvBridge nvBridge.kmd Thu Jan 20 17:10:57 2011 (4D38DD21) fffff880`0fee9000 fffff880`10b49300 nvlddmkm nvlddmkm.sys Thu Jan 20 17:17:54 2011 (4D38DEC2) fffff880`06b07000 fffff880`06b5aa80 nvmf6264 nvmf6264.sys Thu Mar 04 17:04:39 2010 (4B9058A7) fffff880`00f9f000 fffff880`00fca000 nvstor nvstor.sys Fri Mar 19 12:45:11 2010 (4BA3E257) fffff880`01144000 fffff880`01183000 nvstor64 nvstor64.sys Fri Apr 09 01:22:41 2010 (4BBEF1E1) fffff880`03dce000 fffff880`03df4000 pacer pacer.sys Mon Jul 13 16:09:41 2009 (4A5BCCC5) fffff880`03fd2000 fffff880`03fef000 parport parport.sys Mon Jul 13 16:00:40 2009 (4A5BCAA8) fffff880`00eff000 fffff880`00f14000 partmgr partmgr.sys Mon Jul 13 15:19:58 2009 (4A5BC11E) fffff880`00ebf000 fffff880`00ef2000 pci pci.sys Mon Jul 13 15:19:51 2009 (4A5BC117) fffff880`0121a000 fffff880`0122b000 pcw pcw.sys Mon Jul 13 15:19:27 2009 (4A5BC0FF) fffff880`00c10000 fffff880`00c24000 PSHED PSHED.dll Mon Jul 13 17:32:23 2009 (4A5BE027) fffff880`03ebb000 fffff880`03f0c000 rdbss rdbss.sys Mon Jul 13 15:24:09 2009 (4A5BC219) fffff880`019e5000 fffff880`019ee000 RDPCDD RDPCDD.sys Mon Jul 13 16:16:34 2009 (4A5BCE62) fffff880`019ee000 fffff880`019f7000 rdpencdd rdpencdd.sys Mon Jul 13 16:16:34 2009 (4A5BCE62) fffff880`019f7000 fffff880`01a00000 rdprefmp rdprefmp.sys Mon Jul 13 16:16:35 2009 (4A5BCE63) fffff880`01829000 fffff880`01863000 rdyboost rdyboost.sys Mon Jul 13 15:34:34 2009 (4A5BC48A) fffff880`03fc6000 fffff880`03fd2000 serenum serenum.sys Mon Jul 13 16:00:33 2009 (4A5BCAA1) fffff880`03c0f000 fffff880`03c2c000 serial serial.sys Mon Jul 13 16:00:40 2009 (4A5BCAA8) fffff880`0144a000 fffff880`01452000 spldr spldr.sys Mon May 11 08:56:27 2009 (4A0858BB) fffff880`010e2000 fffff880`01144000 storport storport.sys Thu Mar 10 20:24:35 2011 (4D79A403) fffff880`01603000 fffff880`01800000 tcpip tcpip.sys Sun Jun 13 19:39:04 2010 (4C15A458) fffff880`0181c000 fffff880`01829000 TDI TDI.SYS Mon Jul 13 15:21:18 2009 (4A5BC16E) fffff880`01452000 fffff880`01470000 tdx tdx.sys Mon Jul 13 15:21:15 2009 (4A5BC16B) fffff880`03ea7000 fffff880`03ebb000 termdd termdd.sys Mon Jul 13 16:16:36 2009 (4A5BCE64) fffff880`03f8b000 fffff880`03fb1000 tunnel tunnel.sys Mon Jul 13 16:09:37 2009 (4A5BCCC1) fffff880`06ad2000 fffff880`06ae3000 usbehci usbehci.sys Fri Oct 23 20:27:33 2009 (4AE28235) fffff880`03fef000 fffff880`03ffa000 usbohci usbohci.sys Mon Jul 13 16:06:30 2009 (4A5BCC06) fffff880`06a7c000 fffff880`06ad2000 USBPORT USBPORT.SYS Mon Jul 13 16:06:31 2009 (4A5BCC07) fffff880`00ef2000 fffff880`00eff000 vdrvroot vdrvroot.sys Mon Jul 13 16:01:31 2009 (4A5BCADB) fffff880`019a2000 fffff880`019b0000 vga vga.sys Mon Jul 13 15:38:47 2009 (4A5BC587) fffff880`019b0000 fffff880`019d5000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 15:38:51 2009 (4A5BC58B) fffff880`00f14000 fffff880`00f29000 volmgr volmgr.sys Mon Jul 13 15:19:57 2009 (4A5BC11D) fffff880`00f29000 fffff880`00f85000 volmgrx volmgrx.sys Mon Jul 13 15:20:33 2009 (4A5BC141) fffff880`00e00000 fffff880`00e4c000 volsnap volsnap.sys Mon Jul 13 15:20:08 2009 (4A5BC128) fffff880`03d30000 fffff880`03dc5000 vsdatant vsdatant.sys Sun May 09 08:28:58 2010 (4BE6E2CA) fffff880`03e8c000 fffff880`03ea7000 wanarp wanarp.sys Mon Jul 13 16:10:21 2009 (4A5BCCED) fffff880`019d5000 fffff880`019e5000 watchdog watchdog.sys Mon Jul 13 15:37:35 2009 (4A5BC53F) fffff880`00d42000 fffff880`00de6000 Wdf01000 Wdf01000.sys Mon Jul 13 15:22:07 2009 (4A5BC19F) fffff880`00de6000 fffff880`00df5000 WDFLDR WDFLDR.SYS Mon Jul 13 15:19:54 2009 (4A5BC11A) fffff880`03dc5000 fffff880`03dce000 wfplwf wfplwf.sys Mon Jul 13 16:09:26 2009 (4A5BCCB6) fffff880`00eac000 fffff880`00eb5000 WMILIB WMILIB.SYS Mon Jul 13 15:19:51 2009 (4A5BC117) 1: kd> !verifier Verify Level fbf ... enabled options are: Special pool Special irql Inject random low-resource API failures All pool allocations checked on unload Io subsystem checking enabled Deadlock detection enabled DMA checking enabled Security checks enabled Force pending I/O requests IRP Logging Miscellaneous checks enabled Summary of All Verifier Statistics RaiseIrqls 0x0 AcquireSpinLocks 0x4 Synch Executions 0x0 Trims 0x2a3 Pool Allocations Attempted 0x3720 Pool Allocations Succeeded 0x3720 Pool Allocations Succeeded SpecialPool 0x3720 Pool Allocations With NO TAG 0x4d Pool Allocations Failed 0x0 Resource Allocations Failed Deliberately 0x0 Current paged pool allocations 0x3d for 00002C9C bytes Peak paged pool allocations 0x4a for 02EBC954 bytes Current nonpaged pool allocations 0x311 for 0046FC74 bytes Peak nonpaged pool allocations 0x312 for 0046FD90 bytes
If I uninstall ZoneAlarm, what free firewall would you recommend?
Windows 7 built-in firewall is good enough to use.
It is far better than in XP.
3rd party firewall sometimes can cause system instability.
https://www.sevenforums.com/919182-post34.html
Quote