General discussion

Locked

NT Bootup Failure

By richard ·
Hello and thanks for any help anyone will be able to offer! I'm very new to NT and very basic in its operation. So please forgive in advance if I don't understand some things told to me in the beginning and have to ask for further explanation. The machine I'm operating is an NT4 Workstation, running the Pinnacle DC1000 Video edit system. Have 2 450 MHz processors, 256 MB RAM installed,and operating on a Lantastic network for printer and data storage.

Now to the problem. Starting one recent morning and every subsequent morning, afternoon, evening; the machine on bootup starts normally, memory count is fine... does recognizes the Primary and Secondary drives installed... recognizes the SCSI devices connected (hard drives for storage)... comes to the select OS screen and starts NT automatically... does its thinking then stops at a blue error screen. The screen starts out as follows:

2 System Processors [256 MB of Memory] Multiprocessor Kernel

***STOP 0x000000093 (0x0000077F, 0x00000001, 0x0000

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

NT Bootup Failure

by guy In reply to NT Bootup Failure

I expect you have installed Service Pack 5 or later, but it may be worth re-installing. Microsoft's Technet says the error is:
INVALID_KERNEL_HANDLE (0x93)

This message occurs if kernel code (server, redirector, other driver,
and so forth) attempts to close a handle that is not a valid handle.

1 - The handle that NtClose was called with.

2 - 0 means a protected handle was closed.
1 means an invalid handle was closed.
If re-applying the servicepack does not work, I would re-install NT especially as its NT Workstation.
The only slight clue in Rechnet is Redirectory, have you by any chance got the Client for Netware, in which I case I would remove and re install it, then repply the servicepack.

Collapse -

NT Bootup Failure

by richard In reply to NT Bootup Failure

The question was auto-closed by TechRepublic

Collapse -

NT Bootup Failure

by f-2379390 In reply to NT Bootup Failure

The stop error you are getting indicates that there is a conflict/problem between the drivers NT is loading and the actual hardware in your machine. Think back - what did you add to or change on your machine just before this problem started occurring? The blue screen and stop error rarely comes 'out of the blue', it can almost always be traced to a change in the system configuration.
You say you have dual 450 mhz cpus. Did you have the two cpus in from the start - so that nt was running successfully with dual cpus? Or did you just add the second cpu as an upgrade? If so, try removing the second cpu and then restart the computer.
If you added a video card, video capture card or other multimedia device just prior to the problem starting, try removing that as well. Generally, once the device that activated the problem is removed you will be able to revert back to where you were before.
If you are able to boot after removing one of the devices, you will want to take a careful look at whether that device re

Collapse -

NT Bootup Failure

by richard In reply to NT Bootup Failure

The question was auto-closed by TechRepublic

Collapse -

NT Bootup Failure

by McKayTech In reply to NT Bootup Failure

I agree that it sounds like a driver issue, and it is likely related to either a configuration change or corruption of a driver file.

If you have an ERD, you can try a repair install or you can try a parallel installation if there is workstation data you're trying to save.

In a parallel installation, you install to a different directory than the original installation, boot up to that directory and then you can play with the registry in the original installation directory. Once you get itfixed, you just adjust the BOOT.INI file to point back to the original directory and you're home free. On mission-critical machines, I routinely make a parallel install when I do the original setup so I always have a back door into the registry just for times like this.

paul

Paul M. Wright, Jr.
McKay Technologies

Collapse -

NT Bootup Failure

by richard In reply to NT Bootup Failure

The question was auto-closed by TechRepublic

Collapse -

NT Bootup Failure

by jun1cez1 In reply to NT Bootup Failure

To Richard,

The problem is originating from three points,
first 0x77, means that a hardware coprocessor instruction with no coprocessor present, which you can say that the OS does not or failed to recognized the second processor or should we sayhardware incompatibility especially for newly installed hardware. Either you need to reinstall the dual processor support or download a new less buggy one, or remove which one is malfunctioning but of course you need to run a hardware diagnostic test.
Also check to see if all memory module are seated properly.
The second 0x1 i believe was a system debugger call of some sort, you should check for availability for BIOS revision on the motherboard, SCSI controllers or even perhaps NIC cards and be sure that every hardware you have is in the HCL.
By the way, as far as i know, 0x77 is being caused by that the KERNEL DATA from the paging file can not be read into memory (in other words_KERNEL_STACK_INPAGE_ERROR) which is it could be you havesome bad sectors in

Collapse -

NT Bootup Failure

by richard In reply to NT Bootup Failure

The question was auto-closed by TechRepublic

Collapse -

NT Bootup Failure

by richard In reply to NT Bootup Failure

This question was auto closed due to inactivity

Back to Windows Forum
9 total posts (Page 1 of 1)  

Operating Systems Forums