BSOD when removing hardware, PFN LIST CORRUPT

KeyHoe · Mar 24, 2013

I have a piece of hardware called the Tweecer and it connects to my laptop vis usb. This hardware has an FTDI chip inside and is used to program the computer in my truck. If you aren't familiar with this hardware, there is some software that comes with it called calcon.exe. I use this program on my Win 7 x64 Samsung laptop to see real time stats from my motor while it is running. So the calcon.exe connects to the Tweecer hardware and interfaces with the stock computer.

I get a BSOD PFN LIST CORRUPT after I have been using calcon. If I open this program and use it for a few min, when I turn off the motor to the truck, I get the BSOD. Turning off the motor to the truck also removes power from the Tweecer. If I close calcon before I turn off the motor, I don't get the BSOD, but that really is a pain.

In reading the mem dump, it references ftdi.sys (I think that was the file name, could have been ftdibus.sys)

I have been reading about PFN LIST CORRUPT a lot in other threads here and I will run memtest soon. I did setup driver verifier and rebooted. I started calcon and got a BSOD of DRIVER IRQ NOT LESS OR EQUAL (first time I got this). So I disabled driver verifier.

At this point I am slightly confused and don't know where to start since I now have two difference BSODs but the PFN LIST error is the most prominent and something I can reproduce.

I'd like to get this resolved and am willing to do the necessary tests.

Thanks

koolkat77 · Mar 25, 2013

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

KeyHoe · Mar 25, 2013

ummm...what did I miss?? I read those instructions and that's how I got here. I have two different BSODs and I think one was caused by driver verifier since that was the first time I saw that particular BSOD. My question was, which one should I address first? The one I saw only once or the one that I see the other 99% of the time?

Arc · Mar 25, 2013

KeyHoe said:
ummm...what did I miss??

You missed this :ar: Blue Screen of Death (BSOD) Posting Instructions.

If you dont follow it, we cannot help you.

KeyHoe · Mar 25, 2013

The machine has been configured for Kernel Memory dump, overwrite any existing file

Files are attached from the SF tool

koolkat77 · Mar 25, 2013

Almost all BSOD's were caused by FTDI USB to Serial adapter:

Driver Description: FTDI USB to Serial adaptor
Driver Reference Table - ftdibus.sys

Code:

 lmvm ftdibus
start             end                 module name
fffff880`1fddb000 fffff880`1fdebf80   ftdibus  T (no symbols)           
    Loaded symbol image file: ftdibus.sys
    Image path: \SystemRoot\system32\drivers\ftdibus.sys
    Image name: ftdibus.sys
    Timestamp:        Fri Apr 13 16:05:13 2012 (4F87FA59)
    CheckSum:         0001C7F6
    ImageSize:        00010F80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Recommendations:

Perform a clean boot:
- http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html
Perform a clean installation of the ftdibus.sys driver:
Click on the Start rb: ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to ftdibus
Code:
```
   USB Serial Converter Driver    c:\windows\system32\drivers\ftdibus.sys
```
Uninstall or change a program
- Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper
- Tutorial: Sometimes drivers remain, not completely uninstalled.
- Follow this tutorial for complete removal of drivers of the particular program> http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Check for a BIOS update:

Code:

BIOS Version/Date    Phoenix Technologies Ltd. 02FD, 9/3/2011

This tutorial http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html may help you:

To Disable Selective Suspend:

open the control panel
go to power options (you may have to set view to small icons)
click change plan settings
in the window that opens:
click change plan settings
click change advanced power settings, expand usb and ensure usb selective suspend is disabled.

Perform a System File Check to check the integrity of all protected Windows 7:

Click Start Menu
- Type Command Prompt in the Search Bar
- Select and click Run as administrator
- Type
- Code:
```
sfc /scannow
```
- and press Enter

SFC /Scannow Command - System File Checker

Check your hard drive(s) for errors by running chkdsk:

Let us know if you continue to get BSOD's.

KeyHoe · Mar 25, 2013

koolkat77 said:
Almost all BSOD's were caused by FTDI USB to Serial adapter:
Driver Description: FTDI USB to Serial adaptor
Driver Reference Table - ftdibus.sys

Code:

lmvm ftdibus start end module name fffff880`1fddb000 fffff880`1fdebf80 ftdibus T (no symbols) Loaded symbol image file: ftdibus.sys Image path: \SystemRoot\system32\drivers\ftdibus.sys Image name: ftdibus.sys Timestamp: Fri Apr 13 16:05:13 2012 (4F87FA59) CheckSum: 0001C7F6 ImageSize: 00010F80 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Click to expand...

Recommendations:

Perform a clean boot:

http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Perform a clean installation of the ftdibus.sys driver:

Click on the Start rb: ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to ftdibus

Code:

USB Serial Converter Driver c:\windows\system32\drivers\ftdibus.sys

Uninstall or change a program

Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper

Tutorial: Sometimes drivers remain, not completely uninstalled.

Follow this tutorial for complete removal of drivers of the particular program> http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

The driver wasn't listed in add/remove programs. I installed Driver Fusion and ran it per the instructions, the driver wasn't listed there either. I saw a USB driver listed as NEC and one as Fresco. No other USB items in that list. The last time I installed the driver, I plugged in the hardware and browsed for the location of the driver and let windows install it. I do know there are files in the system32 and/or system32\drivers folder.

koolkat77 said:
Check for a BIOS update:

Code:

BIOS Version/Date Phoenix Technologies Ltd. 02FD, 9/3/2011

I didn't find a BIOS update listed for my computer at Support - Notebooks NP700Z5BH | Samsung Laptops.

koolkat77 said:
This tutorial http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html may help you:

To Disable Selective Suspend:

open the control panel

go to power options (you may have to set view to small icons)

click change plan settings

in the window that opens:

click change plan settings

click change advanced power settings, expand usb and ensure usb selective suspend is disabled.

This was set to enabled, I set it to disabled.

koolkat77 said:
Perform a System File Check to check the integrity of all protected Windows 7:

Click Start Menu

Type Command Prompt in the Search Bar

Select and click Run as administrator

Type

Code:

sfc /scannow

and press Enter

SFC /Scannow Command - System File Checker

I ran the sfc command as you suggested and this was the result:
C:\Users\Owner>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Users\Owner>

koolkat77 said:
Check your hard drive(s) for errors by running chkdsk:

Check your hard disk for errors

http://www.sevenforums.com/tutorials/433-disk-check.html

Let us know if you continue to get BSOD's.

I'll run chkdsk next and report back if I have any further BSODs, I just wanted to update the thread with what I have found and done so far.

Thanks

koolkat77 · Mar 25, 2013

Thanks for the update.

Be sure to perform the clean boot.

Keep us posted, good luck.

KeyHoe · Mar 27, 2013

The chkdsk log turned up no issues and I had a chance to try and reproduce the BSOD today. I only made the one change to the power profile for USB and I wasn't able to reproduce the BSOD. With how much I used the computer today, I thought I would have seen the issue. I'll report back if I see the issue again.

thanks for the help

koolkat77 · Mar 27, 2013

Will wait for an update.

Good luck.

KeyHoe · Apr 20, 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 · Apr 20, 2013

Upload new reports.

KeyHoe · Apr 21, 2013

files are attached

Thanks

koolkat77 · Apr 22, 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. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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:

[FONT="Consolas"]***   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)[/FONT]

Code:

[FONT="Consolas"]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: [url=http://www.carrona.org/bsodindx.html#0x0000004E]PFN_LIST_CORRUPT (4e)[/url]
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: [url=http://www.carrona.org/bsodindx.html#0x0000004E]PFN_LIST_CORRUPT (4e)[/url]
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: [url=http://www.carrona.org/bsodindx.html#0x0000004E]PFN_LIST_CORRUPT (4e)[/url]
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: [url=http://www.carrona.org/bsodindx.html#0x0000004E]PFN_LIST_CORRUPT (4e)[/url]
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: [url=http://www.carrona.org/bsodindx.html#0x0000004E]PFN_LIST_CORRUPT (4e)[/url]
Bugcheck code 0000004E
Arguments: 
Arg1: 000000000000009a, 
Arg2: 00000000001df0d8
Arg3: 0000000000000006
Arg4: 0000000000000002
BUGCHECK_STR:  0x4E_9a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

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

BSOD when removing hardware, PFN LIST CORRUPT

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer