BSOD Problem

[jco66mt]

I have had many problems but I have gotten them all fixed I think except the FE USB code problem in the report. It is the 4 most recent BSOD's. Not sure how to fix it thank you so much.



My System

MB-ASUS M4A88TH-V EV0/USB3
CPU-AMD Phenom II x4 965 Black Edition 3.4
GPU-XFX Radeon HD 5830
Memory-G. SKILL Ripjaws Series 4GB 2x2
OS-Windows 7 64bit
PSU-Corsairs 650W

 

[usasma]

Only running the May 2011 memory dumps (6 of them)

Lot's of hardware issues in MSINFO32, please do the following:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

Another interesting test that just came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - program doesn't have a whole bunch of safety features to protect you from yourself!

What is connected to your USB ports? That's what's to blame here.

ALso, please do the following:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

[font=lucida console]
nusb3hub.sys            Tue Feb 23 21:10:14 2010 (4B848A86)
amdxata.sys             Fri Mar 19 12:18:18 2010 (4BA3A3CA)
SYMDS64.SYS             Tue Dec 07 19:16:58 2010 (4CFECE7A)
AtiPcie.sys             Mon Aug 24 04:25:26 2009 (4A924E76)
[Color=Red]scmndisp.sys            Wed Jan 17 02:48:03 2007 (45ADD4B3)[/Color]
AsUpIO.sys              Sun Jul 05 22:21:38 2009 (4A515FB2)
AsIO.sys                Thu Apr 22 07:18:03 2010 (4BD0306B)
SYMNETS.SYS             Thu Mar 17 23:24:33 2011 (4D82D071)
Ironx64.SYS             Fri Nov 12 18:06:50 2010 (4CDDC88A)
ASACPI.sys              Wed Jul 15 23:31:29 2009 (4A5E9F11)
nusb3xhc.sys            Tue Feb 23 21:10:16 2010 (4B848A88)
[Color=Red]Afc.sys                 Wed Jul 12 01:48:20 2006 (44B48D24)[/Color]
GEARAspiWDM.sys         Mon May 18 08:17:04 2009 (4A1151C0)
AtiHdmi.sys             Thu Jan 28 20:03:36 2010 (4B6233E8)
RTKVHD64.sys            Tue Jul 06 06:05:16 2010 (4C32FFDC)
RtNdPt60.sys            Sun Jul 19 22:27:32 2009 (4A63D614)
bcmwlhigh664.sys        Thu Nov 05 19:27:07 2009 (4AF36D5B)
serscan.sys             Mon Jul 13 20:35:32 2009 (4A5BD2D4)
Rt64win7.sys            Wed Feb 16 04:03:57 2011 (4D5B92FD)
ENG64.SYS               Fri Mar 04 17:02:16 2011 (4D716168)
IDSvia64.sys            Fri Mar 11 21:15:42 2011 (4D7AD74E)
eeCtrl64.sys            Tue May 03 00:23:25 2011 (4DBF833D)
SRTSP64.SYS             Tue Mar 29 22:46:12 2011 (4D929974)
BHDrvx64.sys            Wed Apr 13 20:16:01 2011 (4DA63CC1)
EX64.SYS                Fri Mar 04 17:10:51 2011 (4D71636B)
SYMDS64.SYS             Fri Oct 15 13:53:54 2010 (4CB89532)
SYMEFA64.SYS            Mon Nov 15 16:56:23 2010 (4CE1AC87)
SYMNETS.SYS             Tue Nov 30 18:24:40 2010 (4CF587B8)
eeCtrl64.sys            Fri May 21 17:44:45 2010 (4BF6FECD)
EraserUtilRebootDrv.sys Fri May 21 17:44:45 2010 (4BF6FECD)
SYMEVENT64x86.SYS       Fri Jul 30 19:05:59 2010 (4C535AD7)
SRTSPX64.SYS            Fri Nov 19 19:18:10 2010 (4CE713C2)
SRTSP64.SYS             Fri Nov 19 19:17:58 2010 (4CE713B6)
[/font]

http://www.carrona.org/dvrref.html#nusb3hub.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#SYMDS64.SYS
http://www.carrona.org/dvrref.html#AtiPcie.sys
http://www.carrona.org/dvrref.html#scmndisp.sys
http://www.carrona.org/dvrref.html#AsUpIO.sys
http://www.carrona.org/dvrref.html#AsIO.sys
http://www.carrona.org/dvrref.html#SYMNETS.SYS
http://www.carrona.org/dvrref.html#Ironx64.SYS
http://www.carrona.org/dvrref.html#ASACPI.sys
http://www.carrona.org/dvrref.html#nusb3xhc.sys
http://www.carrona.org/dvrref.html#Afc.sys
http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
http://www.carrona.org/dvrref.html#AtiHdmi.sys
http://www.carrona.org/dvrref.html#RTKVHD64.sys
http://www.carrona.org/dvrref.html#RtNdPt60.sys
http://www.carrona.org/dvrref.html#bcmwlhigh664.sys
http://www.carrona.org/dvrref.html#serscan.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#ENG64.SYS
http://www.carrona.org/dvrref.html#IDSvia64.sys
http://www.carrona.org/dvrref.html#eeCtrl64.sys
http://www.carrona.org/dvrref.html#SRTSP64.SYS
http://www.carrona.org/dvrref.html#BHDrvx64.sys
http://www.carrona.org/dvrref.html#EX64.SYS
http://www.carrona.org/dvrref.html#SYMDS64.SYS
http://www.carrona.org/dvrref.html#SYMEFA64.SYS
http://www.carrona.org/dvrref.html#SYMNETS.SYS
http://www.carrona.org/dvrref.html#eeCtrl64.sys
http://www.carrona.org/dvrref.html#EraserUtilRebootDrv.sys
http://www.carrona.org/dvrref.html#SYMEVENT64x86.SYS
http://www.carrona.org/dvrref.html#SRTSPX64.SYS
http://www.carrona.org/dvrref.html#SRTSP64.SYS

Also, please do this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052211-49951-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun May 22 14:34:02.914 2011 (UTC - 4:00)
System Uptime: 6 days 3:00:46.515
BugCheck FE, {5, fffffa800591b1a0, 10024396, fffffa8007ff3c48}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`0591b1a0 00000000`10024396 fffffa80`07ff3c48
BiosVersion = 1401   
BiosReleaseDate = 06/11/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051611-27206-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun May 15 14:53:12.362 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:20.456
BugCheck FE, {5, fffffa8005f3e1a0, 10024396, fffffa8006891258}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`05f3e1a0 00000000`10024396 fffffa80`06891258
BiosVersion = 1401   
BiosReleaseDate = 06/11/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051511-22417-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun May 15 14:29:02.360 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:03.468
BugCheck FE, {5, fffffa8005e511a0, 10024396, fffffa8006565b38}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`05e511a0 00000000`10024396 fffffa80`06565b38
BiosVersion = 1401   
BiosReleaseDate = 06/11/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051511-20904-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun May 15 14:23:22.673 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:19.172
BugCheck FE, {5, fffffa8005f281a0, 10024396, fffffa80065e0c48}
Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveControlEndpoint+57 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_PollActiveControlEndpoint+57
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`05f281a0 00000000`10024396 fffffa80`065e0c48
BiosVersion = 1401   
BiosReleaseDate = 06/11/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051511-21403-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 14 23:18:50.219 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:30.328
BugCheck FE, {5, fffffa8005e0b1a0, 10024396, fffffa8003a79c48}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`05e0b1a0 00000000`10024396 fffffa80`03a79c48
BiosVersion = 1401   
BiosReleaseDate = 06/11/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050211-60575-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  2 01:15:15.859 2011 (UTC - 4:00)
System Uptime: 2 days 12:10:15.342
BugCheck FE, {5, fffffa8005e3d1a0, 10024396, fffffa80098db750}
Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveControlEndpoint+57 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_PollActiveControlEndpoint+57
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`05e3d1a0 00000000`10024396 fffffa80`098db750
BiosVersion = 1401   
BiosReleaseDate = 06/11/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[jco66mt]

Ty for the quick response. I will run all this stuff. I have a Logitech Mouse and a NETGEAR wireless card. I also have a HP Printer but its wireless also.

 

[usasma]

Here's my canned speech on USB wireless devices:

I do not recommend using wireless USB devices.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Disconnect the wireless USB and see if the BSOD's occur.
Get new drivers for the wireless USB - and ensure that they are Win7 drivers, not Vista drivers.

 

[jco66mt]

Ok great ty I will do that. Had no idea. So far the Memory and HD tests are good.

 

[usasma]

Dunno if this article will help or not:

Binary files in some USB drivers are not updated after you install Windows 7 SP1 or Windows Server 2008 R2 SP1
Binary files in some USB drivers are not updated after you install Windows 7 SP1 or Windows Server 2008 R2 SP1