Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

System has stopped

Original Message
Name: harald
Date: June 10, 2003 at 05:33:36 Pacific
Subject: System has stopped
OS: OS/2 Warp 4
CPU/Ram: ?
Comment:
Hello everybody,

I've got an OS/2 machine that intends to crash with the next error msg:
The System detected an Internal Processing error at Location # # 0168:f f f 262 ea - 000e:c2ea.
60000, 9084
07860683
Internal revision 14.046A_W4
The System is stopped. Record all of the above information and contact your service representative.

I have no idea what this means and couldn't find anything about this error. Maybe someone can help me out.
Thanx in advance.

Harald


Report Offensive Message For Removal


Response Number 1
Name: JoseRR
Date: July 18, 2003 at 09:31:43 Pacific
Subject: System has stopped
Reply: (edit)
This kind of crashes are usually related to an activity that OS/2 was performing IMMEDIATELY before the crash.

If the system was performing fine priorly, then do some detective work. Perhaps you added a new setting or a new device driver, you installed a program that modified your Config.sys, etc., etc..

If you always had analogous problems, then make sure that upon a fresh OS/2 installation you update your system with the latest system fixpacks and the corresponding device driver updates BEFORE you configure the video subsystem out of the VGA default.

Additionally, backup your system any time you add support for some option and reaply the fixpacks because your system may have been down leveled.

If you want to suppress the interruption caused by the crash and instead log the crash message to the boot partition, the documentation for the latest fixpacks suggest that you add the following line to your Config.sys:

SUPPRESSPOPUPS=X:

where X is the drive letter of your boot partition. This option merely allows you more flexibility to discover the problem--it does not solve it!

Wish you well.


Report Offensive Follow Up For Removal




Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: System has stopped

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




how to setup call of duty to joytok

WindowsME / HotMail Problem

Corrupt memory

Convert fat32 to Ntfs

Best WinMo phone of 2008


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC