Click to See Complete Forum and Search --> : Windows XP Acting ODD!


bijuabrahamp
July 17th, 2005, 04:29 PM
I had bought a new PC last month (P4 3.2 Ghz LGA775), and installed a fresh copy of Windows XP (SP2). But it was today that I noticed something very strange. This computer was not acting so perfectly as my old one - ofcourse its all to do with the software.
The problem is that, when I type 'cmd' in run, i get a black window like the command prompt but it automatically closes itself in about a second. When I type 'command', it comes properly. Type 'regedit' also causes a similar black window like before which closes itself in a second.
In command prompt, I tried 'ipconfig', it works perfectly.. but when I typed 'netstat', it gives me a horrible error:
Title : 16 bit MS-DOS subsystem
Error : C:\windows\system32\command.com The NTVDM CPU has encountered an illegal instruction. CS:0693 IP:010c OP:c4 f6 a9 02 Choose 'Close' to terminate the application

If I choose Ignore, the error keeps on coming again, so ultimately, I have to try Close. Its very irritating actually and I'm not sure how long this error has been on my computer.

Thinking of this, I feel really :sick:! I tried disabling my McAfee VirusScan Enterprise, but there was no use.
I know many will think of reinstalling my windows... oh.. but thats a really tedious job.. soo many programs are there!

Does anyone have any idea on how to get these things working again?

PeejAvery
July 22nd, 2005, 11:38 AM
Doesn't sound like a virus at all. It just sounds as though you have a 16bit application causing conflicts with a 32bit/64bit OS.

bijuabrahamp
July 22nd, 2005, 02:19 PM
I don't think I have a 16 bit application.. The Processes that are running are:

taskmgr.exe
firefox.exe
alg.exe
YPager.exe
msnmsgr.exe
cftmon.exe
qttask.exe
DC1300mi.exe (Digital Camera stuff)
realsched.exe
TBMon.exe
UpdaterUI.exe
shstat.exe
gcasServ.exe
TotRecSched.exe
SOUNDMAN.EXE
explorer.exe
naPrdMgr.exe
MDM.EXE
VsTskMgr.exe
Mcsheild.exe
FrameworkService.exe
CDANTSRV.exe
AdskScSrv.exe
IEXPLORE.EXE
wowexec.exe
ntvdm.exe
spoolsv.exe
svchost.exe
svchost.exe
InCDsrv.exe
svchost.exe
svchost.exe
wdfmgr.exe
svchost.exe
lass.exe
services.exe
svchost.exe
winlogon.exe
crss.exe
gcasDtServ.exe
smss.exe
FreeRAM XP Pro 1.40.exe
System
System Idle Process

Does anyone see anything odd?

bijuabrahamp
July 22nd, 2005, 02:23 PM
Btw, does anyone know of a good alternate Registry Editor??
I already got an alternate netstat :rolleyes:

PeejAvery
July 22nd, 2005, 02:23 PM
It looks as though one or more of three files is corrupted or missing.

http://windowsxp.mvps.org/16bit.htm

Arjay
July 22nd, 2005, 03:43 PM
I don't think I have a 16 bit application.. The Processes that are running are:

taskmgr.exe
firefox.exe
alg.exe
YPager.exe
msnmsgr.exe
cftmon.exe
qttask.exe
DC1300mi.exe (Digital Camera stuff)
realsched.exe
TBMon.exe
UpdaterUI.exe
shstat.exe
gcasServ.exe
TotRecSched.exe
SOUNDMAN.EXE
explorer.exe
naPrdMgr.exe
MDM.EXE
VsTskMgr.exe
Mcsheild.exe
FrameworkService.exe
CDANTSRV.exe
AdskScSrv.exe
IEXPLORE.EXE
wowexec.exe
ntvdm.exe
spoolsv.exe
svchost.exe
svchost.exe
InCDsrv.exe
svchost.exe
svchost.exe
wdfmgr.exe
svchost.exe
lass.exe
services.exe
svchost.exe
winlogon.exe
crss.exe
gcasDtServ.exe
smss.exe
FreeRAM XP Pro 1.40.exe
System
System Idle Process

Does anyone see anything odd?Something is launching NTVDM.exe and its companion wowexec.exe. There are 32-bit processes that host 16-bit processes). I just verified running \>netstat 5 on Win2003 server and the one I started is definitely a 32-bit process. Try this. Kill NTVDM.exe and start up netstat again (use netstat 5, to launch it in interactive mode and keep the process around). You should see Netstat.exe appear in your process list. If you see NTVDM.exe appear, you are running a 16-bit version of the app.

If this doesn't solve the problem, restart your machine and note if NTVDM.exe appears. If it does, something is getting loaded on startup that is launching the 16-bit process. Look in the run keys in the registry to help determine what.

Arjay

Arjay
July 22nd, 2005, 03:46 PM
Btw, does anyone know of a good alternate Registry Editor??
I already got an alternate netstat :rolleyes:What functionality do you find missing in the current regedit.exe?

PeejAvery
July 22nd, 2005, 09:52 PM
Btw, does anyone know of a good alternate Registry Editor??
I already got an alternate netstat :rolleyes:

Funny, both netstat and regedt32 work just fine for me. What does your 3rd party netstat do differently? I have yet to see a registry editor based like the Windows version. The best I have seen is tweak registry applications.

bijuabrahamp
July 23rd, 2005, 01:20 AM
Funny, both netstat and regedt32 work just fine for me. What does your 3rd party netstat do differently? I have yet to see a registry editor based like the Windows version. The best I have seen is tweak registry applications. Its X-Netstat (http://www.freshsw.com/xns/pro/)

What functionality do you find missing in the current regedit.exe? LOL :D, actually regedit doesnot open as I have mentioned in the first post in this thread

Something is launching NTVDM.exe and its companion wowexec.exe. There are 32-bit processes that host 16-bit processes). I just verified running \>netstat 5 on Win2003 server and the one I started is definitely a 32-bit process. Try this. Kill NTVDM.exe and start up netstat again (use netstat 5, to launch it in interactive mode and keep the process around). You should see Netstat.exe appear in your process list. If you see NTVDM.exe appear, you are running a 16-bit version of the app.

If this doesn't solve the problem, restart your machine and note if NTVDM.exe appears. If it does, something is getting loaded on startup that is launching the 16-bit process. Look in the run keys in the registry to help determine what.

Arjay Ok, I typed netstat 5 in the command prompt.. but the same error comes (as mentioned in the 1st post) and before pressing Close on the error dialog box, I saw that ntvdm.exe is running. But when I pressed Close, ntvdm.exe just vanished. I ran a program called Print Artist 3.0 - an old 16 bit program, thats why ntvdm.exe and wow.. was open.. But now they are not open. Something peculiar about the error is that, the error is caused by command.com - check the 1st post.

Now, I tried netstat 5 in Run.. but the problem is that, a window just appears and closes itself very fast. The same thing happens when I open regedit also. I know regedit is a windows program, but a DOS-like window opens and closes itself automatically (maybe within 1 second) when I run regedit.

It looks as though one or more of three files is corrupted or missing.

http://windowsxp.mvps.org/16bit.htm Unfortunately, I have all these files and I replaced them also.. but this doesnot solve the error.

bijuabrahamp
July 23rd, 2005, 01:22 AM
Actually, I should stress one more odd thing... I can run 'command' from Run .. but not 'cmd'
when I try cmd, a dos-like window appears and closes itself automatically

bijuabrahamp
July 24th, 2005, 03:28 AM
Got a registry program - RegWorks. It works decently.. i think its better than the traditional Registry Editor.

Anyway, thnx for the help

PeejAvery
July 24th, 2005, 04:32 PM
Everything sounds to be really messed up. To me it sounds as though there MIGHT BE a process conflict. I didn't see anyone else mention it. Reboot and go into safe mode. From there, try running cmd.exe. If the problem exists there seriously, I would just format and repartition then install XP WITHOUT SP2. SP2 is garbage.

Arjay
July 24th, 2005, 04:56 PM
Its X-Netstat (http://www.freshsw.com/xns/pro/)

LOL :D, actually regedit doesnot open as I have mentioned in the first post in this thread

Ok, I typed netstat 5 in the command prompt.. but the same error comes (as mentioned in the 1st post) and before pressing Close on the error dialog box, I saw that ntvdm.exe is running. But when I pressed Close, ntvdm.exe just vanished. I ran a program called Print Artist 3.0 - an old 16 bit program, thats why ntvdm.exe and wow.. was open.. But now they are not open. Something peculiar about the error is that, the error is caused by command.com - check the 1st post.

Now, I tried netstat 5 in Run.. but the problem is that, a window just appears and closes itself very fast. The same thing happens when I open regedit also. I know regedit is a windows program, but a DOS-like window opens and closes itself automatically (maybe within 1 second) when I run regedit.

Unfortunately, I have all these files and I replaced them also.. but this doesnot solve the error.Are there any other partitions with other OS's on the machine. It sounds like you are running 16-bit versions. Regedit.exe used to be 16-bit, so one older NT machines 3.51 and before, you used to have to run RegEdt32. On NT4 and higher, Regedit.exe was updated to a 32-bit program. If the only OS install on the machine is your current install, you have some serious issues. I would start in safe mode as suggested by peejavery. And as he says, reinstall the OS if you can't open cmd.exe in safe mode. Also, be carefull about installing 3rd party software from the internet unless you completely trust the vendor.

Arjay

bijuabrahamp
July 25th, 2005, 04:06 AM
Everything sounds to be really messed up. To me it sounds as though there MIGHT BE a process conflict. I didn't see anyone else mention it. Reboot and go into safe mode. From there, try running cmd.exe. If the problem exists there seriously, I would just format and repartition then install XP WITHOUT SP2. SP2 is garbage. Thanks for the suggestion to goto safe mode.. Now I understood there is something seriously wrong!
I can't get into safe mode... I get a blue screen and this written

A problem has been detected and Windows has been shut down to prevent damage to your computer

IRQL_NOT_LESS_OR_EQUAL

and some advices were given saying to enter safe mode etc.

But this error comes only when I enter safe mode

Now, I'm really considering a reinstallation... Btw, do you really recommend installing XP without SP2 because M$ really recommends it in the websites.

Are there any other partitions with other OS's on the machine. It sounds like you are running 16-bit versions. Regedit.exe used to be 16-bit, so one older NT machines 3.51 and before, you used to have to run RegEdt32. On NT4 and higher, Regedit.exe was updated to a 32-bit program. If the only OS install on the machine is your current install, you have some serious issues. I would start in safe mode as suggested by peejavery. And as he says, reinstall the OS if you can't open cmd.exe in safe mode. Also, be carefull about installing 3rd party software from the internet unless you completely trust the vendor. There are two partitions C: and E: and both are NTFS. And Windows is installed in C. I only keep some files in E.
I'm quite careful of what I download, so I don't think its anything to do with what I downloaded


But, the IRQL_LESS_THAN_OR_EQUAL gives me a sensation of something to with my bluetooth stick. I bought a MSI bluetooth stick and this bluetooth things have real compatibility issue with XP... And at the end I got tired because I couldn't get my Nokia phone communicating with my computer after disabling the bluetooth service and re-enabling after some time , so I uninstalled all the bluetooth stuffs... maybe it has something to do with that.

bijuabrahamp
July 25th, 2005, 04:17 AM
Just did a sfc /scannow But everything is perfect... they why is my XP behaving ODD?!

Arjay
July 25th, 2005, 05:33 PM
Reinstall the OS. In the future, if you have issues after some driver or hardware install, you can revert back to the previous configuration by pressing F8 on startup. This will allow you to revert back to a known good configuration.

Arjay

PeejAvery
July 25th, 2005, 11:18 PM
Just did a sfc /scannow But everything is perfect... they why is my XP behaving ODD?!

A problem has been detected and Windows has been shut down to prevent damage to your computer

IRQL_NOT_LESS_OR_EQUAL

Interrupt Request is not a nice error to have. That means you have hardware attempting to access the same interrupts causing system faults. Check your Device Manager. Some hardware should show conflicts.

bijuabrahamp
July 26th, 2005, 04:40 AM
Interrupt Request is not a nice error to have. That means you have hardware attempting to access the same interrupts causing system faults. Check your Device Manager. Some hardware should show conflicts.
No, my device manager shows that all devices are working properly... I'll write the complete configuration of my computer
Pentium 4 3.2 Ghz (LGA 775)
Intel D915GAV motherboard (with 64 MB Graphics card)
1 GB DDR-RAM (512MB X 2)
120 GB Hard Disk
Lite-ON Combo Drive (DVD + CD-RW)
Floppy drive
Creative 56K Fax Modem
Benq DC1300 Digital Camera connected to USB
MSI Bluetooth stick (used to be connected to USB) <-- used to be a problem maker until i unistalled him
Keyboard ;)
Mouse
Acer 15" LCD Monitor(AL512)

any problems with those??

bijuabrahamp
July 26th, 2005, 03:49 PM
Anyway, thanx guys for helping... I formatted my drive and installed again, now everything works superb! It was that old SP2 itself, but this time it works fine... I feel everything is more faster than bfore (maybe becoz i got rid of all the junk i had in my pc ;)) anyway, no more bluetooth installation.. so my pc will work fine

thanx again

PeejAvery
July 26th, 2005, 07:40 PM
You misunderstand.

IRQ is called Interrupt Request. It is a register that each hardware device must call in order to function. It would not show up just under Device Manager. You must check the properties of each device and go under Resources. That will give you the IRQ.

bijuabrahamp
July 27th, 2005, 01:06 AM
IRQ is called Interrupt Request. It is a register that each hardware device must call in order to function. It would not show up just under Device Manager. You must check the properties of each device and go under Resources. That will give you the IRQ.
Oops.. I thought it may come as an exclamation mark on some device in the Device Manager.. Anyway, now there is no problem

PeejAvery
July 27th, 2005, 12:45 PM
Yes, usually they are represented by exclamation points but believe it or not, Windows does strange things, no matter what version. I believe all would agree with me. I have seen many cases where IRQ's show no exclamation.

Glad to know all is working.

bijuabrahamp
July 27th, 2005, 02:56 PM
Yes, usually they are represented by exclamation points but believe it or not, Windows does strange things, no matter what version. I believe all would agree with me. I have seen many cases where IRQ's show no exclamation. I strongly suspect whether it had anything to do with bluetooth becoz XP doesnot support it much.

Glad to know all is working. Me too :wave:
Thanx

PeejAvery
July 27th, 2005, 10:06 PM
Anyway, thanx guys for helping... I formatted my drive and installed again, now everything works superb! It was that old SP2 itself, but this time it works fine... I feel everything is more faster than bfore (maybe becoz i got rid of all the junk i had in my pc ;)) anyway, no more bluetooth installation.. so my pc will work fine

I strongly suspect whether it had anything to do with bluetooth becoz XP doesnot support it much.

Actually that COULD HAVE BEEN your problem at that. XP does not have problems with bluetooth too terribly. Then Microsoft put out SP2. When patching over SP1 with SP2 all bluetooth devices fault due to a new form of device management with bluetooth. Of course, I don't know if you patched from SP1 or not. Either way, SP2 does glitch with bluetooth.

bijuabrahamp
July 28th, 2005, 01:10 AM
Actually that COULD HAVE BEEN your problem at that. XP does not have problems with bluetooth too terribly. Then Microsoft put out SP2. When patching over SP1 with SP2 all bluetooth devices fault due to a new form of device management with bluetooth. Of course, I don't know if you patched from SP1 or not. Either way, SP2 does glitch with bluetooth.
No, I didn't patch from SP1... I just installed Windows XP from my Windows XP SP2 CD-ROM because its a new PC. The thing is that, in my old computer, I had patched from SP1, and the bluetooth was installed at that time, and no problems were there.
But, do you have any idea, why it didn't allow me to go to Safe Mode.. in the normal mode, Windows could start up.