Computing.Net > Forums > Windows NT > 0x00000007b, ntoskrnl.exe,

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

0x00000007b, ntoskrnl.exe,

Reply to Message Icon

Name: plangford
Date: June 25, 2007 at 10:15:04 Pacific
OS: Windows NT Server
CPU/Ram: 512
Product: Compaq P1600
Comment:

When I try to boot up my win nt server I get the BSOD with 0x0000007b stop code, then File:NTOSKRNL.exe and then on the line below it says inaccessible boot device. What I dont understand is that this server has 2 identical operating systems!

I can boot into one of them fine but when I choose this second copy, I get the BSOD.

Any replies would be greatly appreciated.

PL



Sponsored Link
Ads by Google

Response Number 1
Name: wanderer
Date: June 26, 2007 at 11:27:30 Pacific
Reply:

post the boot.ini

Imagine the power if you knew how to internet search


0

Response Number 2
Name: plangford
Date: June 28, 2007 at 08:17:17 Pacific
Reply:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Server Version 4.00"
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Server Version 4.00 [VGA mode]" /basevideo /sos
multi(0)disk(0)rdisk(0)partition(2)\SECONDNT="Windows NT Server Version 4.00"
multi(0)disk(0)rdisk(0)partition(2)\SECONDNT="Windows NT Server Version 4.00 [VGA mode]" /basevideo /sos


0

Response Number 3
Name: plangford
Date: June 28, 2007 at 09:51:39 Pacific
Reply:

I should add that, there was something wrong with the old server, so we replaced the that server with anew one but that had the same parts as the old one. I only kept the HDD's, like i say, the 1st copy of NT boots up OK but not the second.


0

Response Number 4
Name: wanderer
Date: June 28, 2007 at 15:50:41 Pacific
Reply:

I suspect someone didn't know how to edit the boot.ini.

You don't need the "SECONDNT" entries if the first boot fine so delete them.

I suspect a couple of things happened.

1. someone thought SECONDNT was a description in the boot.ini. Its not. It refers to the actual winnt OS folder.
2. someone renamed the winnt folder to SECONDNT and expected that to work. They forgot about thousands of entries in the registry that still pointed to winnt.
3. the SECONDNT folder does not exist

They both point to the same partition and disk.


Imagine the power if you knew how to internet search


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More


CDROM problem Win NT not detecting Com ...


Use following form to reply to current message:

Login or Register to Reply
LoginRegister


Sponsored links

Ads by Google


Results for: 0x00000007b, ntoskrnl.exe,

missing or corrupt: ntoskrnl.exe www.computing.net/answers/windows-nt/missing-or-corrupt-ntoskrnlexe/6747.html

NTOSKRNL.EXE www.computing.net/answers/windows-nt/ntoskrnlexe/5372.html

When .mp3 files played off a cd: STOP screen, CD-FS file system error at ntoskrnl.exe and dumping of physical memory www.computing.net/answers/windows-nt/when-mp3-files-played-off-a-cd-stop-screen-cdfs-file-system-error-at-ntoskrnlexe-and-dumping-of-physical-memory/2160.html