BSOD when removing hardware, PFN LIST CORRUPT

KeyHoe · 20 Apr 2013

BSOD started consistently again. Almost seems as if it got worse and worse once it started again.

I did verify the setting I changed before is still set to disabled.

koolkat77 · 20 Apr 2013

Upload new reports.

KeyHoe · 21 Apr 2013

files are attached

Thanks

koolkat77 · 22 Apr 2013

Try this tutorial to reinstall the ftdibus driver: Uninstall Device and Device Driver

Code:

Start Menu\Programs\avast! Free Antivirus	Public:Start Menu\Programs\avast! Free Antivirus	Public
Start Menu\Programs\Sandboxie	Public:Start Menu\Programs\Sandboxie	Public

The software above often contribute to BSOD's. Please uninstall them.

Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

Replace with Microsoft Security Essentials and Malwarebytes which are recommended from a strict BSOD perspective. Run a full scan with both (separately) once downloaded, installed and updated. Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free

Good and Free system security combination

Information

DO NOT start the free trial of MalwareBytes. Unselect the option when prompted.

Scan your system with the following:
- Kaspersky TDSSKiller How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)
- ESET online scanner One-time virus scanner free with ESET online scanner
- Run the scanners listed here: How to Scan Suspicious Files using Online Scanners

Heat:

Only use the laptop on a hard surface with nothing blocking any of the vents.

Use a laptop cooling pad if possible

Blow out all vents with canned air (DO NOT use a vacuum cleaner or an air compressor, they can damage the components).

Ensure that the fan comes on and is blowing air out of the vent (may not happen at startup, but should happen after using it for a while).

For monitoring heat of the system, use Speccy or HWMonitor:

Speccy System Information
HWMonitor

Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition
How to Upload and Post a Screenshot and File in Seven Forums

Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. RAM - Test with Memtest86+

Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

Tip

Do this test overnight, before going to bed.

The following is for information purposes only. Any drivers in red should be updated/replaced/removed.

SABI.sys Thu May 28 12:38:02 2009 (4A1E314A)
SAMSUNG Kernel Driver
http://www.carrona.org/drivers/driver.php?id=SABI.sys

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

***   3rd PARTY DRIVER LIST   *** 
ETD.sys                     Tue Jun  7 13:54:39 2011 (4DEDD93F)
HECIx64.sys                 Wed Oct 20 05:33:43 2010 (4CBE2AD7)
IntcDAud.sys                Fri Oct 15 14:28:17 2010 (4CB810A1)
NETwNs64.sys                Thu Aug  4 06:28:26 2011 (4E39E7AA)
RTKVHD64.sys                Tue Aug  2 16:34:26 2011 (4E37D2B2)
Rt64win7.sys                Mon May 16 20:53:31 2011 (4DD13A6B)
SABI.sys                    Thu May 28 12:38:02 2009 (4A1E314A)
SGdrv64.sys                 Tue Apr 12 08:55:23 2011 (4DA3BF1B)
SbieDrv.sys                 Sun Dec 16 17:24:57 2012 (50CDAF89)
WDKMD.sys                   Thu Mar 10 05:43:12 2011 (4D781090)
asmthub3.sys                Thu Jun  2 08:27:58 2011 (4DE6F52E)
asmtxhci.sys                Thu Jun  2 08:27:46 2011 (4DE6F522)
aswFsBlk.SYS                Thu Mar  7 05:22:01 2013 (5137CF99)
aswMonFlt.sys               Thu Mar  7 05:22:08 2013 (5137CFA0)
aswRvrt.sys                 Thu Mar  7 05:21:43 2013 (5137CF87)
aswSP.SYS                   Thu Mar  7 05:23:05 2013 (5137CFD9)
aswSnx.SYS                  Thu Mar  7 05:23:10 2013 (5137CFDE)
aswTdi.SYS                  Thu Mar  7 05:22:10 2013 (5137CFA2)
aswrdr2.sys                 Thu Mar  7 05:22:24 2013 (5137CFB0)
atikmdag.sys                Wed Jul 27 17:37:59 2011 (4E2FF897)
atikmpag.sys                Wed Jul 27 17:03:58 2011 (4E2FF09E)
bpenum.sys                  Thu May 19 16:24:59 2011 (4DD4EFFB)
bpmp.sys                    Thu May 19 16:25:07 2011 (4DD4F003)
bpusb.sys                   Thu May 19 16:25:02 2011 (4DD4EFFE)
clwvd.sys                   Thu Apr 14 09:47:49 2011 (4DA66E65)
ftdibus.sys                 Thu Aug 25 21:13:34 2011 (4E56669E)
iaStor.sys                  Fri Feb 18 22:10:50 2011 (4D5E9A0A)
igdpmd64.sys                Tue Apr  5 09:10:07 2011 (4D9A880F)
intelppm.sys                Tue Jul 14 05:19:25 2009 (4A5BC0FD)
iwdbus.sys                  Thu Mar 10 05:43:23 2011 (4D78109B)
mctkmd64.sys                Thu Sep 29 17:13:18 2011 (4E8452CE)
mctkmdldr64.sys             Fri Apr  8 14:35:33 2011 (4D9EC8D5)

Code:

Debug session time: Sun Apr 21 06:05:59.751 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042013-15958-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:04:59.656
*** WARNING: Unable to verify timestamp for ftdibus.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
Probably caused by : ftdibus.sys ( ftdibus+54ce )
BugCheck 4E, {9a, 1dfaed, 6, 2}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Bugcheck code 0000004E
Arguments: 
Arg1: 000000000000009a, 
Arg2: 00000000001dfaed
Arg3: 0000000000000006
Arg4: 0000000000000002
BUGCHECK_STR:  0x4E_9a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Apr 21 06:00:30.102 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042013-15896-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 1:57:12.007
*** WARNING: Unable to verify timestamp for ftdibus.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
Probably caused by : ftdibus.sys ( ftdibus+54ce )
BugCheck 4E, {9a, 1da262, 6, 2}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Bugcheck code 0000004E
Arguments: 
Arg1: 000000000000009a, 
Arg2: 00000000001da262
Arg3: 0000000000000006
Arg4: 0000000000000002
BUGCHECK_STR:  0x4E_9a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Apr 21 04:02:19.772 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042013-24554-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:49:19.678
*** WARNING: Unable to verify timestamp for ftdibus.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
Probably caused by : ftdibus.sys ( ftdibus+54ce )
BugCheck 4E, {9a, 1df380, 6, 2}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Bugcheck code 0000004E
Arguments: 
Arg1: 000000000000009a, 
Arg2: 00000000001df380
Arg3: 0000000000000006
Arg4: 0000000000000002
BUGCHECK_STR:  0x4E_9a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Apr 21 03:12:02.813 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042013-15615-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:53:35.719
*** WARNING: Unable to verify timestamp for ftdibus.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
Probably caused by : ftdibus.sys ( ftdibus+54ce )
BugCheck 4E, {9a, 1da715, 6, 2}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Bugcheck code 0000004E
Arguments: 
Arg1: 000000000000009a, 
Arg2: 00000000001da715
Arg3: 0000000000000006
Arg4: 0000000000000002
BUGCHECK_STR:  0x4E_9a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Apr 21 02:17:28.292 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042013-15085-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:10:56.198
*** WARNING: Unable to verify timestamp for ftdibus.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
Probably caused by : ftdibus.sys ( ftdibus+54ce )
BugCheck 4E, {9a, 1df0d8, 6, 2}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Bugcheck code 0000004E
Arguments: 
Arg1: 000000000000009a, 
Arg2: 00000000001df0d8
Arg3: 0000000000000006
Arg4: 0000000000000002
BUGCHECK_STR:  0x4E_9a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Post your results once you've completed all the steps.