First stop error

Well I knew it'd happen sooner or later, I got a stop error about half an hour ago. It mentioned something about a memory dump. I had to hit the reset button because Ctrl+Alt+Del did nothing. I looked in Event Viewer after I rebooted. This is what it said:

How can I find out what caused this and fix it?

 

"0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). "

Maybe not much help, but look
here.

 

Earlier today EZAntivirus stopped a JavaScript virus from loading on my machine. I ran a virus scan and it found the 2 files in my JavaScript cache folder and deleted them. Could this have caused the problem? Could a bad virus sig update cause it?

 

What I found in StartUp Cop

http://home.comcast.net/~stealthbomber77/screencap2.jpg

StartUp Cop shows a bunch of strange programs as being in my computer's memory and running at startup. Anyone seen these before? I disabled them from startup, but I need to be sure.

These programs
IMJPMIG8.1
IMEKRMIG6.1
MSPY2002
PHIME2002ASync
PHIME2002

 

MSPY2002 & PHIME2002ASync are both legit but used by Microsoft for working with Japanese or Chineese languages in MS Office. Some of the others may be the same.

The total group just showing up sounds like one of the browser hijack apps unless you got them all when you loaded Office and just hadn't noticed before.

I think I'd try disabling the whole bunch from starting and see if they change back on their own. If so, you got bit.

If you continue to have problems, run a scan with hijack this and post the results to the security section.

 

Yeah those are my Asian language support files. I installed them through the Region thing in Control Panel. I didn't realize this until I went and actually looked at them.

I also ran a scan with HijackThis and found nothing out of the ordinary. I guess it's just one of those random errors Windows likes to pull to make our hair turn gray.

Tomorrow I'm defragging and running ScanDisk.

 

Tomorrow I'm defragging and running ScanDisk

You can certainly defrag but no way can you run ScanDisk 'cause it ain't there.

start~run~cmd then chkdsk /r

 

LOL I found that out looking through the System Tools folder. I'm like, "Where the hell is ScanDisk?" I right clicked the hard drive icon in My Computer and found a thing about checking for errors that had the same icon that ScanDisk had. I enabled both options to automatically fix errors and the 2nd one which I forget at the moment. Windows comes back with a message saying it can't do it because it needs access to some files that can only be gotten by rebooting.

I reboot and get the same error message. How can I run the checkdisk and autofix errors w/o encountering that error message?

 

CheckDisk

Did a little research and determined that CheckDisk can't fix anything while other programs are running at the same time.

edit: Now I see why it wouldn't work. CheckDisk has to be run before Windows starts! That's way different from 9x ScanDisk!

 

Sort of. Chkdsk cannot run with repair set on a drive that has any part of the operating system running. So, the drive that contains Windows for sure will have to wait for the next reboot. If you have any of your pagefile on a drive, it is the same.

Chances are good that a pure data drive will run chkdsk while the system is up though.

Chkdsk /f is the equiv. of a scandisk in normal mode and set to fix errors. Chkdsk /r is like scandisk when set to do a surface check so it takes longer. And on an NTFS system, it also checks and fixes things that chkdsk /f does not.

The GUI location you found with the various options you can tick or untick is simply a way to cause chkdsk to run. I normally start it from a command prompt but that's habit I think since the GUI stuff works fine.

 

IMJPMIG8.1 and IMEKRMIG6.1 are both legit Input Method Editors related to your language pack installations.

Getting back to your original problem, has the error occurred again? What did the Event Viewer tell you?

I doubt any javascript-related thing would cause this stop error. But a virus may have, depending which one and how far it got.

If the error has not occurred again, there really is such a thing as a "fluke ", even with computers (electrons are subject to the Uncertainty Principle), so you can just forget it unless it happens at least twice .