Tech Support Forum banner
Status
Not open for further replies.

[SOLVED] Frequent BSOD's while surfing the internet and gaming

4K views 10 replies 2 participants last post by  writhziden 
#1 ·
Hey guys! I have a strange problem regarding BSOD's. Like the title says, I'm having random BSOD's while just surfing the net (watching videos on Youtube, checking my e-mail, etc.) and while playing certain games. I ran memtest86 for about 9-10 hours and it passed with no errors.

About five weeks ago I had the exact same problems as I do now but after installing a fresh copy of windows and updating every single driver (except the modem drivers - I couldn't find new ones) the BSOD's have stopped. Also, when the problems first started a month or so ago I took my computer to the guys I bought it from and they said they ran Prime95 for 92 hours and 3DMark06 for 48 hours and no errors were found.

I really don't understand why the BSOD's returned all of a sudden. Please help!

http://speccy.piriform.com/results/uOsoDMuBY8BfQtXQdC0elw5
 

Attachments

#3 · (Edited)
Re: Frequent BSOD's while surfing the internet and gaming

Recommendations:
The common denominator in all crashes is Alcohol 120%. Remove the software to see if the system is then stable.


You may also have a DirectX/graphics card related problem. DirectX comes installed with Windows, so this may indicate Windows corruption. It may also be that you have corrupted drivers or a graphics card hardware problem.

I do note that you have a newer display card driver than is recommended for your card. Your card is an older version, and the newer drivers are designed for the 6000+ series of cards. Try reverting back to 11.9: Please read this post about the older AMD issues.

  • If you are overclocking any hardware, please stop.

  • Run a system file check to check Windows for corruption:
    1. Click Start Menu
    2. Click All Programs
    3. Click Accessories
    4. Right click Command Prompt
    5. Click Run as administrator
    6. Type
      Code:
      sfc /scannow
      and press Enter
    7. Once it is complete, make note of any messages that appear on the screen.


Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

  1. Download the drivers you want for your display card(s)
  2. Click Start Menu
  3. Click Control Panel
  4. Click Uninstall a program
  5. For AMD:
    • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
    • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers (this applies to onboard graphics, as well):
      1. Click Start Menu
      2. Right Click My Computer/Computer
      3. Click Manage
      4. Click Device Manager from the list on the left
      5. Expand Display adapters
      6. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
      Alternatively:
      1. Login as an adminstrative user
      2. Click Start Menu
      3. Click Control Panel
      4. Click Printers and other hardware
      5. Click Device Manager (the last link under Devices and Printers)
      6. Expand Display adapters
      7. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  6. Restart your computer after uninstalling drivers for all display cards
  7. Install the driver you selected for the display cards once Windows starts

Remember to try multiple versions of the graphics drivers, download them fresh, and install the freshly downloaded drivers.


Outdated and Problematic Drivers:
You should update/replace/remove the following drivers. Any drivers that are known to cause BSODs, please remove the software or remove the drivers and then remove the device; steps to do so are given after the list of outdated drivers.

a347scsi.sys Fri Apr 30 00:32:58 2004 (4091F31A)
Driver for Alcohol 120% in XP.
a347scsi.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

a347bus.sys Fri Apr 30 00:37:01 2004 (4091F40D)
Driver for Alcohol 120% in XP.
a347bus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

glausb.sys Tue Jul 6 18:04:11 2004 (40EB3DFB)
USRobotics/GlobeSpan USB ADSL LAN Modem driver.
glausb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

ASACPI.sys Thu Aug 12 20:52:52 2004 (411C2D04)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys

To update drivers, make sure to download the drivers from the manufacturer and not using 3rd party programs. Your drivers should be found from your motherboard support site (ASUS, Gigabyte, MSI, etc.) or your vendor support site (Dell, HP, Toshiba, Sony, etc.) first. If you have devices you bought yourself, the drivers for those devices need to be downloaded from the manufacturer support site for those devices. If you need help, let us know.

To remove drivers, do so by uninstalling the device or software associated with the driver. Devices can be uninstalled through device manager, and then the device itself should be physically removed from the system if no updates exist for that device driver.


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:
[font=lucida console]**************************Fri Nov 30 04:58:32.968 2012 (UTC - 7:00)************************** 
[COLOR=RED][B]a347scsi.sys Fri Apr 30 00:32:58 2004 (4091F31A)[/B][/COLOR] 
[COLOR=RED][B]a347bus.sys Fri Apr 30 00:37:01 2004 (4091F40D)[/B][/COLOR] 
[COLOR=RED][B]glausb.sys Tue Jul 6 18:04:11 2004 (40EB3DFB)[/B][/COLOR] 
[COLOR=RED][B]ASACPI.sys Thu Aug 12 20:52:52 2004 (411C2D04)[/B][/COLOR] 
lirsgt.sys Sun Jan 29 04:06:18 2006 (43DCA1AA) 
atksgt.sys Fri Sep 15 04:17:58 2006 (450A7DD6) 
LHidFilt.Sys Fri Sep 21 05:05:22 2007 (46F3A572) 
LMouFilt.Sys Fri Sep 21 05:05:25 2007 (46F3A575) 
LUsbFilt.Sys Fri Sep 21 05:05:27 2007 (46F3A577) 
L8042Kbd.sys Fri Sep 21 05:06:13 2007 (46F3A5A5) 
viahduaa.sys Wed Aug 4 01:48:17 2010 (4C591B41) 
ati2cqag.dll Wed Oct 12 13:22:14 2011 (4E95E8E6) 
atikvmag.dll Wed Oct 12 13:33:20 2011 (4E95EB80) 
atiok3x2.dll Wed Oct 12 13:33:45 2011 (4E95EB99) 
ativvaxx.dll Wed Oct 12 13:44:37 2011 (4E95EE25) 
ati2mtag.sys Wed Oct 12 13:59:45 2011 (4E95F1B1) 
ati2dvag.dll Wed Oct 12 14:00:07 2011 (4E95F1C7) 
ati3duag.dll Wed Oct 12 14:04:48 2011 (4E95F2E0) 
Rtenicxp.sys Tue Feb 21 22:24:14 2012 (4F447BFE) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
**************************Tue Nov 27 09:37:48.222 2012 (UTC - 7:00)************************** 
AtihdXP3.sys Fri May 11 02:22:55 2012 (4FACCC5F) 
ati2cqag.dll Tue Jul 3 21:50:01 2012 (4FF3BD69) 
atiok3x2.dll Tue Jul 3 21:56:41 2012 (4FF3BEF9) 
atikvmag.dll Tue Jul 3 22:01:18 2012 (4FF3C00E) 
ativvaxx.dll Tue Jul 3 22:08:57 2012 (4FF3C1D9) 
ati3duag.dll Tue Jul 3 22:32:27 2012 (4FF3C75B) 
ati2mtag.sys Tue Jul 3 22:36:43 2012 (4FF3C85B) 
ati2dvag.dll Tue Jul 3 22:37:10 2012 (4FF3C876) 
[/font]
a347scsi.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
a347bus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
glausb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=lirsgt.sys
http://www.carrona.org/drivers/driver.php?id=atksgt.sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LUsbFilt.Sys
http://www.carrona.org/drivers/driver.php?id=L8042Kbd.sys
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
http://www.carrona.org/drivers/driver.php?id=ati2cqag.dll
http://www.carrona.org/drivers/driver.php?id=atikvmag.dll
http://www.carrona.org/drivers/driver.php?id=atiok3x2.dll
http://www.carrona.org/drivers/driver.php?id=ativvaxx.dll
http://www.carrona.org/drivers/driver.php?id=ati2mtag.sys
http://www.carrona.org/drivers/driver.php?id=ati2dvag.dll
http://www.carrona.org/drivers/driver.php?id=ati3duag.dll
Rtenicxp.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
AtihdXP3.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=ati2cqag.dll
http://www.carrona.org/drivers/driver.php?id=atiok3x2.dll
http://www.carrona.org/drivers/driver.php?id=atikvmag.dll
http://www.carrona.org/drivers/driver.php?id=ativvaxx.dll
http://www.carrona.org/drivers/driver.php?id=ati3duag.dll
http://www.carrona.org/drivers/driver.php?id=ati2mtag.sys
http://www.carrona.org/drivers/driver.php?id=ati2dvag.dll



Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
Code:
[font=lucida console]**************************Fri Nov 30 04:58:32.968 2012 (UTC - 7:00)************************** 
Loading Dump File [C:\Users\writh ziden\Downloads\Freedon_Nadd\TSF_XP_Support\Mini113012-01.dmp] 
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible 
Windows XP Kernel Versio [B] 2600[/B] (Service Pack 3) MP (4 procs) Free x86 compatible 
Built by: [B]2600[/B].xpsp.080413-2111 
System Uptime:[B]0 days 2:35:17.935[/B] 
Probably caused by :[B]usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+68 )[/B] 
BugCheck [B]100000D1, {28, 2, 1, ba3b0be0}[/B] 
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url] 
Arguments: 
Arg1: 00000028, memory referenced 
Arg2: 00000002, IRQL 
Arg3: 00000001, value 0 = read operation, 1 = write operation 
Arg4: ba3b0be0, address which referenced memory 
BUGCHECK_STR: 0xD1 
DEFAULT_BUCKET_ID: DRIVER_FAULT 
PROCESS_NAME: swkotor2.exe 
FAILURE_BUCKET_ID: [B]0xD1_usbohci!OHCI_PollIsoEndpoint+68[/B] 
BIOS Version 2301 
BIOS Release Date 08/11/2010 
Manufacturer System manufacturer 
Product Name System Product Name 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
**************************Tue Nov 27 09:37:48.222 2012 (UTC - 7:00)************************** 
Loading Dump File [C:\Users\writh ziden\Downloads\Freedon_Nadd\TSF_XP_Support\Mini112712-02.dmp] 
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible 
Windows XP Kernel Versio [B] 2600[/B] (Service Pack 3) MP (4 procs) Free x86 compatible 
Built by: [B]2600[/B].xpsp.080413-2111 
System Uptime:[B]0 days 0:50:47.565[/B] 
Probably caused by :[B]usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+298 )[/B] 
BugCheck [B]100000D1, {28, 2, 1, ba3b1b54}[/B] 
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url] 
Arguments: 
Arg1: 00000028, memory referenced 
Arg2: 00000002, IRQL 
Arg3: 00000001, value 0 = read operation, 1 = write operation 
Arg4: ba3b1b54, address which referenced memory 
BUGCHECK_STR: 0xD1 
DEFAULT_BUCKET_ID: DRIVER_FAULT 
PROCESS_NAME: Idle 
FAILURE_BUCKET_ID: [B]0xD1_usbohci!OHCI_PollAsyncEndpoint+298[/B] 
BIOS Version 2301 
BIOS Release Date 08/11/2010 
Manufacturer System manufacturer 
Product Name System Product Name 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
**************************Tue Nov 27 03:26:58.328 2012 (UTC - 7:00)************************** 
Loading Dump File [C:\Users\writh ziden\Downloads\Freedon_Nadd\TSF_XP_Support\Mini112712-01.dmp] 
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible 
Windows XP Kernel Versio [B] 2600[/B] (Service Pack 3) MP (4 procs) Free x86 compatible 
Built by: [B]2600[/B].xpsp.080413-2111 
System Uptime:[B]0 days 1:50:02.903[/B] 
Probably caused by :[B]usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+68 )[/B] 
BugCheck [B]100000D1, {28, 2, 1, ba3b8be0}[/B] 
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url] 
Arguments: 
Arg1: 00000028, memory referenced 
Arg2: 00000002, IRQL 
Arg3: 00000001, value 0 = read operation, 1 = write operation 
Arg4: ba3b8be0, address which referenced memory 
BUGCHECK_STR: 0xD1 
DEFAULT_BUCKET_ID: DRIVER_FAULT 
PROCESS_NAME: Idle 
FAILURE_BUCKET_ID: [B]0xD1_usbohci!OHCI_PollIsoEndpoint+68[/B] 
BIOS Version 2301 
BIOS Release Date 08/11/2010 
Manufacturer System manufacturer 
Product Name System Product Name 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
**************************Mon Nov 26 02:10:42.953 2012 (UTC - 7:00)************************** 
Loading Dump File [C:\Users\writh ziden\Downloads\Freedon_Nadd\TSF_XP_Support\Mini112612-01.dmp] 
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible 
Windows XP Kernel Versio [B] 2600[/B] (Service Pack 3) MP (4 procs) Free x86 compatible 
Built by: [B]2600[/B].xpsp.080413-2111 
System Uptime:[B]0 days 0:00:18.531[/B] 
*** WARNING: Unable to verify timestamp for a347bus.sys 
*** ERROR: Module load completed but symbols could not be loaded for a347bus.sys 
Probably caused by :[B]a347bus.sys ( a347bus+3027 )[/B] 
BugCheck [B]24, {1902fe, a7ec54bc, a7ec51b8, b9e00bc0}[/B] 
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000024]NTFS_FILE_SYSTEM (24)[/url] 
Arguments: 
Arg1: 001902fe 
Arg2: a7ec54bc 
Arg3: a7ec51b8 
Arg4: b9e00bc0 
PROCESS_NAME: svchost.exe 
BUGCHECK_STR: 0x24 
FAILURE_BUCKET_ID: [B]0x24_a347bus+3027[/B] 
BIOS Version 2301 
BIOS Release Date 08/11/2010 
Manufacturer System manufacturer 
Product Name System Product Name 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
**************************Sun Nov 25 08:18:05.593 2012 (UTC - 7:00)************************** 
Loading Dump File [C:\Users\writh ziden\Downloads\Freedon_Nadd\TSF_XP_Support\Mini112512-02.dmp] 
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible 
Windows XP Kernel Versio [B] 2600[/B] (Service Pack 3) MP (4 procs) Free x86 compatible 
Built by: [B]2600[/B].xpsp.080413-2111 
System Uptime:[B]0 days 5:22:34.536[/B] 
Probably caused by :[B]usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+38 )[/B] 
BugCheck [B]FE, {5, 8a38a0e0, 10024397, 899738b0}[/B] 
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000FE]BUGCODE_USB_DRIVER (fe)[/url] 
Arguments: 
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is 
using a physical memory address that was not allocated by 
the USBport driver. 
Arg2: 8a38a0e0, Device extension pointer of the host controller 
Arg3: 10024397, PCI Vendor,Product id for the controller 
Arg4: 899738b0, Pointer to Endpoint data structure 
BUGCHECK_STR: 0xFE 
DEFAULT_BUCKET_ID: DRIVER_FAULT 
PROCESS_NAME: iexplore.exe 
FAILURE_BUCKET_ID: [B]0xFE_usbohci!OHCI_PollIsoEndpoint+38[/B] 
BIOS Version 2301 
BIOS Release Date 08/11/2010 
Manufacturer System manufacturer 
Product Name System Product Name 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
**************************Sun Nov 25 02:54:04.906 2012 (UTC - 7:00)************************** 
Loading Dump File [C:\Users\writh ziden\Downloads\Freedon_Nadd\TSF_XP_Support\Mini112512-01.dmp] 
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible 
Windows XP Kernel Versio [B] 2600[/B] (Service Pack 3) MP (4 procs) Free x86 compatible 
Built by: [B]2600[/B].xpsp.080413-2111 
System Uptime:[B]0 days 0:05:37.859[/B] 
Probably caused by :[B]usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+298 )[/B] 
BugCheck [B]100000D1, {28, 2, 1, ba3b1b54}[/B] 
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url] 
Arguments: 
Arg1: 00000028, memory referenced 
Arg2: 00000002, IRQL 
Arg3: 00000001, value 0 = read operation, 1 = write operation 
Arg4: ba3b1b54, address which referenced memory 
BUGCHECK_STR: 0xD1 
DEFAULT_BUCKET_ID: DRIVER_FAULT 
PROCESS_NAME: iexplore.exe 
FAILURE_BUCKET_ID: [B]0xD1_usbohci!OHCI_PollAsyncEndpoint+298[/B] 
BIOS Version 2301 
BIOS Release Date 08/11/2010 
Manufacturer System manufacturer 
Product Name System Product Name 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
**************************Sat Nov 24 08:13:35.875 2012 (UTC - 7:00)************************** 
Loading Dump File [C:\Users\writh ziden\Downloads\Freedon_Nadd\TSF_XP_Support\Mini112412-01.dmp] 
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible 
Windows XP Kernel Versio [B] 2600[/B] (Service Pack 3) MP (4 procs) Free x86 compatible 
Built by: [B]2600[/B].xpsp.080413-2111 
System Uptime:[B]0 days 0:01:29.839[/B] 
Probably caused by :[B]usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+298 )[/B] 
BugCheck [B]100000D1, {28, 2, 1, ba3b1b54}[/B] 
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url] 
Arguments: 
Arg1: 00000028, memory referenced 
Arg2: 00000002, IRQL 
Arg3: 00000001, value 0 = read operation, 1 = write operation 
Arg4: ba3b1b54, address which referenced memory 
BUGCHECK_STR: 0xD1 
DEFAULT_BUCKET_ID: DRIVER_FAULT 
PROCESS_NAME: iexplore.exe 
FAILURE_BUCKET_ID: [B]0xD1_usbohci!OHCI_PollAsyncEndpoint+298[/B] 
BIOS Version 2301 
BIOS Release Date 08/11/2010 
Manufacturer System manufacturer 
Product Name System Product Name 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
[/font]
 
#5 ·
Re: Frequent BSOD's while surfing the internet and gaming

Crashes point to a USB device. What USB devices do you use?

General USB Troubleshooting

The steps shown are in Windows 7, but they should work for XP as well. The only difference is that INFCACHE.1 should be located in C:\Windows\inf instead of C:\Windows\System32\DriverStore. If you are unable to find it with a search, navigate in your Computer and see if you can find it there manually.

You may need to show hidden files and folders to find the inf directory.
 
#6 ·
Re: Frequent BSOD's while surfing the internet and gaming

I have a mouse and a modem connected by USB.

I've followed steps 1 and 2 of the guide above, but I can't complete step 3 because, having XP, I don't have a Security tab when clicking properties on the INFCACHE.1 file.
 
#7 · (Edited)
Re: Frequent BSOD's while surfing the internet and gaming

Ah yes, I forgot about the security feature of XP. One sec while I come up with steps to delete INFCACHE.1

  1. Click Start
  2. Place the mouse over All Programs
  3. Place the mouse over Accessories
  4. Right click Command Prompt
  5. Click Run as...
  6. Use an administrative account
  7. Type in the following commands in Command Prompt:

    Code:
    cd C:\Windows\inf
    copy INFCACHE.1 INFCACHE.1.bak
    del INFCACHE.1
    That will create a backup just in case, and then delete the original to make sure the USB cache is cleared.


You may need to do the USB troubleshooting steps with the USB modem connection removed. I've seen USB modem connections cause problems on some systems; Ethernet is typically more stable.
 
#10 ·
Re: Frequent BSOD's while surfing the internet and gaming

After a few weeks of intense gaming I think I can say that the problem is solved. If anything pops up in the near future, I know where to turn to. :smile: But regarding this, I'll mark the thread as solved.

Thank you again and happy holidays!
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top