Directinput??DirectX??Memory reference?? What is going on!!!

[meskalin]

SPECS:

Operating system: Win XP Pro
Motherboard: Gigabyte GA-7VAXP
Processor: AMD XP 2500+
Memory: 1536MB Crucial
Graphic Card: ATI Radeon 9700 PRO (latest drivers installed)
Soundcard: Audigy 2
Hard Drives: Maxtor 6YO80PO and 6YO60LO
CD rom: Kenwood 72X Speed
CD/RW: Plextor PX_W4824A
2WIRE modem
DIRECTX 9.0b version


…How I have noticed that my new PC has a problem!

After using the PC for about 3 moths without any major issues a specific problem started to come up more often. After downloading two new demos (TRON 2.0 and XIII) neither of them would run and I would get two different error and warning messages.
One would be referring to direct input and the other one would be about memory reference problem (Listed below).

After opening “dxdiag” now I get a new window with a message, that the last time direct input was accessed there was a problem and it gives me an option to bypass it. If I bypass it, I can use the dx tool but if I don’t it crashes and gives me an error.
I also tried “Planet side” among other applications and same thing happens either the memory reference or direct input fails to get the application running. Couple of times the PC restarted on it’s own with out any reason. I run other app's with out problems (Ravenshiled, Photoshop etc.)

…What I have done!

Updated everything, reinstalled 9.0b directx. Tried out the individual 512 bars of memory but the problem remains with all of them.

I really don’t know what to do but I just want to fix this and what the hack is directinput?

PLEASE HELP

Errors:

Appname:dxdiag.exe Appvers.5.3.0.901 or AppName:planetside.exe AppVers:1.8.5.0 …
ModName:dinput8.dll ModVer.:5.1.2600.1106 Offset:000147cf

Or

A couple versions of this one:

XIII.exe –Application Error

The instruction a “ox77f5952b” referenced memory at “0xfffffff8”. The memory could not be “read”

PLEASE HELP

[meskalin]

ANYONE???

[pam123]

I would consider a repair install of XP.
It sounds like something basic got corrupted.

[mjkovis]

Could be a bad stick of RAM. You havent been messing around on the inside without an astatic wrist band and shocked something, have you? That sounds more like a RAM problem than XP.

[meskalin]

No I was careful to hold on to the case. Besides that I tried out the memory in an diferent computer and it seems it doesnt do that.
Suggesting to reinstall windows is ...well...I'd really really like to do that as the last possible solution....

MAYBE SOMEONE IS OUT THERE WITH AN ANSWER FOR ME...

[pam123]

No I said repair not reformat.
Read this thread :http://forum.pcmech.com/showthread.php?s=&threadid=35662&highlight=repairing+XP

[meskalin]

Sorry thought you were talking about formating...nevermind.
PROBLEM STILL HERE>>>>HELP>>>

[pam123]

Did you try the repair ?

[meskalin]

I will tomorrow....

[meskalin]

OK...now I really don't know what to do. Here is what I have done.

Before trying to repair windows I decided to give it a try once more by replacing the dinput8.dll. I started windows in safe mode and replaced the file.
After rebooting and starting up directx everything looked fine. The directx app didn't crash with the usual message (read above) and I acctually got the XIII demo running. After being so happy and satisfied that I have acctually fixed the problem I went to bed smiling.
The next day everything went wrong. I was getting CRC messagges left and right. I tried to update my ati driver but I could not even unpack the file since it was telling me it was corruped...so was any cd...or any app.....now that's really when I went nuts.
I took the boot discs and restarted windows (saving some of my precious files before) and reformated the whole thing. Reinstalled my Winxp PRO over again.
I've updated everything (doing the system restore) slowly...video drivers, motherboard, etc etc. Everything is fine. I've started directx and it shows that is has 8.1 version on it but it doesn't crash. After all the updating I've created another restore point just before I woulde install directx 9.0b. So I did...and so s*** happend. The app crashed right away with the same dinput8.dll error and right after I've closed it I've got the reference error again.
Now what???? It seems to me that after reinstalling the windows everything was fine until I installed directx. I ahve to mention again that I have used the PC without any problems for a couple of months ...and after I came from vaccation I installed the 9.0b version and I think that's when the problems started. Not totally sure.
OK well now what??? Should I try and replace the memory even it was fine for months and now memorey reference errors were coming up? OR? or?>

PLease please help :confused: :(

[Panama Red]

I have no idea what is causing your problem, but if memory is a possibility and you haven't tested it, do so. Just swapping memory around won't id a faulty stick. Download Memtest86, make a boot disc or boot cd and run it. That way you can eliminate or condemn memory as the problem.

[pam123]

Can you copy the full error out of Event Viewer for me ?
I can search for it in the Microsoft knowledge base and find out what, if anything, they know about it.
I won't be able to get to it till later tonight or maybe tomorrow.

[meskalin]

OK...here is the update.

As you know I have installed win xp pro again and it didn't do much good. The direct input error, merory reference and crc are piling up. So I decided to investigate the hardware a little more. I have tested the memory idividually and out of the three bars (far right socket) one showed a lot of errors. So I took it out and reformated the whole thing. Well ...as you can expect the errors were the same even without that 512. So...I took the memory to my friend that has a similar system and we tested the memory but it came out fine without any errors. I have been doubting the new direct x as a casue of my problem but now i\m starting to thing that it is my motherboard. I don't really have the tools to test my motherboard but since that memory had errors on mine (and all three were from crucial bought at the same time) and it did not have errors on my firends PC I think it's the motherboard. This could explain the CRC errors coming from the cd (connected to the motherboard) and the CRC errors when accessing files on my system hard drive (connected to the motherboard). I guess it coulde also mean that my direct input file is not working properly since the key./mouse are connected to the motherboard, and just maybe my ATI radeon 9700 pro is not working with the new directx beacuse of my motherboard. I don't really really know. These are just guesses.
I still have warrenty on my MB ( gigabyte ga7vaxp) so I'm goning to replace it and hope that the problem will be solved. I will also test my pc with my friends 9700 pro card just to make sure that it is fine.

Now...well I have directx 9.0 installed that came with TRON 2.0 game. And whille I am waiting for a replacment I've only installed tron (don't ask how...it was a tought with all the CRC errors) and that's it. Nothing else on installed. I've crancked up the video card to optimal quality and my eyes are orgasming with the beauty of the TRON game.

The funny thing is :( that because of the dinput8.dll (another guess) my keyboard and mouse are not working like they should. So while I am playing I hit the left mouse button once and it won't stop or the meyboard just goes nuts and well...I just sit and smile :mad: at Jet (TRON) running into walls, jumping of high cliffs, or waisting the disc energy because I can't really stop the mouse.

Well Im still very open to suggestions and thanks for that memory testing utility.
So is it the motherboard? or is it not? what else could it be?

dinput8.dll - crashing applications the link my other post.

[pam123]

I think you're right, and that board seems to have had more than it's fair share of problems.
RMA and try again ( if you can switch it for another try a Soltek ).

[meskalin]

The one thing I consider strange is that I had this board for well over four months and it was just fine. Acctually it was great.Overall, user reviews praise this Gigabyte MB for the most part. I bought another one for a friend but I had problems from the start with it so I replaced it. I can't guess why it went bad on me, I'll never know (if it is the case that the MB is bad).
What model do you recommend from from Solvek.

[meskalin]

Soltek, solvek whatever :)

[pam123]

Understood.
It would be nice if the glitches showed up immeadiately but they don't.
Your board has reputation for causing trouble a few months down the road.
I would replace it.

[meskalin]

What board do you recommend?

[pam123]

Soltek SL-75FRN2

[meskalin]

Well I did go for an gigabyte mobo again. This time it's the GA-7NNXP. I hope that the actual problem was the mobo indeed but I am not going to be sure until I install the mobo.

[meskalin]

Check out "ga-7nnxp thoughts? comments?" thread for more info on the gigabyte mobo's

[meskalin]

OK ok ...here is the scoop.

I have upgraded to the newer Gigabyte motherboard 7NNXP and besides an cd check error (fixed it) everything is as smooth as butter. I am acctually really really happy about the new motherboard since it is giving me everything I need and much more...but..

The same hardware set up as mentioned above except I got the ATI RADEON 9800XT today and switched it with my 9700 PRO. Ofcourse I have uninstalled all the previous software etc. etc.

I connected my 9800XT to the powersupply and put into the AGP slot.

Nof after the software instalation (3.8 catalyst) I wanted to check out directx diagnostics to see if everything is fine ann booooom there it is...the same freakin' error with the dinput8.dll message. I was like ...ahmm..what the hell happend. I don't think I did anything wrong with graphic card installation. Well i reformated everything, reinstalled everything and again...the error message,, dxdiag app crashes as soon as I install the new directx 9.0b

Any comments?
Anyone?

[meskalin]

.

[pam123]

Okay, wait a minute.
Don't buy anything.
I'm wondering about your cd for the OS.
What happens when you do a repair install ?


edit : This was a lapse on my part. My apologies meskalin.

[GaryRouth]

Seems like I remember that Ati drivers can be difficult to completely remove from the registry. Try uninstalling the drivers (switch to Standard VGA in the meantime), from Windows Explorer delete any Ati folders leftover from incomplete uninstalls, run a registry cleaner if you've got one. Install Directx 9 Before you add back the new ATi drivers. Then try the latest version of the Catalyst.

If you then get an error only in a particular game, check it's website for patches - or, if it's a must-have favorite - install the directX from the game's cd.

Praying and prostrating yourself before the PC divinities might help, too :)
. . . Gary

[Edit - hi pam, just saw your post. I still remember that Ati uninstall thread from a while back. I can't remember if that thread was for XP or not = maybe it would help in this spot, too. . . - - - I don't usually jump in to threads over here, but I had some extra time tonight waiting for a file transfer to finish here at work!]

[pam123]

meskalin,
If you have fastwrites turned on turn it off in smartgart as well as in the bios.


Gary,
Thanks for the reminder.
I'll go check now.

[pam123]

Originally posted by meskalin
OK ok ...here is the scoop.



Nof after the software instalation (3.8 catalyst) I wanted to check out directx diagnostics to see if everything is fine ann booooom there it is...the same freakin' error with the dinput8.dll message. I was like ...ahmm..what the hell happend. I don't think I did anything wrong with graphic card installation. Well i reformated everything, reinstalled everything and again...the error message,, dxdiag app crashes as soon as I install the new directx 9.0b

Any comments?
Anyone?

Okay can you download and replace the file ?
Go here : http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=dinput8.dll&btnG=Google+Search

and use this site : http://www.dll-files.com/dllindex/dll-files.shtml?dinput8
You may want to check out a few more sites so that's what the google page is for.

[meskalin]

Thanks again for trying to help out. The Dll download site, I have already been there and replacing the dll file doesn't work I have done it before and it just made things worse. Besides it's really an old version of the file.
I have spent about 5 hours trying to find out more information about this .dll problem and all I am able to find is people with the same problem, Win XPPro, upgrading directx, new graphic hardware or an joystick or something but I have not really found an solution.
There is not one that is working.
They say to install the service pack for windows which I did and it didn't do anything.
I am wondering if this .dll problem could have been created by my wireless keyboards, I doubt it but maybe.
I also now that its not definetly the motherboard or any of the hardware in my pc.
I will keep looking but so far no luck for a solution.

The thing I am really bummed about is that after puting the Radeon 9800TX in the computer and immidiatly after that checking the dxdiag has been corupted with that dinput8.dll file.
LIke I mentioned above I immidialty reinstalled and reformated everything from ground up and the problem shows up right after upgrading to directx 9.0b. I don't really understand how it can show up when originally after putting the pc with this new mobo (ga7nnxp) the problem was not there.
Maybe taking out the battery and redoing everything inclouding the bios will do something.
Right now I created a restore point right before installing the directx 9. The direct x version is 8 I think I the error doesn't happen. I will install the service pack etc. and then directx 9 to see if it help otherwise I have to go back again and install everything over again.

[pam123]

Keep us posted.
Would you also tell us exactly how you set up your computer after the XP install ?
Uninstalling games can whack dll files but just installing DX9 shouldn't.

[meskalin]

I sure will and as I said there was not much installed, since I updated the directx right after finishing all the major installations and updates...so.
I don't understand why the error keeps on coming back even after the reformat and I'm even more confused why I got it twice but with different hardware.
Any way I will do the whole set up from ground up, using a regular key. and mouse just because this dinput8.dll has to do with input devices.
I'll post comments probobly tonight.

[meskalin]

What do you want to know as far as setting up the XP.
I have two harddrives where I split the 80 gig into a 15 gig system and a 65 gig for programs like logic or simply games, I also download stuff onto a seperate drive (mp3, etc etc.)

What else do you want to know?

[pam123]

Okay, I'm making some assumptions but here goes.
Basic hardware : you've replaced the motherboard, replaced the video card and tested the ram. Everything passed.
Your ps is a good one.
You've checked out all the cables and you know your mouse and keyboard are good and you're not using any mouseware programs.
I think you've shown it isn't hardware.
Something is corrupting your XP installs either before they're complete or very soon after.
So install XP, check.
Install recent mobo drivers, check.
And now install DX 9, I'd burn it to a cd and use that.
Check again. It should show up on dxdiag first page. Don't run dxdiag until you've loaded the drivers for the 9800XT.
If all is well in go the video drivers and then do glc's trick, reinstall DX 9.
So you have motherboard drivers, DX9 and video drivers.
If it turns around and gives you the same error you won't have to search far for the culprit.
Since XP is so picky about hardware I'm betting it's a program or something about how you set it up that's causing the trouble.
My only other suggestion is that you load "optimum defaults" in the bios and save any special adjustments for later.
The fewer things you have to sort out the better.

[meskalin]

OK I have finally solved the two main issues that were causeing a lot of headaches on my part. The dinput8.dll and the cd check erorr (cd error-post).
I am 100% sure that the dinput8.dll was corupted by my wireless keyboard. Since I went back reformated, reinstalled everything, step by step updating, graphic, sound chip set driver etc. and I would still get that damn error. Since dinput8.dll is a dll for input devices I just decided to try with a diferent keyboard and a mouse and can you belive it, it works. I have acctually put my wireless keyboard on again since now I can use the dxdiag or anything with out any problems and if they come up again, now that I actually know what was causing it, it's gonna be easy to repair/fix it.

One other thing I am concerned about is the Nvidia SW driver (came with my giagbyte instalation cd and follows up the chipset instalation).
The Nvidia SW driver replaces the ATA drivers that come with WIndows with drivers that are optimized for nforce2 based hardware.
Sw supposedly reduces the storage sub systems bottleneck, enabling the processor and other sys. level hardware to be more productive and efficiant.

"...nforce2 platform processors can significantly reduce the CPU time requird to retrive data from/ or store on HD (or other IDE devices) using the IDE logic inside nforce2 MCP and nforce2 MCP-T"

Now my other problem with this mobo was the IDE device communication, like the cd not being recognized even if it is in the cd rom. Like I said before I have set the primary/secondary chanells to PI0 and the problem was solved but in all acctuallity it didn not work because of the SW drivers. When I choose not to install the Nvidia SW driver, that error doesn't show up and under IDE ata/atapi controllers I end up with Nvidia MCP2 driver.
Now you might think its all good since I have actually fixed the causes of my pc problem but...I dont know if I am imaginig this that my pc is slower with out the SW driver.
The cd instalations seems to take longer, burning a cd takes longer, browsing is slower or pretty much everything ..if I did not go crazy I'd say that I really need that SW driver...but if I put it on the system doesnt work right and just like gigabyte said in the SW read me file....that it is a "as is" and "may cause problems"

I contacted Gigabytes tech support today and ofcourse ..they were really helpfull. What a waist of 30 minutes, it would have been better if I called myself and talked to myself for 30 minutes lol. Blah blah they can't help me the regular b s***.

NOw I guess I need to know since I don't have enough knowlege about this ...is my system gonna be fine with out the sw or ...what should I do.
Nvidia also offers a unified driver, but I read that it fixes mostly the audio (dolbydigital) issues and I use audigy 2 so....


Thanx

[pam123]

Wow !!!
You got it !
There are new Nfoece drivers just out :http://www.elitebastards.com/ go here and scroll down till you see the news and the link.
They may be the answer to your questions or your alternative may be the custom install ( which is tricky but you can ask one of the other Nforce2 owners to walk you through it. My upgrade won't happen till later this month so my experience with NF2 boards is limited, also I don't have a wireless keyboard).
Just a suggestion though.
There is a sticky over on the processor/motherboard forum about NF2 boards.
I think your post would be a classic.

[meskalin]

Hey Pam

Since everything is working fine, I decided to make things worse lol. I am not a gambler but I went and installed the 3.13 over the old drivers without unistalling anything.
I did create a restore point.
To my surprise everything worked out fine! So far so good, even the SW driver is installed now and I don't get my usual error, but like I said so far so good...hope my pc is not going to melt into a yellow blob when I power it on next time.
I am going to sleep for a couple of days and nights, you know just to catch up with all the sleepless nights I have been infront of my LSD I mean LCD monitor, surly I'll dream about overclocking my Gigabyte to a whooping warp speed and I will have about trilion fps with the 9800XT.

Good night and until the next time :D

[pam123]

Glad to hear it.
Just copy your solution to the sticky in Motherboard/Processors ( the one that reads Nforce )and you will have added to everyones' fund of knowledge.

[meskalin]

How do I do that with that sticky?

[pam123]

Doing it for you now.

edit : Okay, you're on the thread.
This was a highkight>edit>copy--and then unhighlight.
This goes to the copy board.
To paste it, when you get to the point in the new post where you want it it > edit >paste. And there it will go.

[meskalin]

I was looking around in my BIOS settings and I was wondering if you know what :

advanced AGP aperture size -64M- (set to 64 but can be set from 32 to 512)
and AGP fast wrtie cababilty _enabled

[pam123]

Aperture setting is a legacy from when video cards had 4mb of ram.
The old rule that it should be half your ram is now really out of date. For most uses 64mb will do or, if you're a really major gamer, you can up it to 128mb.
Fast writes enables the video card and the processor to talk to each other directly.
It doesn't really give much speed and it's a notorious cause of sysem instability even with boards that support it properly. Thus the standard advice for smartgart is " turn off fast write both there and in the bios ".

[meskalin]

I had to go back to the 2.41 drivers since actually my system was performing better then with th enew 3.13 drivers.

Anyway Pam, I told you I am an beginner so I am going to ask a beginners question. You know my system specs so ...how much improvment will I see if I max out my memory from 1,5g to 3g (thats the max I think). In what "departments" will I be able to see the improvments? This much memory and 9800XT what wil that do?

[meskalin]

Anyone???

[mjkovis]

You wont see much of a difference from 1.5GB to 3GB of RAM because there is nothing out there that even needs to use that much space. I have 1.5GB and the highest memory usage I have seen was 27%. And that was using a lot of programs at once. You may see some help in the internet side, but nothing drastic or noticably different.

[meskalin]

Thanx

[pam123]

Hi meskalin,
Acid-Klutch is pretty much right.
Unless you have some professional level CAD programs, or you're a home movie enthusiast who likes to craft his own special effects, 3GB of ram is overkill.