CRASH - gameex no worky

[deano7]

I turn on my puter, run gameex and it crashes every time. Attached is the log and settings.

Anyway, I tried to repair .net 2.0 and it crashes during install. My computer now reboots itself if I try to run Mame. What would you guys do to try and fix the problem? Pretty much no matter what i do I am a crashing.

Thanks in advance.

crash_6_22_08.txt

[shaunopp]

I turn on my puter, run gameex and it crashes every time. Attached is the log and settings.

Anyway, I tried to repair .net 2.0 and it crashes during install. My computer now reboots itself if I try to run Mame. What would you guys do to try and fix the problem? Pretty much no matter what i do I am a crashing.

Thanks in advance.

Startup problems are often caused by themes. Try changing the theme in your GameEx config file.

[Brian Hoffman]

Startup problems are often caused by themes. Try changing the theme in your GameEx config file.

I thought that may be the case also but usually you will see a direct x error. Not this error

--**--

15:18:10.1 6/21/2008: ERRORS DETECTED: EXITING

15:18:10.1 6/21/2008: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

15:18:10.2 6/21/2008: at q.b3()

15:18:10.2 6/21/2008: at q.am()

Id clear your temp files and do a chkdsk.

[bkenobi]

Yeah, that could be a corrupted page file. If running check disk doesn't work, you could try reducing the page file size to 0 (or close to 0), rebooting, then increasing the size again. This *should* result in a reallocation of the page file on a new section of the hard drive. It's possible fragmentation could be an issue (when was the last time you defragged?), but I was pretty sure the page file occupied a single contiguous chunk on the drive.

It's also possible the message is exactly right in that you have corrupt memory. If that's the case, then memtest86 could help.

Incidentally, I had a problem with my system locking up at strange times. I thought it was heat, video card, HDD issues, etc. In the end, it turned out to be mismatched memory. I was using DDR, so it shouldn't have been an issue, but for whatever reason it was. If you have multiple sticks, you could check to make sure they are matched. If that's the issue though, you are probably running on a pretty skimpy system...