Repeated Windows XP Crashing

JediEyeCandy · Post by **JediEyeCandy** » Thu Feb 14, 2008 4:34 pm

I've racked my brain and can't figure out a solution.

I have Innerspace on two machines, my vista box and my xp box.

oddly enough, my Vista box works flawlessly.

My XP box crashes repeatedly after opening the game through Inner Space. I run no plug ins or extensions, I just use Inner Space so that I can use a keyclone program.

Sometimes the game runs well for a few minutes, then the computer crashes and stops responding, must be rebooted. I occasionally also see a graphical distortion.

Inner Space is the only thing causing the crash. Game runs fine for hours on end without it, runs fine with the KeyClone program running. AS soon as I throw Inner Space into the mix, repeated crashing ensues.

I have updated my graphic drivers, .net framework drivers, direct x, motherboard drivers, everything I could think of. i've re-installed both Inner Space and EQ2 and Keyclone, etc.

Any suggestions?

Post by **Lax** » Fri Feb 15, 2008 8:57 am

Well, Inner Space is usermode software. This means that it doesn't have access to any resources that should normally cause the entire system to crash/freeze/reboot/etc (if just the game crashed, that'd be a different story). Anything it does has to pass through the Windows kernel and any drivers, and if one of those is not performing properly, it can cause a crash. If any of your hardware is bad or going bad, this can cause crashes too. For example, if your video card fan got clogged with dust over time and stopped spinning, then it will be more prone to overheating, especially when playing 3D games. Your mention of graphical distortion points to the video card.

So.. here's what you must do:
1. Check for new drivers for your video card. With any luck, your video card is not damaged, and new drivers will solve the problem.
2. If that doesn't help, then based on the information given, you probably need to replace the video card. It has probably been overheating, and may be physically damaged.

JediEyeCandy · Post by **JediEyeCandy** » Fri Feb 15, 2008 4:59 pm

Thanks for the help...

While that could possibly be the issue, the card is brand new. The drivers are up to date.

I can dual box Everquest 2 on it no problem, and there are no crashing issues whatsoever until I run Inner Space.

JediEyeCandy · Post by **JediEyeCandy** » Fri Feb 15, 2008 5:37 pm

After some more experimenting...

I can leave it at the login screen for an hour. No crash. As soon as I log in, within 30 sec to 2 min, crashes. Without Inner Space on, runs flawlessly.

I use Profit UI and EQ2 map, going to try it without Profit installed, see if that does anything.

JediEyeCandy · Post by **JediEyeCandy** » Fri Feb 15, 2008 6:03 pm

Removed profit and eq2 map.

The ONLY graphical distortion on the whole screen is the Inner Space overlay at the top left of the screen. The game has no graphical errors, windows, nothing.

The text in the Inner Space area is blurry when the computer locks up, it gives it odd characters and blurs it out upon system lock up.

Post by **Lax** » Sat Feb 16, 2008 9:38 am

Okay. In that case, it sounds similar to issues people have had in the past. It had to do with video drivers, and simply installing the latest drivers did NOT solve the problem. However, these people could UNINSTALL their video drivers, and then cleanly install the latest drivers, and the problem would go away.

Try that and let me know

JediEyeCandy · Post by **JediEyeCandy** » Sat Feb 16, 2008 2:32 pm

Still no go. Removed and reinstalled drivers, still gives me the crashing problems.

JediEyeCandy · Post by **JediEyeCandy** » Sat Feb 16, 2008 10:14 pm

also tried using older drivers for the card, no good.

Post by **Lax** » Sun Feb 17, 2008 8:24 am

Does the IS uplink look normal? If you right click and select "Patcher" or "Console" or "Configuration", the Uplink window opens up, and this is a 3d rendered environment with the same UI system that would be used on top of EQ2.

It would help to know what kind of PC you're using -- processor, video card, amount of RAM specifically. If you open up the console in the uplink and type "diag", some system diagnostic info will open up in notepad, if you can paste that here for me that might help.

JediEyeCandy · Post by **JediEyeCandy** » Sun Feb 17, 2008 3:16 pm

I can open the uplink, and it looks normal. Sometimes, the computer crashes when I open the uplink configuration also. I opened the console... system crash.

Inner Space Kernel 1.09 Build 4604

System:
-----------------------------------
Windows Version: Microsoft Windows 2000/Service Pack 2/2600.xpsp_sp2_rtm.040803-2158
Process Memory Usage: 15MB
System Physical RAM: 1735/2046MB
Page File: 5821/5985MB
Virtual Memory: 1976/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ @ 2009MHz
CPU 2: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ @ 2009MHz
CPU Affinity Mask: 0x3
Video 1: \\.\DISPLAY1/NVIDIA GeForce 7600 GS
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Sound: ?
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180

Loaded Modules:
-----------------------------------
Module 0x00400000-0x004A2000: C:\Program Files\InnerSpace\InnerSpace.exe (Wed Dec 19 15:16:13 2007)
Module 0x00D40000-0x00D8F000: C:\WINDOWS\system32\DRMClien.DLL (Wed Aug 04 06:03:47 2004)
Module 0x00E60000-0x010C0000: C:\WINDOWS\system32\d3dx9_30.dll (Fri Mar 31 19:32:20 2006)
Module 0x01130000-0x0114E000: C:\Program Files\InnerSpace\IS-D3D9Engine.dll (Fri Jul 20 14:16:07 2007)
Module 0x01170000-0x011A9000: C:\Program Files\InnerSpace\IS-VirtualInput.dll (Sat Dec 22 15:49:07 2007)
Module 0x03000000-0x03162000: C:\Program Files\InnerSpace\IS-Kernel.dll (Sat Feb 16 14:29:11 2008)
Module 0x05000000-0x05148000: C:\Program Files\InnerSpace\ISUI.dll (Mon Aug 20 16:25:03 2007)
Module 0x0FFD0000-0x0FFF8000: C:\WINDOWS\system32\rsaenh.dll (Wed Jul 07 02:17:12 2004)
Module 0x10000000-0x1001E000: C:\Program Files\InnerSpace\Lavish.dll (Tue Oct 30 17:12:23 2007)
Module 0x4B320000-0x4B349000: C:\WINDOWS\system32\wmidx.dll (Wed Aug 04 07:56:56 2004)
Module 0x4FDD0000-0x4FF76000: C:\WINDOWS\system32\d3d9.dll (Wed Aug 04 07:56:03 2004)
Module 0x59A10000-0x59A4C000: C:\WINDOWS\system32\WMASF.DLL (Wed Aug 04 07:56:47 2004)
Module 0x5AD70000-0x5ADA8000: C:\WINDOWS\system32\UxTheme.dll (Wed Aug 04 07:56:43 2004)
Module 0x5CB70000-0x5CB96000: C:\WINDOWS\system32\ShimEng.dll (Wed Aug 04 07:56:42 2004)
Module 0x5D090000-0x5D127000: C:\WINDOWS\system32\COMCTL32.dll (Wed Aug 04 07:56:31 2004)
Module 0x60610000-0x60616000: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\fusion.dll (Wed Oct 24 03:28:45 2007)
Module 0x662B0000-0x66308000: C:\WINDOWS\system32\hnetcfg.dll (Wed Aug 04 07:56:16 2004)
Module 0x688F0000-0x688F9000: C:\WINDOWS\system32\HID.DLL (Wed Aug 04 07:56:12 2004)
Module 0x6CE10000-0x6CE48000: C:\WINDOWS\system32\DINPUT8.dll (Wed Aug 04 07:56:32 2004)
Module 0x6D990000-0x6D996000: C:\WINDOWS\system32\d3d8thk.dll (Wed Aug 04 07:56:02 2004)
Module 0x6F880000-0x6FA4A000: C:\WINDOWS\AppPatch\AcGenral.DLL (Wed Aug 04 07:55:58 2004)
Module 0x71590000-0x71604000: C:\WINDOWS\AppPatch\AcLayers.DLL (Wed Aug 04 07:55:59 2004)
Module 0x71A50000-0x71A8F000: C:\WINDOWS\system32\mswsock.dll (Wed Aug 04 07:59:20 2004)
Module 0x71A90000-0x71A98000: C:\WINDOWS\System32\wshtcpip.dll (Wed Aug 04 07:57:49 2004)
Module 0x71AA0000-0x71AA8000: C:\WINDOWS\system32\WS2HELP.dll (Wed Aug 04 07:57:39 2004)
Module 0x71AB0000-0x71AC7000: C:\WINDOWS\system32\WS2_32.dll (Wed Aug 04 07:57:38 2004)
Module 0x71AD0000-0x71AD9000: C:\WINDOWS\system32\WSOCK32.dll (Wed Aug 04 07:57:51 2004)
Module 0x73000000-0x73026000: C:\WINDOWS\system32\WINSPOOL.DRV (Wed Aug 04 07:56:38 2004)
Module 0x736B0000-0x736B7000: C:\WINDOWS\system32\msdmo.dll (Wed Aug 04 07:57:53 2004)
Module 0x74D90000-0x74DFB000: C:\WINDOWS\system32\usp10.dll (Wed Aug 04 07:56:42 2004)
Module 0x75A70000-0x75A91000: C:\WINDOWS\system32\MSVFW32.dll (Wed Aug 04 07:59:15 2004)
Module 0x76380000-0x76385000: C:\WINDOWS\system32\MSIMG32.dll (Wed Aug 04 07:58:31 2004)
Module 0x763B0000-0x763F9000: C:\WINDOWS\system32\comdlg32.dll (Wed Aug 04 07:56:32 2004)
Module 0x769C0000-0x76A73000: C:\WINDOWS\system32\USERENV.dll (Wed Aug 04 07:56:41 2004)
Module 0x76B40000-0x76B6D000: C:\WINDOWS\system32\WINMM.dll (Wed Aug 04 07:57:10 2004)
Module 0x76BF0000-0x76BFB000: C:\WINDOWS\system32\PSAPI.DLL (Wed Aug 04 07:56:58 2004)
Module 0x76C30000-0x76C5E000: C:\WINDOWS\system32\WINTRUST.dll (Wed Aug 04 07:56:41 2004)
Module 0x76C90000-0x76CB8000: C:\WINDOWS\system32\IMAGEHLP.dll (Wed Aug 04 07:56:25 2004)
Module 0x76D60000-0x76D79000: C:\WINDOWS\system32\iphlpapi.dll (Wed Aug 04 07:56:10 2004)
Module 0x76F20000-0x76F47000: C:\WINDOWS\system32\DNSAPI.dll (Wed Aug 04 07:56:45 2004)
Module 0x76F60000-0x76F8C000: C:\WINDOWS\system32\WLDAP32.dll (Wed Aug 04 07:56:43 2004)
Module 0x76FB0000-0x76FB8000: C:\WINDOWS\System32\winrnr.dll (Wed Aug 04 07:56:35 2004)
Module 0x76FC0000-0x76FC6000: C:\WINDOWS\system32\rasadhlp.dll (Wed Aug 04 07:56:24 2004)
Module 0x77120000-0x771AC000: C:\WINDOWS\system32\OLEAUT32.dll (Wed Aug 04 07:57:39 2004)
Module 0x771B0000-0x77256000: C:\WINDOWS\system32\WININET.dll (Wed Aug 04 07:57:08 2004)
Module 0x77260000-0x772FC000: C:\WINDOWS\system32\urlmon.dll (Wed Aug 04 07:56:37 2004)
Module 0x773D0000-0x774D2000: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll (Wed Aug 04 07:55:56 2004)
Module 0x774E0000-0x7761C000: C:\WINDOWS\system32\ole32.dll (Wed Aug 04 07:57:38 2004)
Module 0x77920000-0x77A13000: C:\WINDOWS\system32\SETUPAPI.dll (Wed Aug 04 07:56:32 2004)
Module 0x77A80000-0x77B14000: C:\WINDOWS\system32\CRYPT32.dll (Wed Aug 04 07:56:01 2004)
Module 0x77B20000-0x77B32000: C:\WINDOWS\system32\MSASN1.dll (Wed Aug 04 07:57:23 2004)
Module 0x77BE0000-0x77BF5000: C:\WINDOWS\system32\MSACM32.dll (Wed Aug 04 07:57:03 2004)
Module 0x77C00000-0x77C08000: C:\WINDOWS\system32\VERSION.dll (Wed Aug 04 07:56:39 2004)
Module 0x77C10000-0x77C68000: C:\WINDOWS\system32\msvcrt.dll (Wed Aug 04 07:59:14 2004)
Module 0x77D40000-0x77DD0000: C:\WINDOWS\system32\USER32.dll (Wed Aug 04 07:56:40 2004)
Module 0x77DD0000-0x77E6B000: C:\WINDOWS\system32\ADVAPI32.dll (Wed Aug 04 07:56:23 2004)
Module 0x77E70000-0x77F01000: C:\WINDOWS\system32\RPCRT4.dll (Wed Aug 04 07:56:30 2004)
Module 0x77F10000-0x77F56000: C:\WINDOWS\system32\GDI32.dll (Wed Aug 04 07:56:07 2004)
Module 0x77F60000-0x77FD6000: C:\WINDOWS\system32\SHLWAPI.dll (Wed Aug 04 07:56:44 2004)
Module 0x78130000-0x781CB000: C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1433_x-ww_5cf844d2\MSVCR80.dll (Wed Oct 24 03:02:06 2007)
Module 0x79000000-0x79046000: C:\WINDOWS\system32\mscoree.dll (Wed Oct 24 07:35:46 2007)
Module 0x79E70000-0x7A3FF000: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll (Wed Oct 24 07:41:29 2007)
Module 0x7C800000-0x7C8F4000: C:\WINDOWS\system32\kernel32.dll (Wed Aug 04 07:56:36 2004)
Module 0x7C900000-0x7C9B0000: C:\WINDOWS\system32\ntdll.dll (Wed Aug 04 07:56:36 2004)
Module 0x7C9C0000-0x7D1D4000: C:\WINDOWS\system32\SHELL32.dll (Wed Aug 04 07:56:39 2004)
Module 0x7D790000-0x7D99A000: C:\WINDOWS\system32\WMVCore.dll (Wed Aug 04 07:57:33 2004)

Display
-------------------------------------
Adapter resolution: 1280x1024
Current display mode: 792x566 (windowed)
Window viewable size: 792x566
Display Scale: 100.0%x100.0%, Distortion: 0.0%
MaxFPS Foreground: 60 (Calculate)
MaxFPS Background: 30 (Absolute)

Post by **Lax** » Sun Feb 17, 2008 5:04 pm

Well, something's borked in your PC and I can't tell you exactly what. Some people in your situation would opt to reformat and do a fresh installation of Windows, which would likely solve your problem unless it's a hardware problem.

The system crashes described at random times along with graphical distortion really points to a problem with your hardware or drivers (more likely hardware). If I were to guess, based on personal experience at home and when I worked as a PC technician, I would probably start by checking the video card. Typically what happens is the fan on the video card acquires dust over some period of months (quicker for people who smoke in the house), and if it's not blown out it will slow the fan and eventually stop it from spinning (or some other mechanical failure in the fan). Then it starts overheating, particularly when playing games, and this can result in artifacts, freezing, bsod/reboots, and so on. Why it would happen with IS and not without it, I couldn't tell you, but IS is using standard Direct3D functionality.

Now here's a good question: What is the error from the system crash? Typically there's an error code (e.g. ), and it names a driver, like nvdisp, which would be your NVIDIA video driver. This would be a pretty definite indicator that it's related to your video driver or video card itself.

If it were me, I'd start by trying the video card from the Vista box to rule out the video card itself. If everything works fine, then I'd replace the video card. If that didn't solve it, I would use one of my old hard drives temporarily to do a fresh installation of Windows XP, update it with SP2 and whatnot, install appropriate drivers, and try that. If everything works fine, then that means it's definitely because of something installed on the PC.

JediEyeCandy · Post by **JediEyeCandy** » Sun Feb 17, 2008 6:29 pm

Did a complete wipe and reformat and reinstall already. Installed nothing but XP Pro Corp, Eq2, Inner Space, KeyClone, and the required driver updates and DX and such. Still having the same problem.

I'll try trading out video cards and see if that works. Can't use my Vista box card, its too big (8800) to fit in the case of the XP Box.

The card in the XP box is brand new, I've had it for maybe 2 weeks. So it can't have fan spinning problems, and EQ2 runs flawlessly without IS running. It is an Asus card, but its using Nvidia drivers (EN7600)... didn't have any probs with that box other than trying to run IS. Not sure why its conflicting with IS. I'll try switching cards I suppose.