Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: falcon23 on March 23, 2008, 10:05:50 PM
-
Hey guys,been having problems with game locking up to blue screen and would like to type out ehre what it says,and maybe I can fix the problem...
it says something about drivers,like,make sure they are updated or something.and then some numbers and such.
Technical INFO:STOP:0X0000008E(0X00000005,0XB5AF0A68,0X0000000)
And on a seperate line it has the following: SAIH075C.SYS-ADDRESSB5D929F4 base at B5"I think 5 and not an S in that space"D89000,DATE STAMP 4369ebdb
I am wondering if it has to do with my SAITEK SYSTEM?
But whatever it is,it is getting very irritating,and any help in working this bug out would be greatly appreciated..
Thanks,
Kevin
-
Here is my DXDIAG
------------------
System Information
------------------
Time of this report: 3/23/2008, 22:49:49
Machine name: FEESHYBUSTERS
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254)
Language: English (Regional Setting: English)
System Manufacturer: HP Pavilion 061
System Model: EW171AV-ABA a1520y
BIOS: BIOS Date: 06/22/2006 Ver: 08.00.12
Processor: Intel(R) Pentium(R) 4 CPU 3.06GHz (2 CPUs)
Memory: 2048MB RAM
Page File: 300MB used, 3129MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: NVIDIA GeForce 8600 GT
Manufacturer: NVIDIA
Chip type: GeForce 8600 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0402&SUBSYS_C7573842&REV_A1
Display Memory: 512.0 MB
Current Mode: 1280 x 1024 (32 bit) (75Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.5827 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 5/11/2007 07:03:00, 5421312 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 5/11/2007 07:03:00, 6738432 bytes
Device Identifier: {D7B71E3E-4742-11CF-314D-5CE700C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0402
SubSys ID: 0xC7573842
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
-------------
Sound Devices
-------------
Description: Realtek HD Audio rear output
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_103C2A3D&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RtkHDAud.sys
Driver Version: 5.10.0000.5523 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 12/5/2007 18:30:36, 4632576 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Standard
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
---------------------
Sound Capture Devices
---------------------
Description: Line in/Mic in
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: RtkHDAud.sys
Driver Version: 5.10.0000.5523 (English)
Driver Attributes: Final Retail
Date and Size: 12/5/2007 18:30:36, 4632576 bytes
Cap Flags: 0x0
Format Flags: 0x0
-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: n/a
Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: Not run
-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Saitek X52 Flight Controller
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x075C
FF Driver: n/a
Device Name: Saitek Pro Flight Rudder Pedals
Attached: 1
Controller ID: 0x1
Vendor/Product ID: 0x06A3, 0x0763
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x1002, 0x4375
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 2/28/2006 07:00:00, 57600 bytes
| Driver: usbd.sys, 2/28/2006 07:00:00, 4736 bytes
----------------
Gameport Devices
----------------
------------
PS/2 Devices
------------
+ Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 2/28/2006 07:00:00, 52736 bytes
| Driver: kbdclass.sys, 2/28/2006 07:00:00, 24576 bytes
|
+ HID Keyboard Device
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 8/3/2004 23:58:36, 14848 bytes
| Driver: kbdclass.sys, 2/28/2006 07:00:00, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 02:01:08, 40840 bytes
| Driver: kbdclass.sys, 2/28/2006 07:00:00, 24576 bytes
|
+ Microsoft PS/2 Mouse
| Matching Device ID: *pnp0f03
| Service: i8042prt
| Driver: i8042prt.sys, 2/28/2006 07:00:00, 52736 bytes
| Driver: mouclass.sys, 2/28/2006 07:00:00, 23040 bytes
|
+ HID-compliant mouse
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 2/28/2006 07:00:00, 23040 bytes
| Driver: mouhid.sys, 2/28/2006 07:00:00, 12160 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x046D, 0xC50E
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 2/28/2006 07:00:00, 23040 bytes
| Driver: mouhid.sys, 2/28/2006 07:00:00, 12160 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 02:01:08, 40840 bytes
| Driver: mouclass.sys, 2/28/2006 07:00:00, 23040 bytes
-
I recommend installing the INF files for your monitor. You can probably get them from the manufacturer's website.
Realtek Audio is an integrated sound chip, IIRC. Those things are nothing but trouble and even if they don't break, they'll drag your performance way down since they use system resources (instead of their own) for processing and storage.
-
It does appear to be the Saitek drivers, but they may not be the cause of the crash, just the result of something else. Try playing the game withouth the Saitek drivers loaded and see if it still crashes.
-
Z,
What would the INF files do for me?
Skuzzy,just totally delete my drivers for the x-52?and run the game like that??
Man I can sound really ignorant sometimes when it comes to COMP stuff.. ;)
Kevin
-
Instead of knowing that it has a monitor, the computer would know what make/model, brand, and type of monitor you have along with how it operates and its abilities, especially refresh rates.
-
Z,
What would the INF files do for me?
Skuzzy,just totally delete my drivers for the x-52?and run the game like that??
Man I can sound really ignorant sometimes when it comes to COMP stuff.. ;)
Kevin
I think skuzzy is referring to the saitek profile making software that comes with the stick. It's been a long time since I've owned
a saitek, but I think the software is SST something or another.
-
AHHH...I see,yes I do run the SST programming software,and I had got a recent updated one,but got rid of it and went back to the older one due to the fact that in the newer one I could not print out my settings..
Kevin
-
I just noticed something. Did you add that vide card to the computer? The CPU is the older Prescott Pentium 4 which was discontinued long before the 8600GT became available. I am just wondering if there is a heat or power supply issue at work here as well.
-
The CPU is the older Prescott Pentium 4 which was discontinued long before the 8600GT became available.
Really? I could swear that back when I got my "clean" 6800, I could've sworn Prescott's were just breaking in...I remember buying a last-generation Northwood (bought the last one from NewEgg for the girl :D) for the whole heat issue.
-
You lost me OOZ. I was talking about falcon23's machine.
-
Is it possible for an old mother board to be the problem of causing overheating?
Pardon the comp illiteracy.
-
Is it possible for an old mother board to be the problem of causing overheating?
Pardon the comp illiteracy.
Not from my experience, inadequate CPU cooling (heatsink and fan), poor air flow throughout the case which usually means poor cable
management, or for example you have a large full tower case and only one or two 80'mm fans. Also, if the graphics card gets too hot it will
crash on ya. Only thing you can do about that really is to like I said have good cable management, get one of those PCI graphic card coolers (I've never used one nor bought one for another machine so I don't know how well they do.
Of course, you can always buy an after market heatsink and fan for your graphics card (I've never had to do that) but that option is available.
If it's a power issue on falcons machine (That graphics card requires a plugin from the power supply just like hard drives and cd-roms do.)
The reason skuzzy brings up the Prescott P4 is they run notoriously hotter than the previous generation (Northwoods) and therefore he may not have adequate CPU cooling. Same reason he brings up the power issue, he may have a weak power supply or a failing power supply. Also falcon, did you try running Aces High without the SST software running? You can set your stick up in Aces High just like with the SST due to HTC's very well written (coded) joystick button mapping.
-
You lost me OOZ. I was talking about falcon23's machine.
I also have a 6800 and a P4 Northwood core...I was just saying my memory recalls that the Prescotts were getting into their mid-term age back when I built the machine...I could be wrong though.
-
Prescotts came after Nortwood and falcons machine has an 8600GT series video card which is a pretty new card. Much newer than the Prescott.
I bring it up as that video card is also power hungry and if he just slapped it in there without thinking about the power supply, it could be the cause of his troubles.
-
I did upgrade my PSU to a 500W enermax with 22@ on 2 12v. rails..I tried to return this card recently and the 2 they sent me to replace it with did NOT have the molex power adapter and they told me,they had done away with it on the card,and it would now operate fine without the extra power..I kept my original one..
The card under LOAD runs about 80C.
I have not yet got rid of the SST programming drivers...but plan on trying it without..
Any program to run that will show me if my PSU is actually PuTTING out what it should??
Thanks,
Kevin
-
Oh, 8600? I read 6800. Sorry. :D
falcon, best would be to get a multimeter and test the connectors physically instead of having a motherboard based sensor do it.