Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Always a BSOD on shutdown


  • Please log in to reply
63 replies to this topic

#46 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:10 AM

Posted 08 June 2012 - 05:01 PM

We are having no success at all attempting to use the Sunbelt removal tool to get rid of the drivers.

I have been a bit slow picking up on the possible significance of this small detail, but the system uptime being shown (8 to 10 seconds) indicates that the crashes are occurring very early in the startup process ... not when shutting down as you have been reporting.

Can you reconcile that with what you are seeing happening with the system?

==========================
BSOD BUGCHECK SUMMARY: system uptime
................................................................
Loading Dump File [C:\CactusIsland\pcar_BC\060812-16364-01\060812-16364-01.dmp]
System Uptime: 0 days 0:00:08.439
................................................................
Loading Dump File [C:\CactusIsland\pcar_BC\060712-17035-01\060712-17035-01.dmp]
System Uptime: 0 days 0:00:09.890
................................................................
Loading Dump File [C:\CactusIsland\pcar_BC\Minidump\060512-20638-01.dmp]
System Uptime: 0 days 0:00:10.436
................................................................
Loading Dump File [C:\CactusIsland\pcar_BC\Windows7_Vista_jcgriff2\060412-18158-01.dmp]
System Uptime: 0 days 0:00:10.467
................................................................
Loading Dump File [C:\CactusIsland\pcar_BC\Windows7_Vista_jcgriff2\060312-16863-01.dmp]
System Uptime: 0 days 0:00:08.860
................................................................

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

BC AdBot (Login to Remove)

 


#47 pcar

pcar
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:10 AM

Posted 09 June 2012 - 11:39 AM

Interesting idea and I don't know that it's NOT happening at startup as well, but the following sequence points to a problem at shutdown.

1. I Shut down computer

2. Generally if there is constant HD activity, shutdown completes all will be fine when I reboot.

3. If there is no constant HD activity the shutdown will not complete and I will see the shutdown screen forever. The computer just freezes and there is never a BSOD error message during shutdown. That will only happen upon a boot after the freeze-up.

4. I don't know how to get around that screen to see as error message.


Also, I've attached the latest .dmp file. It happened last night and is dated as such. I rebooted this morning. Wouldn't the dump file be dated at startup if it were happening then?

Thanks for the persistence.

#48 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:10 AM

Posted 09 June 2012 - 07:42 PM

4. I don't know how to get around that screen to see as error message.

Let's try making a little change to the system settings, so that you get to see the BSOD error message when it actually occurs and you can let me know what you see happening with the system now, while I do some more investigation on the recent crash information.
Last night's crash, dated last night as you say, did indeed happen last night, recording a system uptime of 4 hours and 14 minutes:

System Uptime: 0 days 4:14:49.892


This latest crash STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE was completely different to the previous ones which were all STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR occuring very early on startup. For the first time, I got to see a "normal" crash dump (instead of barely half a one).

Do you have any idea what this might be doing on the system?

EprDrv-amd64.sys Thu Jul 16 04:59:39 2009 ... WinOLS driver for MP2440P - WinOLS OLS500 - EVC electronic GmbH


***Note: These Sunbelt drivers were loaded on the system at the time of the crash:
SbFw.sys     Wed Apr 06 04:12:59 2011
SBFWIM.sys   Tue Feb 08 22:37:58 2011

I note that VirtualBox is on the system, and it may be causing a problem:
VBoxDrv.sys  Thu Mar 15 04:22:40 2012 ... VirtualBox
VBoxNetAdp.sys Thu Mar 15 04:22:41 2012 ... VirtualBox network driver
VBoxNetFlt.sys Thu Mar 15 04:22:40 2012 ... VirtualBox network driver
VBoxUSBMon.sys Thu Mar 15 04:22:40 2012 ... VirtualBox USB driver

If it is not a problem or a major inconvenience for you, I suggest uninstalling Oracle VM VirtualBox 4.1.10 (Version: 4.1.10) for the time being and see what effect it has.

I note these drivers are looking a little out-dated, and it is possible that they may be causing a problem and in need of updating:

agrsm64.sys Tue Nov 11 02:01:35 2008 ... Agere Systems Soft Modem
LPCFilter.sys Wed Apr 23 12:17:54 2008 ... LPC Lower Filter Driver [Toshiba]
tifm21.sys Wed May 02 18:51:57 2007 ... Texas Instruments PCIxx21/PCIxx12 Integrated FlashMedia Controller
UVCFTR_S.SYS Thu Jun 26 18:25:22 2008 ... Chicony USB 2.0 Camera


========================
BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\pcar_BC\060812-16598-01\060812-16598-01.dmp]
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0020d362?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`01770c32?
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat Jun 9 11:44:34.816 2012 (UTC + 10:00)
System Uptime: 0 days 4:14:49.892
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.

Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8001743040, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510
DRVPOWERSTATE_SUBCODE: 4
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff880`031b1f00 fffff800`02e8cc12 : fffffa80`01743040 fffffa80`01743040 00000000`00000000 00000000`0000000f : nt!KiSwapContext+0x7a
fffff880`031b2040 fffff800`02e9df9f : 00000000`00000001 fffff880`01712110 fffffa80`00000000 fffff800`03009e80 : nt!KiCommitThreadWait+0x1d2
fffff880`031b20d0 fffff880`016ba992 : fffffa80`01743000 fffff880`00000000 ffff0000`026a0100 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`031b2170 fffff880`01221c52 : 00000000`00000000 fffff800`02fc2350 fffff880`031b2370 00000000`00000000 : ndis!NdisWaitEvent+0x32
fffff880`031b21b0 fffff880`0121db0b : fffffa80`03565af8 fffffa80`03565af8 fffff880`01228110 00000000`00000000 : vwififlt!filterDoInternalRequest+0x156
fffff880`031b2330 fffff880`0122467d : fffffa80`03565af8 fffffa80`03565af8 fffff880`01228110 fffff800`02e7148a : vwififlt!FilterDeleteVirtualMac+0x183
fffff880`031b23c0 fffff880`037657d7 : fffffa80`055a1c10 00000000`00000000 fffff880`03768110 fffffa80`055601a0 : vwififlt!FExDeregisterMp+0x161
fffff880`031b2400 fffff880`01765d25 : 00000000`00000006 00000000`00000000 fffffa80`055601a0 00000000`00160500 : vwifimp!MPHalt+0x10f
fffff880`031b2440 fffff880`017662d8 : fffffa80`05560100 fffffa80`0000007e fffffa80`01d0ad50 fffffa80`03589990 : ndis!ndisMCommonHaltMiniport+0x6a5
fffff880`031b24e0 fffff880`01769d3c : fffffa80`055601a0 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMHaltMiniport+0x68
fffff880`031b2510 fffff880`01700e6a : fffffa80`055601a0 fffffa80`055601a0 fffffa80`01d0ad50 fffff880`016ae300 : ndis!ndisPnPRemoveDevice+0x36c
fffff880`031b26b0 fffff880`0175d5b2 : 00000000`00000000 fffffa80`055601a0 fffffa80`01d0ad50 00000000`00000002 : ndis!ndisPnPRemoveDeviceEx+0xca
fffff880`031b2710 fffff800`030fd8c9 : fffff8a0`099eadd0 fffffa80`05560050 fffff880`031b2868 00000000`00000000 : ndis! ?? ::LNCPHCLB::`string'+0x7363
fffff880`031b27b0 fffff800`0327d231 : fffffa80`05598d40 00000000`00000000 fffffa80`05598840 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`031b2820 fffff800`02f90763 : fffff8a0`01655c00 fffff8a0`01655c00 00000000`00000018 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`031b28e0 fffff800`0327cd84 : fffffa80`05598840 00000000`00000000 00000000`00000002 00000000`00000000 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`031b2930 fffff800`0327ce90 : 00000000`00000000 fffffa80`05598d00 fffff8a0`018e2d20 fffff800`03092a80 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`031b2960 fffff800`0327cf89 : fffffa80`05543902 fffffa80`055439f0 00000000`00000001 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`031b29d0 fffff800`0327d101 : fffffa80`055439f0 00000000`00000000 fffffa80`055439f0 00000000`00000001 : nt!PnpDelayedRemoveWorker+0x79
fffff880`031b2a20 fffff800`02f90989 : 00000000`00000000 fffffa80`03d78ae0 00000000`00000001 00000000`00000000 : nt!PnpChainDereferenceComplete+0x131
fffff880`031b2a60 fffff800`0330e110 : 00000000`00000000 fffffa80`05598800 fffff8a0`041712d0 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffff880`031b2ae0 fffff800`0330e3ac : fffff880`031b2cb8 fffffa80`03c9d300 fffffa80`01743000 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xff0
fffff880`031b2c20 fffff800`031f764e : 00000000`00000000 fffffa80`03c9d350 fffff8a0`041712d0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`031b2c50 fffff800`02ea0851 : fffff800`030fc760 fffff8a0`041712d0 fffff800`030342d8 00000000`00000299 : nt! ?? ::NNGAKEGL::`string'+0x5ab8b
fffff880`031b2cb0 fffff800`0312de6a : 00000000`00000000 fffffa80`01743040 00000000`00000080 fffffa80`016c4b30 : nt!ExpWorkerThread+0x111
fffff880`031b2d40 fffff800`02e87f06 : fffff880`009e6180 fffffa80`01743040 fffff880`009f0f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b2d80 00000000`00000000 : fffff880`031b3000 fffff880`031ad000 fffff880`031b29e0 00000000`00000000 : nt!KxStartSystemThread+0x16

FAILURE_BUCKET_ID: X64_0x9F_4_ANALYSIS_INCONCLUSIVE
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`01743040 fffff800`00b9c510
BiosVersion = V2.30
BiosReleaseDate = 01/15/2010
SystemManufacturer = TOSHIBA
SystemProductName = Satellite A215
................................................................

Edited by AustrAlien, 09 June 2012 - 07:58 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#49 pcar

pcar
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:10 AM

Posted 10 June 2012 - 11:54 AM

Note: The latest .dmps are attached. To your questions:

1. I have disabled the automatic restart.

2. I have uninstalled the Virtualbox application. It was used for the WIN 8 beta.

3. The EprDrv-amd64.sys file is unknown to me and dated a year prior to my Windows 7 installation which was on a new HD and not an upgrade from Vista.

4. On the Bugcheck report, I don't know if the NDIS drivers are part of the vwififlt (virtual wifi filter) architecture, and I'm not deliberately using ndis wrappers for any protocols I'm using. But if the atheros driver installed these as well I wouldn't have known about it. That (Atheros) driver was updated some weeks ago AFTER the BSOD problem had been present for about a month and before you got involved with this issue.

5. Probably unrelated but I'll state it anyway. I did update this BIOS before installing WIN 7.


Question: Any idea how can I completely remove the Sunbelt drivers?

Edited by pcar, 10 June 2012 - 11:54 AM.


#50 pcar

pcar
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:10 AM

Posted 10 June 2012 - 03:06 PM

Attached are the last two .dmp files. A different shutdown circumstance in the last case.

The latest of these happened as I left the computer unplugged and it ran out of battery, which only lasts 15 minutes anyway. Just in case it's diagnostic here they are.

#51 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:10 AM

Posted 10 June 2012 - 03:41 PM

Question: Any idea how can I completely remove the Sunbelt drivers?

That's got to be the next job! Let's work on that.

In an earlier post (post #18], the first step), the instructions called for downloading autoruns.exe to the "Documents" folder. When you ran the jcgriff2 application it was also supposed to run autoruns and provide the output .... but that didn't happen. I would like you now to run autoruns.exe and provide me with the output:
  • Right-click on autoruns.exe > Run as Administrator to run the application.
    Please be patient: It may take a little time to complete scanning of the system.
  • When scanning is complete, on the main menu at the top, go to File > Save.
  • Choose to Save the file to your Desktop, with the default name of AutoRuns.
    The default file type will be Autoruns Data (.arn)
  • Close autoruns.
At the Desktop, zip up the Autoruns.arn file and attach to your reply:
  • Right-click on the AutoRuns.arn file > Send to ... > Compressed (zipped) Folder.
    The zip file will be located in the same place (the Desktop).
  • Attach the zip file to your next reply.
    When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message.
:exclame: Note: The BC forums will allow a total attachment size of only 512 kb and what you need to attach may exceed this limit. In that case, please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#52 pcar

pcar
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:10 AM

Posted 10 June 2012 - 03:55 PM

Find the AutoRuns file attached. Remarkable how small that turned out to be.

Attached Files



#53 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:10 AM

Posted 10 June 2012 - 03:59 PM

Find the AutoRuns file attached. Remarkable how small that turned out to be.

Yes: Very good! Thank you.

Note: Sooner or later as you keep attaching files, you will get to the 512 KB limit that you are allowed, and will not be able to attach anything more until you remove some of the existing attachments.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#54 pcar

pcar
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:10 AM

Posted 10 June 2012 - 04:14 PM

Thanks for the heads up. I just checked and am so far doing fine on attachments. If you have all you need I'll delete earlier ones from this post, or should I leave them intact until we finish this or get to the 512 limit?

I have them all stored in a directory structure specifically for this problem anyway.

#55 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:10 AM

Posted 10 June 2012 - 04:20 PM

:step1: Please have a look at Services:
  • Start > type services.msc in the search box and press <ENTER>
Have a look down the list of services for anything Sunbelt.
  • Could be Sunbelt Software Firewall or something similar? ... or something like SBRE ... or SBREdrv.sys? ... etc.
Let me know what you find. I am looking for a "nice" way to stop all things Sunbelt, in this case Services ... before actually deleting the Sunbelt files!


:step2: Please have a look at Device Manager:
  • Any devices there with warning symbols displayed?
    Again ... looking for Sunbelt "devices" .... namely that mentioned in event logs as having a problem ... SBRE
Let me know what you find.

Note: I have all your attached stuff on my computer ... so you are free to remove existing attachments any time you wish.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#56 pcar

pcar
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:10 AM

Posted 10 June 2012 - 04:35 PM

No Sunbelt or SBRE artifacts in the services list and the Device Manager shows everything is behaving. No warnings.

#57 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:10 AM

Posted 10 June 2012 - 04:53 PM

Let's make a start with autoruns in that case. Run autoruns.

Click on the Scheduled Tasks tab and uncheck the following:
\Ad-Aware Update (Weekly)			File not found: C:\Program Files (x86)\Lavasoft\Ad-Aware\Ad-AwareAdmin.exe
\Microsoft_Hardware_Launch_IPoint_exe			File not found: c:\Program Files\Microsoft IntelliPoint\IPoint.exe

Click on the Drivers tab and uncheck the following:
Lbd	Ad-Aware mini-filter driver		File not found: system32\DRIVERS\Lbd.sys
SbFw	Sunbelt Personal Firewall driver	Sunbelt Software, Inc.	c:\windows\system32\drivers\sbfw.sys
SBFWIMCL	Sunbelt Personal Firewall NDIS Intermediate driver	Sunbelt Software, Inc.	c:\windows\system32\drivers\sbfwim.sys
SBFWIMCLMP	Sunbelt Personal Firewall NDIS Intermediate driver	Sunbelt Software, Inc.	c:\windows\system32\drivers\sbfwim.sys
sbhips	Legacy Host Intrusion Prevention System Driver	Sunbelt Software, Inc.	c:\windows\system32\drivers\sbhips.sys
Synth3dVsc			File not found: System32\drivers\synth3dvsc.sys
tsusbhub	@%SystemRoot%\system32\drivers\tsusbhub.sys,-2		File not found: system32\drivers\tsusbhub.sys
VBoxNetAdp	VirtualBox Host-Only Network Adapter Driver	Oracle Corporation	c:\windows\system32\drivers\vboxnetadp.sys
VBoxNetFlt			File not found: system32\DRIVERS\VBoxNetFlt.sys
VGPU			File not found: System32\drivers\rdvgkmd.sys

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#58 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:10 AM

Posted 10 June 2012 - 05:13 PM

Re-start the computer.

Earlier on, you were able to delete the Sunbelt driver SBREdrv.sys

Let's see how you go deleting the remaining Sunbelt drivers:
sbfw.sys
sbfwim.sys
sbhips.sys

They will all be found in the drivers folder:
  • c:\windows\system32\drivers\

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#59 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:10 AM

Posted 10 June 2012 - 05:21 PM

I just went back and checked your SystemLook output:

________________________________________
SystemLook 30.07.11 by jpshortstuff
Log created at 17:15 on 07/06/2012 by Ron
Administrator - Elevation successful

========== filefind ==========

Searching for "sbaphd.sys"
No files found.

Searching for "sbapifs.sys"
C:\Windows\System32\drivers\sbapifs.sys --a---- 72280 bytes [21:26 11/05/2011] [21:26 11/05/2011] DB7F9394B2F2D446DF14D46C61B0E94B

Searching for "SbFw.sys"
C:\Windows\System32\drivers\SbFw.sys --a---- 253528 bytes [16:12 26/04/2012] [22:35 05/04/2011] CDB954C736D51DC5FA712C039AF4F683

Searching for "SBFWIM.sys"
C:\Windows\System32\drivers\SbFwIm.sys --a---- 84568 bytes [16:12 26/04/2012] [14:14 08/02/2011] 5DE22E3CB6140213DA2E0599B08D525C
C:\Windows\System32\DriverStore\FileRepository\sbfwim.inf_amd64_neutral_1eddd41265f92d7d\amd64\wnet\SBFWIM.sys --a---- 84568 bytes [14:14

08/02/2011] [14:14 08/02/2011] 5DE22E3CB6140213DA2E0599B08D525C

Searching for "sbtis.sys"
C:\Windows\System32\drivers\sbtis.sys --a---- 94296 bytes [16:12 26/04/2012] [22:35 05/04/2011] F9955774A6BF0A5CA696F591C7B80A79

Searching for "SBREdrv.sys"
No files found.

Searching for "sbhips.sys"
C:\Windows\System32\drivers\sbhips.sys --a---- 60504 bytes [16:13 26/04/2012] [22:35 05/04/2011] A5BC45F8C2F30350E7566799C86B2F5D

-= EOF


There's a couple more of the little sods to delete:
  • C:\Windows\System32\drivers\sbapifs.sys
  • C:\Windows\System32\drivers\sbtis.sys

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#60 pcar

pcar
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:10 AM

Posted 10 June 2012 - 09:05 PM

About the "little sods", is that an acronym or a colloquialism? That asked...

I've Manually deleted C:\Windows\System32\drivers\
1. sbapifs.sys
2. sbtis.sys
3. sbfw.sys (Sunbelt Personal FireWall Driver)
4. sbfwim.sys
5. sbhips.sys (Sunbelt Host Legacy Intrusion Prevention System)

On the earlier request (unchecking Sunbelt drivers in AutoRuns) I immediately (on reboot) lost my wireless internet connection. Adding back one at a time I was able to get it back with only one of them loading.

That one is SBFWIMCLMP.sys.

Without it I can't get a wifi connection at all. It does see the SSID but won't connect. Both SBFWIMCLMP.sys and another driver, SBFWIMCL.sys are labeled "Sunbelt Personal Firewall NDIS Intermediate Drivers". Why they work without #3 above (sbfw.sys Sunbelt Personal FireWall Driver) is unknown to me.
______________________________________________________________________________________________

SystemLook still finds the following file in C:\Windows\System32\DriverStore\FileRepository\

- sbfwim.sys

along with a fairly large number of sbfwin*.* files and subdirectories.
________________________________________________________________________

Shutdown Report:

- I had one BSOD immediately after unchecking the Sunbelt drivers the first time in AutoRuns. After that there were seven clean reboots and the shutdowns are taking less time.

FROM ANOTHER COMPUTER:
- Just now the eighth shutdown produced another BSOD. I'm on another computer and will attach the minidump file in the morning.

- I'll add back those two files one at a time until I have my wifi connection back, but it'll have to wait until tomorrow afternoon. Gotta make up for time lost on this today!

Thanks for the persistence. I'm learning a lot.

Edited by pcar, 10 June 2012 - 09:46 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users