Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: FOGOLD on March 10, 2003, 03:34:19 AM
-
Copying message I put on Frugals world. I am convinmced this is causing lockups.
SYSTEM VERIFICATION ERROR INSTTUB 201.SYS (WDM DRIVER ERROR 20E) STTUB 201.SYS + 1941 AT EF4A09
No one seem interested in this yet Microsoft says all drivers MUST pass verification! This is the MAIN HOTAS DRIVER FOLKS. I am getting lockups and I want to know if this error is causing uSB problems. I have e-mailed Thrustmaster (no reply). Everyone else tells me to reloas Windows blah blah.
Is this driver porked or not?
"Windows 2000 Driver Verifier
By Mark Russinovich of Systems Internals http://www.sysinternals.com
Windows 2000 is introducing a very powerful device-driver development aid called Driver Verifier. This tool works with code in the kernel to gain control of your driver and exercise it for adherence to kernel-mode rules in a way that was not previously before possible. Buggy device drivers are by far the most significant contribution to the reputation among many people that NT is an unstable operating system, and this tool is aimed at repairing that reputation by helping driver writers find their bugs before users do.
"Several types of subtle problems can make it through casual driver testing (the most common type of testing performed under tight time-to-market constraints), and even slip through serious stress tests. One type of common driver problem is a driver accessing paged memory at "elevated IRQL" (high interrupt priority). If the memory the driver accesses happens to be physically present at the time of the access (it hasn't been paged out to the paging file), then the illegal access will go unnoticed. Release a driver that violates this rule out into the wild-world-of-users and its bound to show up, resulting in a Blue Screen crash.
Another type of common driver programming error is for a developer to write the code with the assumption that paged and/or non-paged memory will always be available i.e. they don't check the return values for allocations. If pool runs out and the driver receives a NULL buffer address the driver merrily de-references the system into a Blue Screen. Although pool exhaustion is a rare occurrence, it's not something that should give a System Administrator a Blue Screen. A related memory bug is a buffer overrun or under-run, where a driver reads or writes outside of a buffer it has allocated."
Verifier also in XP
-
Trying 1.04 drivers. If that doesn't work Cougar is going in the skip.
-
Originally posted by FOGOLD
Trying 1.04 drivers. If that doesn't work Cougar is going in the skip.
whadda ya mean 'going in the skip?'
Thanks for that tidbit too, since I'm thinkin I'm gonna order a cougar in the next day or three.
-
Now the error is "STDRIVER>SYS". I wish Cougar World BBS would reply either confirming or denying my suspicions about this.
Going out to buy a regular USB stick and see of it stops the locks.
-
Fogold,
That is something I have not seen in dealing with the Cougar for nearly a year. When you installed the Cougar did you have any error's? Did you get the E901 or E900 error's about the Cougar not being connected? How long have you had the Cougar working and was it working fine then just started going out on you? Lastly did you install any other hardware or software after installing the Cougar? I am asking that part because I think that my issues with the newest software for it 2.02/2.03 is related to me installing SP1 for WinXP then trying to install the new software. When I go to install the new versions they will install correctly but I am unable to load the driver for the Cougar. XP tells me that it can not locate the correct .inf file to run the devices and I don't get an option to select them at all. I have not heard back from TM Support either and it has been several weeks since I last contacted them.
-
I have had no problems with the Cougar superficially, it all installed fine and no conflicts. BUT , when I think back to changing from MS Sidewinder to Cougar last June, I think the lockup problems started then.
The only way XP throws a problem is if you run "verifier"from the command line, you get a blue screen with the above message. You reboot into safe mode, run verifier again and delete the existing settings.
There's something fishy.
Anyhow. I have just bought a Thrustmaster Top Gun Afterburner 2 for £30 and will try it for a week. If I still get lockups I'll know I'm off the track and will reinstall windows and forgive the Cougar.
I must confess, I think the Cougar is overcomplex and overpriced for what is essentially a game, and all that modding and new gimbals and such is just lunacy.
Of course, you would think othewr people would be suffering, but the hard lockups are so random and intermittent a lot of people might just shrug and say that's life (like discoes and CTD). But I cant stand being an hour into a TOD and having a lockup.
-
Not sure if it is relevant or not, but I haven't had any blue screens in the time I've had my Cougar with Win2k. All original drivers off of the CD.
SOB
-
I'm running XP and have not had a lockup yet with a Cougar installed since they were released.
MiniD
-
Well, I as well never had a BSOD caused by the Cougar,
but all sorts of other problems,
such as random and even frequent dis-connects / drop-outs,
corrupted (no message but no response until after re-flashing)
and even vanishing (all of a sudden the compiler complains) flash,
and all sorts of driver-issues that made me turn off this XP-service...
[rant]
As for TM and what they might / can / will do...
well, since they themselves love to link to CW
whenever you report something or ask for help or info
in their "official but not meant to give support" forum (their words, not mine),
I should have thought that they at least monitor CW's forums to stay informed -
unfortunately, I've just been told by James himself that this is not the case,
so that TM actually doesn't have the slightest idea that there might ;) be e.g. some disconnection-problem etc. ...
That's no joke (unfortunately) but real life comedy (but not funny at all),
but since the main problem is to get Mark and David to work on reported issues
this means that whatever issue must be officially known to TM
(yep, the rest of the world doesn't matter, it's that easy)
so that the bosses can decide to spend some time on it (or not)...
So, James advised me to contact TM,
which could be funny since their official forum is almost as helpful as Windows' recycle-bin
(and twice as dead, since only those poor souls who don't find an answer here go there),
and it always takes a lot of time and even more luck to get a reply there -
which is more than you usually get when you send 'em an e-mail
(their e-mail address seems to be a direct link into their recycle-bin :rolleyes: )...
To cut it short:
I don't have the slightest idea what might cause these problems -
after all, it could as well be MS' fault (like this DX8.1 on non-XP system thingie) -
but I can't help the feeling that TM won't do much to solve 'em...
[/rant]
I still hope that they work on solving the current problems,
but I guess I needn't point out that without any sign o' life - let alone progress! -
it's rather hard to swallow the situation "as is" and the obvious - and valid, IMHO - comments!
(Maybe they should make the firmware open source ;) ,
hoping that some users might do their work
just like they did - and still do - with the hardware :rolleyes: -
on the other hand, the to be expected prices sure would suck :p ...
Hehe - some fine day maybe some proud owner of such a million dollar kitten
might wonder what it would be like to actually program it :rolleyes: -
just to find out that this is almost impossible 'cause nobody cared
when it would have been the time to care 'bout the soft- and firmware :p :
lemme tell ya that nobody of the Cougar-crew is currently working on the Cougar at all :eek: -
take my word 'cause they told me :D !)
-
Originally posted by DonULFonso
lemme tell ya that nobody of the Cougar-crew is currently working on the Cougar at all :eek: -
take my word 'cause they told me :D !)
That is a sad, sad, sad statement right there Don. Dream Mode OnI guess I should have known even though I still have faith that someday one of the big suits will wake up and realize how much they have screwed up. Dream Mode Off
-
They actually made this beast. That alone is a jaw dropping accomplishment. I wouldn't have thought they'd ever care to attempt it.
SOB
-
Its only an accomplishment if it hasn't got buggy drivers.
-
Well, I for one can life with the Cougar's hardware's design-flaws:
it's not perfect and could have been designed better in several ways,
but I wouldn't exaggerate and call it complete crap -
but I sure cannot live without working drivers and firmware!
I think we all agree that we've seen an amazing support until now,
what with many issues being fixed shortly after they've been reported on CW,
and I for one wouldn't have expected them to really increase the no. of flags,
so that has been really good news and good service as well
(while the "new" THR_RANGE simply was adding a necessary feature
they had forgottten in the first place IMHO) -
however, the Cougar's available since more than a year now,
and I doubt that you really can expect 'em to work on it forever -
remember that Guillemot did and still do everything they can to make it a failure:
no support (talking 'bout TM, not CW, mind!),
no news (if you don't state anything you don't have to deny it later),
a batch that by far exceeds all original expectations
but still isn't enough to serve all orders (yep, people still are ordering!), etc.!
They intended to profit of the Cougar's name and reputation
to sell their middle-class Top Guns joysticks -
a fact - not a rumour - pointed out from the start and never denied!
Be it as it is, I sure could imagine that they won't allow Mark and David
to continue their - necessary, mind! - work on the Cougar's soft- and firmware forever -
after all, they wanna make money (perfectly valid for a company)
and the Cougar had been said to be a loss-leader from the start
(THX to Guillemot's initial and continued lack of support, but anyway),
and Guillemot stripped down TM's size by 50% -
think about it:
how long do you think will they allow their (left over) employees
to continue their work on a finished - in Guillemot's eyes - product?!
When they'll have modded their kittens' hardware ad nauseum
and the last gimbal is mounted, the last spring softened,
the last detent flatened, the last hall-sensor soldered,
the last speedbrake rotated and the last dogfight switch realigned,
then they'll find out that their soft- and firmware still are buggy
and that they can't fully and properly use these fine pieces of craftmanship...
I've posted my concerns on TM's "technical issues"-forum,
and the moderator replied he'd talk to Mark and David and see what to do then -
I'm really curious :rolleyes: ...
-
Their French....... as far as the Cougor... they have surrendered already.....
-
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.
-
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.
-
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
-
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:)
-
Other one
-
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!
-
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!
-
Fogold, there are issues with VIA and USB full stop. Get yourself an add-on card.
-
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:
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 ;) ...
-
Get yourself a different stick more like! There are 8 USB ports on this board and any other device works fine;)
-
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
---------
-
Imagine that...an end user incorrectly diagnosing a problem. I can hardly believe it!
SOB
-
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.
-
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.
-
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!!
-
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
-
I have ordered the Hall sensors from cub Pilot for a U2 upgrade for my cougar.
here is the email for the Halls
cougar-hs@att.net
100 US for the pair.
(http://members.optushome.com.au/jg11_ij/Modded%2040.JPG)
-
They are very good and work well not a spike in sight.
However before take off move your stick to the limits and hold for a few seconds.
Every time you start the game your elevators and aelerons deflect very slowly on first use, but once the limits have been found its back to normal instantaneous response.
If you can afford it go for the throttle option as well, like many others mine has been playing up (not getting to max or min at times) which prevents wep kicking in or being able to stop on runways unless you kill the motor.
-
Pongo,
I have a question to ask you about your Cougar insides. Send me an email.
Thanks!
-
That picture is not of my cougar. It is what my cougar will look like once its ubgraded with a Uber 2 mod and Hall sensors..
look here...
mods and tweaks on Cougar hardware forum (http://forums.frugalsworld.com/vbb/showthread.php?s=&postid=360251#post360251)
-
That does look nice there Pongo. Any idea how much the U-2 is going to run us? If it is significantly lower than the Evenstrain then I might look into that a bit earlier than "the other side of never" as IJ puts it.
-
325 US + 100 US for the Hall sensors..+ shipping.
The everstrain is 570 US with halls I think.
The Uber is going to be a drop in part..so you send him money. He sends you parts..you install.
Advantage of replacing all the workings inside the thing.
The feel of the Uber is different then the Everstrain though. The 4 uniform springs on the Everstain take away entirly the transition as you cross the center any one of the axis. The uber absolutly minimizes and smooths the transition, yet it is there to feel as you are flying.
That and the fact that I dont have to send my Cougar away are the big reasons I am doing the Uber instead of the Everstain.