Windows server 2003 ntoskrnl exe




















Cancel Submit. Vijay B. Hi Swanco, The issue you posted is related to Server and would be better suited in the TechNet community. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. This site in other languages x. Windows Server General Forum. Sign in to vote. Neshuta Any Ideas before I drive nearly 2 hours out to the client to work on this would be appreciative.

Wednesday, June 23, PM. Karen, thanx for the evening reply, however not much help here. Microsoft has failed me, again. My original post does state the message is from a client 2 hours away, and I have no other knowledge of the issue, also, it clearly states the client attempted to boot off the Windows CD and got the blue screen.

Microsoft did fail me big time on this one, however Google came through with flying colors, again; so here's the fixit answer for any sucker looking at Microsft for an answer:. I did some google research before getting in the car and driving 2 hours to uncertanty.

I brough all of my fixit CD's that I have, just in case, and a box of floppies, as they can be quite useful in situations like this. I found the original RAID floppy and popped it into the drive, hit F6 upon beginning of the setup, it attmpted to load the drivers, with no luck. I figured, hey, 2 year old floppy, its probably bad, so I'll make another.

Found the handy driver CD, put it in an XP box, found the make disk exe and found 6 possibilities. I made 6 disks, trying each one, and fail, fail, fail, fail, fail and walah, wouldn't ya know it, the 6th one, of corse, worked!!!

Excited the server no longer had a BSOD, and got to the welcome screen, I hit R for recovery console, and went right in, then began problem 2, the password. Turns out, the Adminstrator password for RC is different from the Active Directory password users use everyday to login. Active 2 years ago.

Viewed 3k times. All drivers installed OK. All unused devices are disabled in the bios. No conflict in drivers Tried opening via remote desktop and the problem continues.

UnexpectedInterrupt", all threads stacks end in "UnexpectedInterrupt" ntoskrnl. KiFastSystemCallRet kernel Improve this question. Glorfindel 1, 3 3 gold badges 14 14 silver badges 22 22 bronze badges.

Burnsys Burnsys 1 1 silver badge 5 5 bronze badges. Add a comment. Andrew Hancock - VMware vExpert. See if this solution works for you by signing up for a 7 day free trial.

What do I get with a subscription? With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros.

We can't always guarantee that the perfect solution to your specific problem will be waiting for you. If you ask your own question - our Certified Experts will team up with you to help you get the answers you need.



0コメント

  • 1000 / 1000