Another BSOD help request

Slick Twitchy · 04 Jun 2011

I am at wits' end. I am an avid gamer, and have recently installed an ATI 6990 (I was a huge nvidia fan, but their boards couldn't do a specific thing I needed).

Since, the addition of that board I have been getting consistent (once every couple of days BSODs).

They "seem" to have different causes, but I am not sophisticated enough to diagnose.

I would gladly pay someone a reasonable fee (50 bucks for diagnosis). More if it was complicated...

I have attached the requisite files, but I could provide more if needed.
- Win 7 x64 ?
- the original installed OS on the system was Vista 64-did a complete reinstall- full retail version?
The age of system (hardware) varies- system ios about 1.5 years old, but GPU, and RAM are additions
I just installed WIn 7 on a SSD drive.

Attachment 158088

zigzag3143 · 04 Jun 2011

Slick Twitchy said:

I am at wits' end. I am an avid gamer, and have recently installed an ATI 6990 (I was a huge nvidia fan, but their boards couldn't do a specific thing I needed).

Since, the addition of that board I have been getting consistent (once every couple of days BSODs).

They "seem" to have different causes, but I am not sophisticated enough to diagnose.

I would gladly pay someone a reasonable fee (50 bucks for diagnosis). More if it was complicated...

I have attached the requisite files, but I could provide more if needed.
- Win 7 x64 ?
- the original installed OS on the system was Vista 64-did a complete reinstall- full retail version?
The age of system (hardware) varies- system ios about 1.5 years old, but GPU, and RAM are additions
I just installed WIn 7 on a SSD drive.

Attachment 158088

Memory corruption probably caused by video driver.

Please re-install newest video driver like this and run memtest and driver verifier.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Slick Twitchy · 05 Jun 2011

Thanks for the quick reply.

Memory seems ok. I ran Memtest for 6 passes.

I ran the verifier and the system eventually crashed, but I don't know where any of the data was stored.

System is crashing with different BugCheckString PFN_List_Corrupt....

I have always updated, and cleaned drivers, but I did it again for good measure.

I am at a loss (as usual..)

Slick Twitchy · 05 Jun 2011

Here is some newer information (I just updated to Win 7 SP1), and it completely screwed my system up. I can't play any of my games now without a BSOD within 3 minutes (wah!!).

Things are getting progressively worse as I try to fix things....

zigzag3143 · 05 Jun 2011

Slick Twitchy said:

Here is some newer information (I just updated to Win 7 SP1), and it completely screwed my system up. I can't play any of my games now without a BSOD within 3 minutes (wah!!).

Things are getting progressively worse as I try to fix things....

80 % of these relate to your video subsystem (video driver, card, memory, power, heat). I would re-install the driver using this method and re-install directX.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

You also have a few relating to USB. What devices are on USB?

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050811-35022-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`04200000 PsLoadedModuleList = 0xfffff800`0443de50
Debug session time: Sun May  8 14:46:40.992 2011 (GMT-4)
System Uptime: 0 days 0:44:20.928
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {6, fffffa800716f1a0, 4f444648, 0}

Probably caused by : usbehci.sys ( usbehci!EHCI_InternalPollIsoEndpoint+109 )

Followup: MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000006, USBBUGCODE_BAD_SIGNATURE An Internal data structure (object)
    has been corrupted.
Arg2: fffffa800716f1a0, Object address
Arg3: 000000004f444648, Signature that was expected
Arg4: 0000000000000000

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  DCS.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8800418d14d to fffff80004270740

STACK_TEXT:  
fffff880`03144cb8 fffff880`0418d14d : 00000000`000000fe 00000000`00000006 fffffa80`0716f1a0 00000000`4f444648 : nt!KeBugCheckEx
fffff880`03144cc0 fffff880`0418d0d8 : fffffa80`08939c50 fffffa80`071706a0 fffffa80`08939a10 fffff880`051bbba4 : USBPORT!USBPORT_AssertSig+0x25
fffff880`03144d00 fffff880`051b78c9 : 00000000`0027864e 00000000`0027864f 00000000`00000005 fffffa80`0716f050 : USBPORT!USBPORTSVC_LogEntry+0x2c
fffff880`03144d30 fffff880`051c0aef : fffffa80`07daf750 00000000`0027864f fffffa80`00004001 fffffa80`07fdc620 : usbehci!EHCI_InternalPollIsoEndpoint+0x109
fffff880`03144da0 fffff880`04161e8b : 00000000`00000002 fffffa80`0716f1a0 00000000`00000000 00000000`00000040 : usbehci!EHCI_PollEndpoint+0xbf
fffff880`03144de0 fffff880`041669b1 : 00000000`00000040 00000000`00000004 fffffa80`07daf510 fffffa80`0716f050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`03144e10 fffff880`04172043 : fffffa80`0716f1a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`03144e70 fffff880`04162f89 : fffffa80`0716f050 00000000`00000000 fffffa80`0716fa02 fffffa80`0716fa10 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1af
fffff880`03144ed0 fffff800`0427bbfc : fffff880`03115180 fffffa80`0716fa10 fffffa80`0716fa28 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`03144f00 fffff800`04276865 : 6ecd6ecd`51845184 fffffa80`08259780 00000000`00000000 fffff880`04162db0 : nt!KiRetireDpcList+0x1bc
fffff880`03144fb0 fffff800`0427667c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`06384be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_InternalPollIsoEndpoint+109
fffff880`051b78c9 418d5fff        lea     ebx,[r15-1]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbehci!EHCI_InternalPollIsoEndpoint+109

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc06

FAILURE_BUCKET_ID:  X64_0xFE_usbehci!EHCI_InternalPollIsoEndpoint+109

BUCKET_ID:  X64_0xFE_usbehci!EHCI_InternalPollIsoEndpoint+109

Followup: MachineOwner
---------

Old drivers needing update.

Code:

Alpham264.sys    3/20/2007 5:51:03 AM        fffff880`042be000    fffff880`042c3500    0x00005500    0x45ffae87                        
SiWinAcc.sys    6/14/2007 8:02:02 PM        fffff880`0112f000    fffff880`01138000    0x00009000    0x4671d6fa                        
SiRemFil.sys    6/20/2007 3:42:10 PM        fffff880`01907000    fffff880`0190f000    0x00008000    0x46798312                        
Alpham164.sys    7/23/2007 3:57:03 AM        fffff880`042b1000    fffff880`042bdf00    0x0000cf00    0x46a45f4f                        
SI3132.sys    10/3/2007 2:39:29 PM        fffff880`00dd9000    fffff880`00df3000    0x0001a000    0x4703e1e1                        
k57nd60a.sys    4/26/2009 7:23:05 AM        fffff880`04169000    fffff880`041b1000    0x00048000    0x49f44419                        
spldr.sys    5/11/2009 12:56:27 PM        fffff880`0144a000    fffff880`01452000    0x00008000    0x4a0858bb                        
spsys.sys    5/11/2009 1:20:58 PM        fffff880`04000000    fffff880`04071000    0x00071000    0x4a085e7a                        
GEARAspiWDM.sys    5/18/2009 8:17:04 AM        fffff880`051ea000    fffff880`051f7000    0x0000d000    0x4a1151c0

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Slick Twitchy · 05 Jun 2011

Thanks again. I always follow the guru3d driver cleaner procedure (driver sweeper in safe mode etc.) I did it again to be safe. I removed all of my usb devices (except mouse) and still got BSOD.

I will update drivers. Thanks again. What a pain.....lucky to have guys like you out there.

This happens much more frequently since I installed SP1 (Win 7), and happens immediately when I run Witcher 2 graphics.

zigzag3143 · 05 Jun 2011

Slick Twitchy said:

Thanks again. I always follow the guru3d driver cleaner procedure (driver sweeper in safe mode etc.) I did it again to be safe. I removed all of my usb devices (except mouse) and still got BSOD.

I will update drivers. Thanks again. What a pain.....lucky to have guys like you out there.

This happens much more frequently since I installed SP1 (Win 7), and happens immediately when I run Witcher 2 graphics.

Read here issue with witcher The Witcher 2: Assassins of Kings GPU & CPU Performance - TechSpot Reviews

Slick Twitchy · 06 Jun 2011

Witcher 2 ran pretty well prior to the SP1 update. After that it caused BSOD within a minute or two ALWAYS. I just did a system restore to a point prior to SP1, and the problem went away-with the occasional BSOD that sent me down the rabbit hole in the first place.

Working on updating all drivers per zigzags post.