Solved BSOD while using Internet Explorer, and mini usb wifi TP-Link

[julyzerg]

I constantly have BSOD recently while using IE. I have a driver error report and I guess it may be caused by mini usb wifi TP-Link TL-WN725N.

Here is my SF file created by SF Diagnostic Tool as guided.

Thanks in advance.

 

[koolkat77]

Reduce items at start up:

Performing a Clean Startup in Windows 7

Add, or Remove Startup Programs in Windows 7
​

Your Antivirus software is basically whats just needed there.

Uninstall your current antivirus as it is contributing to your BSOD's. Replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials - Microsoft Windows

Malwarebytes Free​

• :info: Do not start the trial version of MalwareBytes
  
  

You may also take a look at:

Good & Free System Security Combination​

Use the System File Checker tool and Run Disk Check:

Repair Windows 7 System Files with System File Checker

Run Disk Check in Windows 7 for Bad Sectors & Errors​

Upload a screenshot using:

CrystalDiskInfo​

:tip: For how to upload a screenshot or file, read here

Test your Hard Drive by running:

Hard Drive Diagnostic Procedure​

Test and Diagnose RAM Issues with Memtest86+:

RAM - Test with Memtest86+​

:info: Pay close attention to part 3 of the tutorial "If you have errors"

   Tip

• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 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.

BSOD SUMMARY:

[FONT="Lucida Console"]Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jul 24 08:12:38.859 2013 (UTC + 6:00)
System Uptime: 0 days 0:27:27.201
BugCheck D1, {fffffa800c9bd001, 2, 0, fffffa800e12391f}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jul 24 07:44:43.033 2013 (UTC + 6:00)
System Uptime: 0 days 0:36:53.001
BugCheck D1, {fffffa800fd50000, 2, 0, fffffa800cd2391f}
*** WARNING: Unable to verify timestamp for em008_64.dat
*** ERROR: Module load completed but symbols could not be loaded for em008_64.dat
Probably caused by : em008_64.dat ( em008_64+2291f )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jul 24 07:07:19.564 2013 (UTC + 6:00)
System Uptime: 0 days 10:22:50.906
BugCheck D1, {fffffa800f959000, 2, 0, fffffa800e92391f}
*** WARNING: Unable to verify timestamp for em008_64.dat
*** ERROR: Module load completed but symbols could not be loaded for em008_64.dat
Probably caused by : em008_64.dat ( em008_64+2291f )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Jul 23 20:43:59.182 2013 (UTC + 6:00)
System Uptime: 0 days 23:07:59.524
BugCheck D1, {fffffa8010b42000, 2, 0, fffffa800cb2391f}
*** WARNING: Unable to verify timestamp for em008_64.dat
*** ERROR: Module load completed but symbols could not be loaded for em008_64.dat
Probably caused by : em008_64.dat ( em008_64+2291f )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[julyzerg]

I have uninstalled ESET Security and installed MSE. BSOD seems disappeared.

There is no error when I run SFC scan, HD Tune and Memtest86.

Here is my screen shot from Crystal Disk Info.

Thanks for your support.

 

[koolkat77]

Thanks for the update, much appreciated.
Continue to monitor for further BSODs. If you have them - you know what to do
Good luck!