Author Topic: Cougar Owners (Read 1188 times)

FOGOLD · « **Reply #15 on:** March 12, 2003, 05:35:05 AM »

Think I'm getting this tracked to a definite USB/Cougar problem in my VIA mobo. Tried a cheapo stick, ran all last night on offline sitting on RW. Still purring away this morning.
Cougar drivers and Cougar on board the thing would have locked solid 10 mins to 3 hours in!

A powered USB hub looks in order here!

Will fly with Top Gun Afterburner this week see what happens, but I'm really hoping I cracked it.

Heater · « **Reply #16 on:** March 12, 2003, 09:20:24 AM »

FOGOLD

Wheh the system locks does it creat a dump file? (check the Windows directory under minidumps) check the date time stamp on the file to check which one relates to the lock-up and Post or send me the file.

Cheers

FOGOLD · « **Reply #17 on:** March 12, 2003, 10:11:31 AM »

These two dump files were there, but I've been getting a lot more lockups than that in AH.

These two might not be anything to do with it.

Here they are anyways. Thanks:)

FOGOLD · « **Reply #18 on:** March 12, 2003, 10:12:36 AM »

Other one

Reschke · « **Reply #19 on:** March 12, 2003, 11:38:42 AM »

Fogold,

Which Via chipset motherboard is it? I have an ASUS A7V266 that the Cougar would drop out when it was plugged into the spare ports that ASUS sends with the board. But it works fine when I have it plugged into the ports directly under the PS/2 connections. Also with my trouble I can't get the newer versions of the software to load my drivers no matter if I use a powered USB hub or not. You might want to check http://www.viaarena.com/ for the new 4-in-1 drivers for version 4.46 if you have the KT266 chipset they have a newer beta USB filter patch for it.

Good Luck!

FOGOLD · « **Reply #20 on:** March 12, 2003, 12:10:58 PM »

Thanks, yes I'll try that. If you look at Cougar World theres a lot of stuff on that new driver problem and a 2.03 version which loaded for me ok. I am rapidly coming to the conclusion that there are problems with the Cougar and USB, especially on VIA boards.

What bugs me is that I suspect I could go to the hassle of reinstalling the whole PC and find the problem is still there. What's the point of that? Also I'm pretty busy and family life etc, I don't have time for all this troubleshooting. I have time for Aces High now and again and thats it. If I cant solve this soon, I'm afraid the game and Cougar are going to have to take a hike!

qts · « **Reply #21 on:** March 12, 2003, 03:15:54 PM »

Fogold, there are issues with VIA and USB full stop. Get yourself an add-on card.

DonULFonso · « **Reply #22 on:** March 12, 2003, 03:48:53 PM »

Quote

Originally posted by qts
there are issues with VIA and USB full stop.

Well, I for one never had any issues prior to 2.02
although I've got a VIA-chipset etc. -
what beats me is that only since the 2.02 update,
which included new USB-drivers for the Cougar,
I not only happen to have all sorts of issues with it,
but that these issues turned out to be the rule rather than the exception!

I had posted links to at least some of these new major bugs on TM's official forum,
asking them to at least say something (even a negative reply is better than none, IMHO!),
and in the meantime I at least got this comment on that topic:

Quote

Posted by TM CFC over at TM's official forum
Just to let you that the guys are indeed aware about these issues
and will get to them as soon as they are assigned to do so.
They are currently working on other projects.

Let's just wait and see - but I for one don't dare to hold my breath

...

FOGOLD · « **Reply #23 on:** March 13, 2003, 01:06:17 AM »

Get yourself a different stick more like! There are 8 USB ports on this board and any other device works fine;)

Heater · « **Reply #24 on:** March 13, 2003, 12:20:31 PM »

FOGOLD.

ALL of the dumps are related to the the driver BsUDF.sys this is a appears to be CD-ROM driver for NEC it a conflict between the Thrusmaster driver and this one but the actual dump is being caused by the BsUDF.sys driver

any here is the back trace from the dump all 3 look the same:

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

Loading Dump File [D:\Temp\Dumps\Mini031103-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
Executable search path is: C:\windows;C:\WINDOWS\system32
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Tue Mar 11 17:41:02 2003
System Uptime: 0 days 0:02:28.562
Loading Kernel Symbols
............................. ............................. ............................. ............................. ...............
Loading unloaded module list
...
Loading User Symbols
Unable to load image BsUDF.SYS

*** ERROR: Module load completed but symbols could not be loaded for BsUDF.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D5, {8c910ea8, 0, ede3fcab, 0}

*** ERROR: Module load completed but symbols could not be loaded for tmpreflt.sys
Probably caused by : BsUDF.SYS ( BsUDF+10cab )

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

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

Arguments:
Arg1: 8c910ea8
Arg2: 00000000
Arg3: ede3fcab
Arg4: 00000000

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

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD5

LAST_CONTROL_TRANSFER: from ede3c5c4 to ede3fcab

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f78867c4 ede3c5c4 00074800 82953a60 00000000 BsUDF+0x10cab
f7886824 ede593ec 8291ff04 8291fe80 8291fe84 BsUDF+0xd5c4
f7886864 ede5721c fc35b520 8291ffc8 8291fe80 BsUDF+0x2a3ec
f7886888 ede4e0de fc35b520 82943e48 82943e48 BsUDF+0x2821c
f78868f8 ede3f5b2 fc35c430 82943e48 82943e48 BsUDF+0x1f0de
f7886918 ede3f732 fc35c430 82943e48 fc35c430 BsUDF+0x105b2
f788692c 804eca36 fc35c430 82943e48 806c91a8 BsUDF+0x10732
f788693c 80647111 82943e48 82943ff4 82a23ec0 nt!IopfCallDriver+0x31
f7886960 f87e9ddf fc3595f8 82943e48 828a2000 nt!IovCallDriver+0x9e
f78869ac f87ea407 fc3595f8 82943e48 fc3595f8 tmpreflt+0x2ddf
f78869f4 8055c3bb 828a2030 806c9158 f7886b3c tmpreflt+0x3407
f7886a44 804dd63e fc3595f8 f7886b00 00000000 nt!IopMountVolume+0x1d1
f7886a74 80582bc4 82a28540 828a2030 f7886bac nt!IopCheckVpbMounted+0x59
f7886b68 8057f6f0 828a2030 00000000 faf6f008 nt!IopParseDevice+0x3ba
f7886bec 80581aba 00000000 f7886c2c 00000040 nt!ObpLookupObjectName+0x56a
f7886c40 80583172 00000000 00000000 80594901 nt!ObOpenObjectByName+0xe9
f7886cbc 8058324e 0029fe2c 00100001 0029fe40 nt!IopCreateFile+0x407
f7886d04 80585258 0029fe2c 00100001 0029fe40 nt!IoCreateFile+0x36
f7886d44 804da140 0029fe2c 00100001 0029fe40 nt!NtOpenFile+0x25
f7886d44 7ffe0304 0029fe2c 00100001 0029fe40 nt!KiSystemService+0xc4
0029fe84 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4

FOLLOWUP_IP:
BsUDF+10cab
ede3fcab 8b4618 mov eax,[esi+0x18]

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: BsUDF+10cab

MODULE_NAME: BsUDF

IMAGE_NAME: BsUDF.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3c3c54fa

STACK_COMMAND: kb

BUCKET_ID: 0xD5_BsUDF+10cab

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

SOB · « **Reply #25 on:** March 13, 2003, 04:03:59 PM »

Imagine that...an end user incorrectly diagnosing a problem. I can hardly believe it!

SOB

Reschke · « **Reply #26 on:** March 13, 2003, 04:32:58 PM »

Quote

Originally posted by FOGOLD
Get yourself a different stick more like! There are 8 USB ports on this board and any other device works fine;)

Like I mentioned with my other post I had no trouble with any other devices on the spare ports on my motherboard but I did with the Cougar. The Cougar simply uses alot of power and that is why so many people have been going to powered USB hubs. My particular issue is unrelated to that and might be caused by a screwed up SP1 install. As of now I can't track it down and I ahve no idea when I will get around to formatting my harddrive and starting over again.

milnko · « **Reply #27 on:** March 16, 2003, 06:10:48 AM »

Hey SOB,

You got that URL for the digital pot upgrade handy?

Thinkin' of upgrading my Cougar, as I've hadda clean the throttle pot once and the stick Y axis twice.

FOGOLD · « **Reply #28 on:** March 16, 2003, 04:29:45 PM »

Sorry folks. Led you all a merry dance. Been flying with a tm Afterburner2 and still getting intermittent lockups. So I've been through every possibility and Im going to have to reinstall windows XP from scratch. If that doesn't work I'm shagged. It must be hardware somewhere.

How do i clean install. Do I boot from a win98 floppy and FDISK C:>?

Then change BIOS to boot from CD, insert CD and off we go?

Thing I don't get is what I did. I don't have millions of games on this machine!!

SOB · « **Reply #29 on:** March 16, 2003, 10:30:42 PM »

Heya Milenko...I don't remember if there's actually a web page for that mod or not. Check the hardware forums over on Cougar World, and I'm sure you'll be able to find it!

SOB