[RESOLVED] System Reboot

[wolff]

Im having a Directx direct input error I believe, the games play fine through MAME32 by itself but if I try to launch the games from gameex it reboots my whole computer. This is a very frusrtating problem. I have a screen shot of what I get on the first attempt to launch gammex and then the second time I can get into gameex and launch a game only to reboot again. The video card is an onboard one with the latest drivers its a nvidia geforce 7025.

[Tom Speirs]

I have to say Ive not seen this issue before. It sounds like it may be something that is only affecting you. I don't have any idea of a fix but you could try disabling direct input support (custom input) for the keyboard.

[Brian Hoffman]

That is quite an interesting error, it indicates a memory issue. If I were you, I would remove a stick of ram from your machine, then try again. If it does it again, then swap and remove the other ram module.

Perhaps you have some bad memory.

[hansolo77]

That is quite an interesting error, it indicates a memory issue. If I were you, I would remove a stick of ram from your machine, then try again. If it does it again, then swap and remove the other ram module.

Perhaps you have some bad memory.

I'm thinking the same thing. When I saw that, I thought "Bad Memory". There are a few memory testing programs out there. I would try Brian's suggestion, to find the culprit. Then test it throroughly with a memory testing program to make sure it's not something serious. Might have to replace it.

[wolff]

I'm thinking the same thing. When I saw that, I thought "Bad Memory". There are a few memory testing programs out there. I would try Brian's suggestion, to find the culprit. Then test it throroughly with a memory testing program to make sure it's not something serious. Might have to replace it.

Why would I be able to actually get into gameex the second time and get as far as starting a game? And why would it reboot? Shouldnt I get a blue screen first?

[hansolo77]

Not necessarily. The computer uses RAM "randomly" (hence the acronym "Random Access Memory"). There could just be a bad block in the memory that's corrupted. If you can figure out which RAM module isn't working right, a Memory Testor program can actually mark the bad block, and not try to use that part of the memory again. Your computer may work fine forever until it hits that bad block, then you get those kinds of problems.

Now, SOME programs are designed to run in a specific memory location. I think a lot of Windows OS runs in dedicated memory locations. So you might not ever see any kinds of problems.

As for the Blue Screen, it depends on the problem. Usually a Blue Screen error is something inside the Windows OS failing. If the memory fails, your computer's motherboard and/or bios may be configured to perform a hard reset if such things occur.

Something else to look at is the part of the error that's causing it. It clearly shows the failure at reading/writing protected memory and this may be related to corruption.. The other part is that it's shows what's flagged the error: DirectX-DirectInput. That is why Tom suggested disabling the direct/custom input. It might be a simple thing as a driver issue. But that's just what tried to use your memory. The memory is probably the problem. Disabling the input might just be a temporary solution.

[wolff]

Not necessarily. The computer uses RAM "randomly" (hence the acronym "Random Access Memory"). There could just be a bad block in the memory that's corrupted. If you can figure out which RAM module isn't working right, a Memory Testor program can actually mark the bad block, and not try to use that part of the memory again. Your computer may work fine forever until it hits that bad block, then you get those kinds of problems.

Now, SOME programs are designed to run in a specific memory location. I think a lot of Windows OS runs in dedicated memory locations. So you might not ever see any kinds of problems.

As for the Blue Screen, it depends on the problem. Usually a Blue Screen error is something inside the Windows OS failing. If the memory fails, your computer's motherboard and/or bios may be configured to perform a hard reset if such things occur.

Something else to look at is the part of the error that's causing it. It clearly shows the failure at reading/writing protected memory and this may be related to corruption.. The other part is that it's shows what's flagged the error: DirectX-DirectInput. That is why Tom suggested disabling the direct/custom input. It might be a simple thing as a driver issue. But that's just what tried to use your memory. The memory is probably the problem. Disabling the input might just be a temporary solution.

The input for the keyboard is disabled by default and I used to work for geek squad and just so happened to have a piece of software that test memory real well and im currently testing it now. I'm also going to run everything on another machine and do the same setup I've been doing to see if I get the same thing.

[Adultery]

Ive seem this error, and it was indeed a bad stick. Other programs were also affected though. MemTest helped me diagnose it... I let it go for an overnight to be sure.

Hope it's not new RAM!

[hansolo77]

Geek Squad sucks. Maybe it's just because I know so much already. I never went to college, and sometimes I think I know more than those graduates anyway. Plus, it really sucks because if you want any kinda job dealing with that kinda stuff, you HAVE to have a degree, and certifications.. stupid if ya ask me.

[wolff]

Geek Squad sucks. Maybe it's just because I know so much already. I never went to college, and sometimes I think I know more than those graduates anyway. Plus, it really sucks because if you want any kinda job dealing with that kinda stuff, you HAVE to have a degree, and certifications.. stupid if ya ask me.

I know they suck Ive been in the IT field for about 6 years now and I only went there for extra money and I didnt stay long because non of them knew anything except "we can send it in for warranty work" I felt like I worked with 1st graders.

[wolff]

I know they suck Ive been in the IT field for about 6 years now and I only went there for extra money and I didnt stay long because non of them knew anything except "we can send it in for warranty work" I felt like I worked with 1st graders.

I have solved all problems that I was having by installing Windows 7 so the only thing I can think of is some type of corrupt file in windows Xp that I have. But a new problem has come up, a certain few roms wont start such as asteroids, mrs pacman, galaga,and a few others. I have typed in to accept these roms they show up in the list but when initialized the screen acts like its going into game but goes back to the menu any ideas?

[Adultery]

Have you audited your roms?

[wolff]

Have you audited your roms?

How do I do that?

[Adultery]

Well there's a few ways. The method I use is clrMAMEpro. It's a handy little tool that checks your MAME roms and makes sure everything you need is in there for the version you're using. Just download the DAT for your MAME version and do some googling or ask here if you get stuck.

[wolff]

Well there's a few ways. The method I use is clrMAMEpro. It's a handy little tool that checks your MAME roms and makes sure everything you need is in there for the version you're using. Just download the DAT for your MAME version and do some googling or ask here if you get stuck.

I really dont know what it is I need to do I clicked on DAT and I saw files like for cabinet, snaps etc, is that it? I mean the ROMS for the games that try to start in gameex will play in just the regular mame32 program so I'm not sure what to do . I looked at the HELP menu in MAME and its .037 Beta is what I saw. I hope this makes somewhat of sense.

[Adultery]

Could you right click the MAME executable and look and see what the version number is please?

[headkaze]

An "Attempted to read or write protected memory" error is not in any way indicative of bad RAM chips. It is .NET's security preventing access to protected memory.

[hansolo77]

HA! I figured I might be going in the wrong direction. I was going on the 2nd sentence in the error: "This is often an indication that other memory is corrupt". Being .net (according to hk) is a good indication that it's outside my knowledge area. I was wondering why just upgrading the OS would have solved the problem. One of these days, I hope to learn .net and those new webcodes called PHP, ASP, etc.

[headkaze]

Since it's an error raised when enumerating joystick and keyboard devices using DirectInput I would have tried unplugging the keyboard and joystick to see if the error went away.

[wolff]

Since it's an error raised when enumerating joystick and keyboard devices using DirectInput I would have tried unplugging the keyboard and joystick to see if the error went away.

I will try this and if the error goes away what do I do? I mean I need the joystick obviously.

[headkaze]

I will try this and if the error goes away what do I do? I mean I need the joystick obviously.

That was before you updated to Windows 7. I was just saying it was likely not a RAM issue.

Adultery is on the right track with your latest problem so continue to follow his instructions.

[wolff]

Could you right click the MAME executable and look and see what the version number is please?

The Version is 3.1082. Ive tried a few things and some games i can get into and other it loads to the control panel screen to show you what button to use and then exits back to the play this game menu. How do I audit or make these games work within Gameex?

[Adultery]

The version number I'm looking for would start with 0.??? unless you're using MAME32 or something. Then the MAME version number is under HELP>ABOUT in the GUI.

[wolff]

The version number I'm looking for would start with 0.??? unless you're using MAME32 or something. Then the MAME version number is under HELP>ABOUT in the GUI.

The version is 0.122u1, its mameui32

[Adultery]

Okay. Now what version is your rom set for? How long you had them?