Ghost crashed windows xp

Due to time constraints, I only tested a few games- ones with problems or suspected problems on Windows on my Windows XP machine. The results were surprising. Of the tested titles, 9 worked perfectly or very close to perfectly on Windows 10, while seven had caveats such as performance issues or requiring a special patch.

Deus Ex : Steam version, tested on Windows 10 only. The game itself worked perfectly on Windows 10, but not on Windows XP. The menu appeared offscreen and was impossible to navigate. Mostly works on Windows 10, but UI performance is terrible and this causes heavy stuttering when UI elements pop up in gameplay.

On Windows 10, it had audio issues out of the box that were resolved with this patch. On Windows XP, everything worked fine out of the box.

I tried cranking up the settings, which completely broke the game and made it basically impossible even to get into the menu. It almost worked perfectly in Windows 10, but stuttered and played music incorrectly.

The disc version almost worked perfectly, but locked up when I tried to quit. Combat Flight Simulator 3 : Unknown disc version, tested on Windows The installer worked but the game refused to start. I am running Windows 7 Professional bit.

I also run Windows XP mode occasionally on this system. I can access the XP C: drive fine. I went through netsetup in XP to give the XP system a different name than my Windows 7 system name although it was already different.

Nothing changed. I disabled my avast antivirus protection on the XP system, but that didn't change anything. Please run the file called PartInfo. This will create a file called partinfo.

Please attach this file to your post by clicking on the Add Attachments link at the bottom. I did a chkdsk and nothing still crashes.

I will do the partinfo thing and then post. Thanks for the updates. I am seeing something a little strange in partinfo for your C drive. Is this a custom built computer? It would appear to be since I don't see the typical diagnostic and recovery partitions that an OEM manufacturer would normally put on. I want to get a second opinion on the Drive C file system type anomaly because I have not seen this before.

Type 0, 1, etc? I got a second opinion from one of my colleagues and he agrees that the partition information for Drive C is not correct. To fix this, you should boot from the Windows XP recovery console and perform a fixboot command.

Please see this Microsoft article and search for fixboot for further details. Fat32 has gotten extended over the years it can now do drives up to 8 Terabytes. One of the reasons I kept FAT32 around was for easy boot access in case of a crash and I needed to pull files off the drive. With a maximum of 32 KB per cluster with space for the file allocation table FAT , this equates to a maximum disk size of approximately 8 terabytes TB.

As for the other two drives, they are regular hard drives and they are not in a RAID array but they are on different controllers. Thanks for the update.

It was not the size of the drive which made it look wrong, it was the fact that one section identified the same drive with a partition type of NTFS instead of FAT But after looking at some more examples I believe this section where it says NTFS can be written in by something other than the OS so this may be ok after all.

Apart from the error code of 0x8e were you able to get any wording and other hex codes from the BSOD? Also, please check the Windows System and Application events and see if there is anything relevant posted at around the time of the BSOD.

Search Advanced search…. New posts. Search forums. Log in. Sign up. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. Thread starter Double07 Start date Dec 3, Status This thread has been Locked and is not open to further replies.

The original thread starter may use the Report button to request it be reopened but anyone else with a similar issue should start a New Thread.