[SOLVED] Windows 7 x64 BSOD

Amcgrap · Sep 29, 2012

As instructed, I have attached the ZIP files. Thanks for your help and look forward to the results.

Regards,
Amcgrap

Amcgrap · Sep 29, 2012

Re: New Thread, as Instructed

Additional info requested:

· OS - Windows 7 Home Premium
· x64
· What was original installed OS on system? Windows 7
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Came pre-installed on the system
· Age of system (hardware) - Purchased in April of this year (2012)
· Age of OS installation - have you re-installed the OS? Have not re-installed and have not run recovery or gone back to previous point because of the large amounts of software I have installed since purchasing the system. Re-installing software would take large amounts of time and would like to avoid as much as possible
· CPU - 2.50 gigahertz Intel Core i5-2450M, 128 kilobyte primary memory cache, 512 kilobyte secondary memory cache, 3072 kilobyte tertiary memory cache, 64-bit ready, Multi-core (2 total), Hyper-threaded (4 total)
· Video Card - AMD Radeon(TM) HD 6630M [Display adapter], Intel(R) HD Graphics Family [Display adapter]
· MotherBoard - SONY Vaio
· Power Supply - brand & wattage - Not certain
· System Manufacturer - SONY
· Exact model number (if laptop, check label on bottom) - SONY Vaio VPCSA43FX - C60A2ZLY

writhziden · Sep 29, 2012

Re: New Thread, as Instructed

Recommendations:

Software Concerns:

Code:

Start Menu\Programs\SmartPCFixer
Start Menu\Programs\Uniblue\RegistryBooster
Start Menu\Programs\What's my computer doing

The above programs should be removed. The first two are likely to damage your Windows installation rather than repairing it. Windows 7 is very lightweight as it is, and most PC fixing or boosting programs are designed for XP era systems. Running them on Windows 7 tends to strip away components of the installation that are needed for Windows to function properly.

There are better alternatives to What's My Computer Doing. Process Explorer is one. Others are listed here: Sysinternals File and Disk Utilities.

Blue Screen Recommendations:

Your crashes are primarily pointing to SBFWIM.sys as the likely culprit. Did you have AdAware installed at some point? If so, it may not have been removed properly.

Please list any and all security software you have had installed in the past. Also let us know how each was removed from the system.

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

Code:

**************************Fri Sep 28 14:45:43.613 2012 (GMT-6)**************************
ckldrv.sys                  Mon Mar 17 10:46:29 2008 (47DEA065)
ArcSoftKsUFilter.sys        Mon May 25 02:27:31 2009 (4A1A5673)
intelppm.sys                Mon Jul 13 17:19:25 2009 (4A5BC0FD)
SFEP.sys                    Thu Nov 26 22:39:13 2009 (4B0F6601)
amdxata.sys                 Fri Mar 19 10:18:18 2010 (4BA3A3CA)
psi_mf.sys                  Wed Sep  1 01:53:14 2010 (4C7E066A)
RTKVHD64.sys                Tue Oct 19 04:27:08 2010 (4CBD727C)
HECIx64.sys                 Tue Oct 19 17:33:43 2010 (4CBE2AD7)
ATSwpWDF.sys                Tue Nov 30 11:53:17 2010 (4CF5481D)
Rt64win7.sys                Wed Jan 26 06:34:03 2011 (4D4022CB)
WDKMD.sys                   Wed Mar  9 16:43:12 2011 (4D781090)
iwdbus.sys                  Wed Mar  9 16:43:23 2011 (4D78109B)
rikvm_9EC60124.sys          Wed Mar 16 02:30:49 2011 (4D807539)
btmaud.sys                  Wed May 18 15:11:44 2011 (4DD43610)
appliand.sys                Fri May 20 04:20:42 2011 (4DD6407A)
iaStor.sys                  Fri May 20 10:52:24 2011 (4DD69C48)
RimSerial_AMD64.sys         Wed Jul  6 17:20:01 2011 (4E14EDA1)
IntcDAud.sys                Tue Aug 23 07:12:57 2011 (4E53A759)
SBFWIM.sys                  Thu Sep 22 03:11:58 2011 (4E7AFBDE)
Apfiltr.sys                 Tue Oct  4 02:15:43 2011 (4E8AC0AF)
nusb3hub.sys                Mon Oct 24 18:57:37 2011 (4EA60981)
nusb3xhc.sys                Mon Oct 24 18:57:38 2011 (4EA60982)
btmhsf.sys                  Wed Nov  2 06:26:12 2011 (4EB136E4)
iBtFltCoex.sys              Fri Dec  9 12:45:13 2011 (4EE26549)
AMPPAL.sys                  Mon Dec 12 04:33:34 2011 (4EE5E68E)
atikmpag.sys                Wed Dec 21 23:12:38 2011 (4EF2CA56)
atikmdag.sys                Wed Dec 21 23:45:27 2011 (4EF2D207)
RtsPStor.sys                Mon Jan  2 20:01:26 2012 (4F026F86)
MpFilter.sys                Fri Mar  9 04:05:26 2012 (4F59E3F6)
Netwsw00.sys                Mon Mar 12 15:06:43 2012 (4F5E6563)
SbFw.sys                    Fri Apr 13 05:40:33 2012 (4F8810B1)
GEARAspiWDM.sys             Thu May  3 13:56:17 2012 (4FA2E2E1)
igdpmd64.sys                Fri May 25 12:01:38 2012 (4FBFC902)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep 28 09:18:37.579 2012 (GMT-6)**************************
RimUsb_AMD64.sys            Thu Jun 23 15:26:20 2011 (4E03AF7C)

Analysis:

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

Code:

**************************Fri Sep 28 14:45:43.613 2012 (GMT-6)**************************
Loading Dump File [C:\Users\BSODAnalyst\Downloads\Amcgrap\Minidumps 092812\092812-22588-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 5:24:55.472
BugCheck Code: BugCheck BE, {fffff88000d66064, 1f20000003e85101, fffff880033954f0, a}
*** WARNING: Unable to verify timestamp for SBFWIM.sys
*** ERROR: Module load completed but symbols could not be loaded for SBFWIM.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :pacer.sys ( pacer!PcFilterRequestComplete+68 )
BugCheck Info: ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xBE_pacer!PcFilterRequestComplete+68
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep 28 09:18:37.579 2012 (GMT-6)**************************
Loading Dump File [C:\Users\BSODAnalyst\Downloads\Amcgrap\Minidumps 092812\092812-31387-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 9:34:41.828
BugCheck Code: BugCheck D1, {0, 2, 8, 0}
*** WARNING: Unable to verify timestamp for SBFWIM.sys
*** ERROR: Module load completed but symbols could not be loaded for SBFWIM.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :pacer.sys ( pacer!PcFilterRequestComplete+68 )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
PROCESS_NAME: System
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_pacer!PcFilterRequestComplete+68
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Amcgrap · Sep 29, 2012

Re: New Thread, as Instructed

I will remove the programs you suggested. As to Adaware, I haven't used it for years and definitely not on this computer. Re: Security software, I have used VIPRE and Norton 360, but completely removed them and installed MSE, as per jcgriff2's suggestions, and actually solved my previous BSOD problems. It is working very well. These two new occurences are very puzzling because I haven't installed new software the last couple of days. I always thing that Microsoft updates may be the culprits. Could this be a matter of updating / uninstalling / reinstalling my network drivers?

Thanks for your help.

writhziden · Sep 29, 2012

Re: New Thread, as Instructed

It appears that VIPRE did not completely uninstall. GFI provides excellent support in my own experience. I would recommend that you start a support ticket with GFI support to remove the remaining VIPRE drivers. That will most likely resolve the crashes.

Contact GFI Support

Amcgrap · Sep 29, 2012

Re: New Thread, as Instructed

The problem I have with all of this is that the system was perfectly stale the past 3 months after VIPRE and NORTON were uninstalled. I haven't seen any occurences of either recently. McAfee tricks you occasionaly being bundled with new software, but I learned about that a few years ago.

Thank you again. I would like to get rid of any VIPRE remnants in my computer, but the original message was a problem with the network card. I haven't had any more occurences, but wish to avoid 99.9%...if that is possible.

writhziden · Sep 29, 2012

Re: New Thread, as Instructed

The VIPRE drivers interface with your network adapter drivers. The Microsoft Security Essentials drivers will do the same. Since both provide security for your network and internet, they have to share resources.

Having two security programs installed, or having remnants from one installed with another, can cause conflicts since both are trying to accomplish similar or the same tasks. That can lead to any number of network related crashes that may or may not blame the network adapter directly.

You should always avoid having two antiviruses installed in tandem, or two firewalls, or two anti-spyware programs, or two antimalware programs, etc. Right now, you appear to be running both the Windows firewall and remnants of the VIPRE firewall, so network related conflicts are not surprising. If you check the Windows firewall, does it say it is turned on?

Windows Firewall

Click Start
Click Control Panel
Click System and Security
Click Windows Firewall

Amcgrap · Oct 2, 2012

Re: New Thread, as Instructed

Yes. The Windows firewall is on and I never installed the Vipre firewall on this computer. However I downloaded several uninstallers produced by GFI, ran them although, I never found remnants of Vipre before (visually to me) after I uninstalled. Since then, no more BSOD's.

I now have issues with sleep mode with this computer. The SONY Vaio VPCSA43FX is an excellent computer but has shown to be a bit sensitive to Windows Updates and updated drivers.

Thanks for your help. Your organziation is tops in the field.

writhziden · Oct 2, 2012

Re: New Thread, as Instructed

What types of issues occur during sleep? We can probably help.

Amcgrap · Oct 2, 2012

Re: New Thread, as Instructed

I've had issues with going into sleep mode with this computer (intermittent). There were driver conflicts, and one update of the BIOS worked, but as of approx. 1 week ago, the screen goes dark after the time in my power settings, but the power light stays green rather blinking orange, which tells me it is not in sleep mode. It's also odd that when using powercfg -a from the command prompt, the following is the result:

I have looked into this and theoretically S3 is not the state I should have activated, rather S1 or S2. By the way if I manually put the computer to sleep, it still functions. This problem only occurs while the computer is idle.

I am surprised but very happy that from this forum you can try to assist. I've had great success here. Thanks.

writhziden · Oct 2, 2012

Re: New Thread, as Instructed

Have you tried loading the default setup through the BIOS Exit screen?

If your VAIO is like mine, press F2 when the system turns on to enter the BIOS.

Amcgrap · Oct 2, 2012

Re: New Thread, as Instructed

I actually don't recall, but I will try...my previous Vaio was the best notebook system I ever had (there have been many), until it started to act up after 3 years. This one has been finicky, if that can be the right word. Great concept, but either SONY made a slight mistake with this model, and/or I am really taxing the system with the way I use it. The previous unit accepted everything from new drivers to a seamless upgrade from VISTA to WIN 7. I'll let you know what happens. What surprises me is that I can manually make the system go to sleep, yet when idle, will not go to sleep mode.

Thanks.

Amcgrap · Oct 3, 2012

I reset the bios to default settings and it now seems to have resolved the sleep mode problem. I will observe for a couple of days and if everything is OK, will let you know.

Thanks much.

writhziden · Oct 3, 2012

You're welcome!

That's excellent news. Look forward to your next post to find out how things progress after you have had time to do your normal routine for a while.

Amcgrap · Oct 12, 2012

Well 9 days later, the system is working like a charm!! Thanks for your help, as always. You guys are the best!!

writhziden · Oct 12, 2012

I am happy to see all is running smoothly again!

Search

Search

[SOLVED] Windows 7 x64 BSOD

Amcgrap

Well-known member

Attachments

Amcgrap

Well-known member

writhziden

Administrator, .NET/UWP Developer

Amcgrap

Well-known member

writhziden

Administrator, .NET/UWP Developer

Amcgrap

Well-known member

writhziden

Administrator, .NET/UWP Developer

Amcgrap

Well-known member

writhziden

Administrator, .NET/UWP Developer

Amcgrap

Well-known member

writhziden

Administrator, .NET/UWP Developer

Amcgrap

Well-known member

Amcgrap

Well-known member

writhziden

Administrator, .NET/UWP Developer

Amcgrap

Well-known member

writhziden

Administrator, .NET/UWP Developer