fatal exception 0E...

[sape]

“Fatal exception 0E has occurred at 0028:C000A4B0 in VXD VMM(01) + 000094B0. The application will be terminated. Press any key …”
That same F***ing notice with blue screen comes almost always when play any games (usually CMR2, GP3,NFS Porche).
When I press any key, the game will close down, and Windows goes to desktop (not crash down).

My combination is:
AOpen HQ45D, 250W ATX -case
ECS K7VZA v.1.0 mobo with 1.1g bios
Duron 750
2x128 Mb
W98SE
DX8
Elsa Cladiac geforce MX
I use mobo’s integrated audio chip
Motorola’s Rockwell chip -based 56k PCI-modem
Microsoft’s FFWheel in game port

I have tested VIA4in1 v. …24, …29, and nowadays v. …132
Nvidia’s detonator 6.50, 7.58, Elsa’s few latest drivers (now Elsas latest based Nvidias 12.40 detonator)
There seems not to be any conflict in any irq’s (in control panels-system page).

This blue screen comes only when playing, sometimes almost at once sometimes even a hour, but generally always. All other programs (Office2000, surfing with internet explorer 5.5) works fine. There seems to be something doing with 3d.
I have tried all kind of bios settings (I've read geforcefaq.com very permanently) which are available. I have tried to only with one memory module and tried to change those places. Memory modules are similar PC133’s.
Is there any experience on that ECS mobo or something else incompatible between Duron/VIA-chips/Geforce-cards?
How about Radeon DDR ?

I feel , I have fight with this too long! Please give me a tip what to do !

 

[butchrecon]

Did you try a different Video Card? If you can get ahold of another Gforce MX and try it. Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.


James Collins
Computer Hardware Engineer
A+, MCP

email: butchrecon@skyenet.net

 

[Sam177]

I'm getting the same blue screen error, while playing NFSorche. It happens with in a few mins or so into the game.

My system

AMD DURON 650 MHz
K7TPRO MS-6330 motherbord
512 mb of PC-133 RAM
20 gb and 50 gb hardrives
ALL IN WONDER 128 PRO video card (32 mb of video memory)
Windows 98 Second Edition

My system is a fresh OS. I had other problems the other day, so I fdisk and formatted C: /u/s

I don't have many program reinstalled on it yet, so I can't think what's could be the matter. I thought this problem as well as the others would not reappear after the new re-install.

PLEASE HELP!

 

[sape]

This all seems to happen when I use wheel. All other games with pad or even these racing games playing on keyboard works without crashing. There seems to be something doing with wheel or force effect....

 

[Sam177]

Sape, you may have a point there. I'm using MS Sidewinder Force Feedback wheel. It's the older serial port version, not USB.

 

[sape]

As specified above, I have the same wheel...

 

[Guest_imported]

OK... IT IS THE WHEEL - I try ANYTHING to make my System work - NOTHING helps - yesterday I bought a different wheel (Thrustmaster FF) - IT WORKS FINE!!!!! - NO BLUESCREEN with C000A4B0 - 000094B0!!!!!
I dont know the Prob with the Microsoft wheel, but I think it is the Gameport. TAKE USB! Try to take an Adapter from GAME to USB or an new Wheel with USB!!!

 

[ped]

OK....There's only one way to get around this until Microsoft come up with a fix for this....DISABLE THE FORCE FEEDBACK effects as it's definitely this that's causing the blue screen. You can do this by opening Regedit and going to:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\Microsoft SideWinder Force Feedback Wheel\OEMForceFeedback\Effects

Click on 'Effects', then in Registry menu(in Regedit), click 'Export registry file'...Save the details as whatever you want....This is to backup your registry keys unless something goes wrong

Next, delete the entire 'Effects' key and close Regedit...This will have disabled your force feedback, but you'll still have tension in your wheel. And there you have it...no more blue screens!!

 

[Guest_imported]

I had exactly the same problem on my sytem

Athlon Thunderbird 800
Epox 8KTA+ (VIA KT133)
396 MB RAM PC133
LeadTek Geforce 2MX
Microsoft Sidewinder Force Feedback Wheel

when I used the internal gameport. When I read your thread I've searched for a cheaper solution than buying a new wheel. And I found it!
I've deactivated the internal sound and gameport and plugged a TerraTec PCI soundcard. And now it works great. No Bluescreens at all.
I think it was a problem with the VIA drivers...

 

[Sam177]

I'm sure, it is the force feedback issue with the serial version of the Microsoft Sidewinder wheel to cause the crashing. This was the only time, I ever received this type of blue screen. It's not memory module problems, processor problems or whatever. I even upgraded to a different motherboard (Shuttle) with a AMD 1.33 GHz processor. Same VIA drivers though. It still crashed, esp. while playing NFS: Porche Unleased.

I never got a chance to troubleshoot disabling the FFB in the registry as someone suggested. In the meantime, I upgraded my OS to Windows 2000. This action solved my problems: I can now play all my NFS games without any crashing. My force feedback wheel works great in Win2000 with no problems what so ever!

(Knock on wood) I will never go back to Windows 98 (What a piece of crap). I will stay with Windows 2000.

Sam

 

[nighteyes]

Eventually thanks to you people I have managed to find out what this exception error means. I have exactly the same problem. Is Microsoft releasing a patch for the wheel or just ignoring the problem?

 

[ped]

Nighteyes - I have since found out from the Microsoft Support site....It is indeed a problem to do with the force feedback on MS Wheels and it's compatibility with a particular soundchip: the AC 97. I suspect, like many others on this forum you are using this chip, which usually comes in the form of sound integrated into the motherboard. The solution: to get a new soundcard, or alternatively disable the force feedback altogether. As I cannot afford a new soundcard yet, I have chosen the latter method(see the registry tweak in my earlier post). I have had no problems at all since doing this.
This is a problem that Microsoft can do nothing about, as it appears it's more of a hardware limitation than a software problem.