Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Bsod 0x1e On Every W2k Boot


  • Please log in to reply
17 replies to this topic

#1 Legacy712

Legacy712

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:01:48 PM

Posted 10 April 2007 - 01:31 AM

A few days ago, I rebooted my W2K (SP4) box (Intel 3.2 P4), and it issued a blue screen. This happens on every boot, at the logon screen, whether I logon or not. If I just let it sit on the logon screen without touching anything, after around 15 seconds it will go bsod. If I logon, same results (while it's doing the desktop) and same time interval. This indicates to me that there's probably a problem with something specific it's initializing/loading, either an appl or device driver. At least it will come up in safe mode, so I can fiddle with it.

The BSOD text is similar to the following: (?=not sure)
0x0000001E (0xC0000005,0x??????,0x0000,0x0047)
KMODE_EXCEPTION_NOT_HANDLED
?????? loaded? 0400000 exception? 041DDE3 - NTOSKRNL.EXE

If parm 2 or anything else is important, I can get it.

Normally, I only reboot this cpu every 3 weeks or so, unless I have to because of installing some s/w or applying patches. It's been running w2k for many (6?) years, through various m/b and other h/w upgrades. Last h/w upgrade was around 6 months ago, upgrading to a 300 GB disk. W2K is in the 3rd (NTFS) partition, a throwback to running WFW 3.11 and OS/2 in other partitions, but it always runs fine.

I tried unsuccessfully to repair it using the CD, but it won't recognize any w2k partition because it seems to "see" the drive as only 128 GB, which doesn't even get to the start of the 3rd partition. I don't think a repair would have done any good anyway.

I've run 3 antivirus programs and 2 antispyware programs, each in their most complete modes, but nothing significant was found. I run ZoneAlarm for AV, antispyware, and firewall at all times (cable modem), so I didn't expect to find much. I ran WinASO with a deep registry scan and all other options, and deleted anything which looked wrong. I've run memory (2 GB) tests and they look okay. The disk is running fine with lots of space in all partitions. I've disabled any services which didn't seem necessary. I've "downgraded" some bios options to be extra-safe. I never overclock anything. In safe mode, it won't let me uninstall anything, so I've renamed folders pertaining to the latest s/w I installed the day before, which was Dataviz's Documents To Go upgrade for the Palm Pilot.

Everything was fine until I rebooted, and I don't remember why I did. Unfortunately, some s/w appls check for updates every day or so, and update themselves automatically in the background, so I don't really know exactly what's changed in the last few weeks.

Using the last known good configuration is not an option, since too many things have changed since then.

I've read just about everything on the net about the 0x1E bsod for the last 3 days, and it all seems to point to a device driver, of which I have lots and lots. I've been an Assembler s/w developer in the mainframe world for 38 years, but know very little about PC instructions or dump layouts. Is there any way I can determine what's going wrong a little more definitively, with a dump or something?

Thank you.

Doug

Edited by Legacy712, 10 April 2007 - 01:56 AM.


BC AdBot (Login to Remove)

 


#2 acklan

acklan

    Bleepin' cat's meow


  • Members
  • 8,529 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Baton Rouge, La.
  • Local time:01:48 PM

Posted 10 April 2007 - 02:17 AM

Boot back into Safe Mode and go into the Event Viewer, located in the Administrative Tools. Let's start with the most recent errors(Last couple of days).

Edited by acklan, 10 April 2007 - 02:18 AM.

"2007 & 2008 Windows Shell/User Award"

#3 oldf@rt

oldf@rt

  • Members
  • 2,609 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Avondale, Arizona USA
  • Local time:12:48 PM

Posted 10 April 2007 - 02:26 AM

Are you running partitioning software provided by the manufacturer of the disk?

The W2K disk will not recognize the full HDD if this is the case, as it only sees what the BIOS sees.

If you are, use the key sequence and then insert the W2K cd to boot and run recovery.

You should see this specified just before w2k starts to load for a couple of seconds.
The name says it all -- 59 and holding permanently

**WARNING** Links I provide might cause brain damage

#4 Legacy712

Legacy712
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:01:48 PM

Posted 10 April 2007 - 05:09 PM

Thank you for your responses. I wish I'd checked for responses to my query this morning, as I was up until 5:30 with this, but I didn't think anyone would have responded already.

I started w2k in normal mode and waited for the bsod. Then I started it in safe mode. These are the application events, but these events are from starting it in -safe- mode; there were none from normal mode. Following that are the system events from the BSOD startup. I omitted the last columns for clarity.

Type Date Time Source Category Event
Error 04/10/2007 2:50:51 PM W3Ctrs None 1003
Unable to query the W3SVC (HTTP) service performance data. The error code returned by the service is data DWORD 0.

Error 04/10/2007 2:50:51 PM rasctrs None 2001
The description for Event ID ( 2001 ) in Source ( rasctrs ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: The event log file is corrupt..

Error 04/10/2007 2:50:51 PM PerfDisk None 1000
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Error 04/10/2007 2:50:50 PM FtpCtrs None 1000
Unable to collect the FTP performance statistics. The error code returned by the service is data DWORD 0.

Warning 04/10/2007 2:50:50 PM WinMgmt None 41
WMI ADAP was unable to create object index 4880 for Performance Library MSDTC because no value was found in the 009 subkey

--------

System events with BSOD

Type Date Time Source Category Event
Error 04/10/2007 4:14:48 PM Service Control Mgr None 7000
The BDA Slip De-Framer service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Error 04/10/2007 4:14:35 PM Service Control Mgr None 7000
The Microsoft Streaming Tee/Sink-to-Sink Converter service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Error 04/10/2007 4:14:35 PM Service Control Mgr None 7000
The NABTS/FEC VBI Codec service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Error 04/10/2007 4:14:34 PM Service Control Mgr None 7000
The IPSEC driver service failed to start due to the following error:
Insufficient system resources exist to complete the requested service.

Error 04/10/2007 4:14:34 PM Service Control Mgr None 7000
The Parallel Port CF Driver service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Error 04/10/2007 4:14:34 PM Service Control Mgr None 7000
The Closed Caption Decoder service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Error 04/10/2007 4:14:34 PM Service Control Mgr None 7000
The BDA MPE Filter service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Error 04/10/2007 4:14:34 PM IPSEC None 4281
Unable to allocate required resources. Initialization failed.

Info 04/10/2007 4:14:00 PM eventlog None 6005
Info 04/10/2007 4:14:00 PM eventlog None 6009
Error 04/10/2007 4:13:44 PM msi8042 None 4
The hardware resources for are already in use by another device.

Info 04/10/2007 4:13:34 PM b57w2k None 9
Info 04/10/2007 4:13:32 PM b57w2k None 15
Broadcom NetXtreme Gigabit Ethernet message

The msi8042 message has me concerned: it doesn't say whose resources, and MSI is my m/b. Maybe something on my m/b (sound?) suddenly died?

The IPSEC message has me concerned, as I don't know which resources it cannot allocate.

--------

Not to be overly verbose, I have included the normal (bsod) mode's boot log, in case it helps anything.

Service Pack 4 4 10 2007 15:24:12.500 normal mode
Loaded driver \WINNT\System32\ntoskrnl.exe
Loaded driver \WINNT\System32\hal.dll
Loaded driver \WINNT\System32\BOOTVID.dll
Loaded driver imagesrv.sys
Loaded driver ACPI.sys
Loaded driver \WINNT\System32\DRIVERS\WMILIB.SYS
Loaded driver isapnp.sys
Loaded driver pci.sys
Loaded driver compbatt.sys
Loaded driver \WINNT\System32\DRIVERS\BATTC.SYS
Loaded driver pciide.sys
Loaded driver \WINNT\System32\DRIVERS\PCIIDEX.SYS
Loaded driver ftdisk.sys
Loaded driver Diskperf.sys
Loaded driver dmload.sys
Loaded driver dmio.sys
Loaded driver MountMgr.sys
Loaded driver PartMgr.sys
Loaded driver atapi.sys
Loaded driver aic78xx.sys
Loaded driver \WINNT\System32\DRIVERS\SCSIPORT.SYS
Loaded driver imagedrv.sys
Loaded driver disk.sys
Loaded driver \WINNT\System32\DRIVERS\CLASSPNP.SYS
Loaded driver fltmgr.sys
Loaded driver PxHelp20.sys
Loaded driver TPkd.sys
Loaded driver KSecDD.sys
Loaded driver Ntfs.sys
Loaded driver NDIS.sys
Loaded driver viaagp1.sys
Loaded driver srescan.sys
Loaded driver ohci1394.sys
Loaded driver \WINNT\System32\DRIVERS\1394BUS.SYS
Loaded driver Mup.sys
Loaded driver agp440.sys
Loaded driver \SystemRoot\system32\DRIVERS\nv4_mini.sys
Loaded driver \SystemRoot\system32\DRIVERS\HDAudBus.sys
Loaded driver \SystemRoot\system32\DRIVERS\b57w2k.sys
Loaded driver \SystemRoot\System32\DRIVERS\uhcd.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbehci.sys
Loaded driver \SystemRoot\System32\DRIVERS\i8042prt.sys
Loaded driver \SystemRoot\System32\Drivers\L8042Kbd.sys
Loaded driver \SystemRoot\System32\DRIVERS\kbdclass.sys
Loaded driver \SystemRoot\System32\Drivers\L8042mou.sys
Loaded driver \SystemRoot\System32\Drivers\LMouKE.sys
Loaded driver \SystemRoot\System32\DRIVERS\mouclass.sys
Loaded driver \SystemRoot\System32\DRIVERS\fdc.sys
Loaded driver \SystemRoot\System32\DRIVERS\parport.sys
Loaded driver \SystemRoot\System32\Drivers\AFS2K.SYS
Loaded driver \SystemRoot\System32\Drivers\Cdr4_2K.SYS
Loaded driver \SystemRoot\System32\DRIVERS\cdrom.sys
Loaded driver \SystemRoot\System32\Drivers\cdralw2k.SYS
Loaded driver \SystemRoot\System32\DRIVERS\audstub.sys
Loaded driver \SystemRoot\System32\DRIVERS\rasl2tp.sys
Loaded driver \SystemRoot\System32\DRIVERS\ndistapi.sys
Loaded driver \SystemRoot\System32\DRIVERS\ndiswan.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspptp.sys
Loaded driver \SystemRoot\System32\DRIVERS\ptilink.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspti.sys
Loaded driver \SystemRoot\System32\DRIVERS\parallel.sys
Loaded driver \SystemRoot\System32\DRIVERS\swenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\update.sys
Did not load driver \SystemRoot\system32\DRIVERS\d347bus.sys
Loaded driver \SystemRoot\system32\drivers\cmudax.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbhub.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbhub20.sys
Loaded driver \SystemRoot\System32\DRIVERS\flpydisk.sys
Loaded driver \SystemRoot\System32\Drivers\NDProxy.SYS
Loaded driver \SystemRoot\System32\Drivers\EFS.SYS
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Loaded driver \SystemRoot\System32\DRIVERS\USBSTOR.SYS
Loaded driver \SystemRoot\System32\DRIVERS\usbscan.sys
Loaded driver \SystemRoot\system32\drivers\vicamusb.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbprint.sys
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Loaded driver \SystemRoot\System32\Drivers\Fs_Rec.SYS
Loaded driver \SystemRoot\System32\Drivers\Null.SYS
Loaded driver \SystemRoot\System32\Drivers\Fastfat.SYS
Loaded driver \SystemRoot\System32\Drivers\Beep.SYS
Did not load driver \SystemRoot\System32\Drivers\tga.SYS
Loaded driver \SystemRoot\System32\drivers\vga.sys
Loaded driver \SystemRoot\System32\Drivers\mnmdd.SYS
Loaded driver \SystemRoot\System32\Drivers\Msfs.SYS
Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS
Loaded driver \SystemRoot\System32\Drivers\UdfReadr.SYS
Loaded driver \SystemRoot\System32\DRIVERS\rasacd.sys
Loaded driver \SystemRoot\System32\DRIVERS\msgpc.sys
Loaded driver \SystemRoot\System32\DRIVERS\tcpip.sys
Loaded driver \SystemRoot\System32\DRIVERS\wanarp.sys
Loaded driver \SystemRoot\System32\DRIVERS\netbt.sys
Loaded driver \SystemRoot\System32\vsdatant.sys
Loaded driver \SystemRoot\System32\DRIVERS\netbios.sys
Did not load driver \SystemRoot\System32\DRIVERS\serial.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Did not load driver \SystemRoot\System32\DRIVERS\redbook.sys
Loaded driver \SystemRoot\System32\DRIVERS\rdbss.sys
Loaded driver \SystemRoot\System32\Drivers\PQNTDrv.SYS
Loaded driver \SystemRoot\System32\DRIVERS\mrxsmb.sys
Loaded driver \??\F:\WINNT\system32\drivers\ikhlayer.sys
Loaded driver \??\F:\WINNT\system32\drivers\ikhfile.sys
Loaded driver \SystemRoot\System32\DRIVERS\enc2filt.sys
Loaded driver \SystemRoot\System32\DRIVERS\enc2port.sys
Did not load driver \SystemRoot\system32\DRIVERS\d347bus.sys
Loaded driver \SystemRoot\System32\drivers\afd.sys
Loaded driver \??\F:\WINNT\system32\ZoneLabs\avsys\KLIF.SYS
Did not load driver \SystemRoot\system32\DRIVERS\d347bus.sys
Loaded driver \SystemRoot\system32\DRIVERS\imagesrv.sys
Loaded driver \SystemRoot\system32\drivers\wdmaud.sys
Loaded driver \SystemRoot\system32\drivers\sysaudio.sys
Loaded driver \SystemRoot\system32\drivers\swmidi.sys
Loaded driver \SystemRoot\system32\drivers\DMusic.sys
Loaded driver \SystemRoot\system32\drivers\kmixer.sys
Loaded driver \SystemRoot\System32\Drivers\BrPar.sys
Did not load driver \SystemRoot\System32\DRIVERS\CCDECODE.sys
Did not load driver \SystemRoot\system32\DRIVERS\d347bus.sys
Did not load driver \SystemRoot\System32\DRIVERS\ctljystk.sys
Did not load driver \SystemRoot\system32\DRIVERS\d347bus.sys
Did not load driver \SystemRoot\System32\DRIVERS\epcfw2k.sys
Did not load driver \SystemRoot\system32\DRIVERS\d347bus.sys
Did not load driver \SystemRoot\System32\DRIVERS\gameenum.sys
Did not load driver \SystemRoot\system32\DRIVERS\d347bus.sys
Did not load driver \SystemRoot\System32\DRIVERS\hidusb.sys
Did not load driver \SystemRoot\system32\DRIVERS\d347bus.sys
Did not load driver \SystemRoot\System32\Drivers\Modem.SYS
Did not load driver \SystemRoot\System32\DRIVERS\MPE.sys
Did not load driver \SystemRoot\system32\drivers\MSTEE.sys
Did not load driver \SystemRoot\System32\DRIVERS\NABTSFEC.sys
Loaded driver \SystemRoot\System32\Drivers\ParVdm.SYS
Did not load driver \SystemRoot\System32\DRIVERS\serial.sys
Did not load driver \SystemRoot\System32\DRIVERS\SLIP.sys

I don't know why this would have happened all of a sudden, unless some s/w altered or installed something without my knowledge, since all of my h/w seems to be working alright, at least whatever will work in safe mode.

I do not use any special disk s/w, partitioning or otherwise. My bios sees this drive as 320 GB, m/b is only around 1.5 years old. I've checked and rechecked all of my bios settings, and they appear fine.

I -did- notice one strange thing, though. Somewhere in my wanderings through the o/s the other day, I noticed some devices using irq's over 15, like 23 and such, but less than 32. I don't recall seeing this before, and I didn't think they were defined beyond 15...?

Some additional info: This PC is part of a 4 PC network. In safe mode, I can access the other 3 PCs just fine, fwiw.

Again, thank you for your responses, as I'm going nuts here. I get the feeling that it's a very small problem causing this to happen --- just a matter of finding the proverbial needle in the haystack, but I don't know.

Doug

Edited by Legacy712, 10 April 2007 - 05:11 PM.


#5 oldf@rt

oldf@rt

  • Members
  • 2,609 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Avondale, Arizona USA
  • Local time:12:48 PM

Posted 10 April 2007 - 06:11 PM

Dont worry about the IRQs assigned by W2K. W2K can use virtual IRQs.

Try disabling the serial and parallel ports in the bios. restart in 386E mode (regular mode) and see if you still get the bsod.

Some of the errors you are getting in safe mode are caused by drivers that are unable to load in safe mode.
The name says it all -- 59 and holding permanently

**WARNING** Links I provide might cause brain damage

#6 Legacy712

Legacy712
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:01:48 PM

Posted 11 April 2007 - 01:10 PM

I tried disabling the serial and parallel ports. It didn't help, and actually came up with more errors because of my fax machine.

I found a post from 2002 regarding a Brother MFC fax s/w problem which caused IPSEC to have problems loading, and I have a Brother MFC 4600 (with s/w) attached to my system. I went to the Brother site and they no longer have the MFC 4600, so I tried the 4800. I searched for the faq # and got nothing. Since I'm in safe mode, I cannot do an uninstall, so I'm screwed on that one.

There is no other mode I can put the machine into. The m/b is around 2 years old.

The msi8042 problem I had deals with the mouse. I've checked, and the keyboard is using 2 memory locations which are in conflict with the m/b, apparently, with red lines running through them. Don't know how long it's been like that, as it works in safe mode.

Although I ran extensive memory tests for well over an hour with clean results, I decided to slow my memory from 533 to 400, just to check. Alas, same problem.

I've also tried unplugging all my usb devices with no luck.

It's going on 5 days, and I'm going nuts. My PC has never been down that long in 20 years. If this was a mainframe, I would have had it up within hours. Thank God I can boot in safe mode and access the net. I'm hoping one of you guys will figure out something.

Thanks for the reply. Please keep at it. I got tied-up yesterday and couldn't get back to here until today, but I'll try to respond more quickly.

Doug

Edited by Legacy712, 11 April 2007 - 01:18 PM.


#7 acklan

acklan

    Bleepin' cat's meow


  • Members
  • 8,529 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Baton Rouge, La.
  • Local time:01:48 PM

Posted 11 April 2007 - 01:47 PM

Old school tying to detect a memory problem would be to remove one stick at a time and see if it clears up. The trouble with that these days is most computers cram all of the memory onto one module. If you have two try one at a time and see if it is an error that Mem86 cannot detect, although I find that doubtful.
"2007 & 2008 Windows Shell/User Award"

#8 Legacy712

Legacy712
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:01:48 PM

Posted 11 April 2007 - 07:26 PM

Just did the memory thing. I have (2) 1GB DDR2 sticks, so I tried one, then the other. Same results.

I did manage to eliminate my IPSEC failing to load error. I found the patch on the Brother website and applied it to the registry. At least that's okay now.

Still puzzled about the keyboard driver addresses conflict.

Doug

#9 Legacy712

Legacy712
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:01:48 PM

Posted 12 April 2007 - 04:13 PM

Any ideas from anybody? I'm just looking for things to try...

#10 oldf@rt

oldf@rt

  • Members
  • 2,609 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Avondale, Arizona USA
  • Local time:12:48 PM

Posted 12 April 2007 - 10:03 PM

Twon things i can thhink of:

Try resetting the bios pull clock battery for 30 min, reset to optimal, redo date time, pull all expansion cards except video, re install between restarts,.

try removing sp 4 and re installing after you have uninstalled 3rd party keyboard and mouse drivers.

still looking through KB at m$
The name says it all -- 59 and holding permanently

**WARNING** Links I provide might cause brain damage

#11 Legacy712

Legacy712
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:01:48 PM

Posted 15 April 2007 - 03:05 AM

Thanks for the ideas.

I couldn't remove sp4, since I was in safe mode and it wouldn't let me remove anything.

I removed the only card in the system other than the video, which is my scsi card for my tape backup. Lo and behold, it came up! I was so surprised the scsi card could have had such an impact, since it's only used when I use the tape drive, and I can view and set its cmos settings just fine.

I immediately created an ERD with registry backup. Then I rebooted, to see if it was a fluke. It came up again, so I began reinstating the processes I had set to manual or disabled, and set my startup appls the way they were. I should have done it a few at a time, because I ended up with the 0x1E again. Apparently, the scsi card wasn't at fault.

This time, I decided to do the "last known good configuration" thing, since it worked the last time I logged on. Big mistake. Then, on booting, it immediately said the F:\winnt\system32\config\SYSTEM file was missing or corrupted. Now I was screwed, since I couldn't even boot in safe mode, and the install disk couldn't access the winnt partition, since it's too far into the 320 GB disk.

Since I couldn't boot into safe mode, I've been "gone" the last 2 days.

I tried booting my D: drive, since I keep a small W2K system there for recovery, but it came up with a 0x7E. I tried fixing and reloading it, but the install cd didn't like the D: partition, either.

I then used Partition Magic from a bootable cd. I shrunk my D:, E: and F: partitions to leave just 10% unused. Then I moved my E: and F: partitions down against D: and shrank the logical area to just contain the partitions. This brought everything as close as possible to the front of the disk.

I next tried repairing the F: partition, which the install cd found this time, but that didn't solve the problem. However, I was able to fix my D: win2k and use it to restore the system files in the F:\winnt\system32\config from the F:\winnt\repair folder (after renaming the "bad" ones - system and system.alt), but got the same message when I tried booting F:. I then booted into the recovery console (which I keep installed as a boot option) and did a chkdsk F: /r. Same results. I tried repairing F: again with no the same results.

I've looked at the F: system hive with regedt32 and it looks alright, from what I can tell. It certainly isn't missing.

So now I'm trying to solve this problem of a missing or corrupt F:\winnt\system32\config\system file. But, at least I can access the net and modify my F system, using my D: system. It's a lot better than nothing, for a while.

Doug

#12 oldf@rt

oldf@rt

  • Members
  • 2,609 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Avondale, Arizona USA
  • Local time:12:48 PM

Posted 15 April 2007 - 12:03 PM

Foung something: according to M$, your 2000 boot must be located in the first 1024 cylinders of your boot drive.

Hope this helps.
The name says it all -- 59 and holding permanently

**WARNING** Links I provide might cause brain damage

#13 Legacy712

Legacy712
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:01:48 PM

Posted 16 April 2007 - 04:39 PM

Yeah, I recall something like that. That's why I moved everything down towards the beginning of the drive, and is probably why the win2k cd wouldn't recognize the F: partition to repair.

Yet, it's been working fine for many years until now. Right now, my D: partition starts at cylinder 260 and ends at cylinder 4083. My F: partition starts at cylinder 4211, and that's after I moved it down 100 GB.

Now I'm getting the scourge of booting on my F: system: Missing or corrupt <winnt>\system32\ntoskrnl.exe. I've copied ntoskrnl.exe from my working D: system to no avail. My boot.ini file is just fine. Even copied my hal.dll. Done extensive chkdsk'ing. My D: system sees all of F: alright. Checked attributes and permissions on the winnt and winnt\system32 folders.

This is getting absolutely crazy now. I've had many bsod's in the past, usually involving h/w, and have always just solved them and went on my way. I've never seen them deteriorate into so many other problems before, for little or no apparent reason.

I appreciate the support you've given me so far, and the ideas. I normally do better with other people's systems, but I'm too emotionally involved with my own to consider everything.

Doug

#14 oldf@rt

oldf@rt

  • Members
  • 2,609 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Avondale, Arizona USA
  • Local time:12:48 PM

Posted 18 April 2007 - 09:25 PM

Found this on M$:

http://support.microsoft.com/kb/155118
The name says it all -- 59 and holding permanently

**WARNING** Links I provide might cause brain damage

#15 Legacy712

Legacy712
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:01:48 PM

Posted 28 April 2007 - 03:49 AM

Well, I'm finally back, for now. Thanks for the suggestions. I check out every one in great length.

I had my D: system working, then it went down. I even got my F: (main) system working for awhile. I was about to back it up, but made the big mistake of trying to defrag it. The defrag went awry and wiped out all 4 partitions of my hard drive. Bummer. My mistake, which set me back over 5 days.

I now have my D: system running again, but the install repair still won't recognize my F: system. On boot to F:, I'm now getting a "F:\winnt\system32\config\SYSTEM file is missing or corrupted" message. I'm working on that now.

Meanwhile, because of some of the squirelly problems I've been having, I bought another 320 GB drive and have been using that to keep a copy of my 4 partitions, which has succeeded on several instances in pulling my bacon out of the fire, so to speak.

I've also bought a 500 GB external usb backup drive, for when I finally get everything back to normal.

I've also replaced my mobo. I had an MSI and replaced it with an ASUS ($100), because of some of the weird things which were happening. The mobo died after around 8 hours and couldn't make it through the post, so I brought it back for another one which works fine.

Along the way, my recovery console experienced some problems, which I fixed. Really don't know why all these various things are happening, but I just keep solving them one by one. There have been at -least- 20 problems which I haven't mentioned, but I've gotten through them all.

This is getting very old, and today marks the start of the 4th week I've been down. This has never happened like this before. I cannot send emails, and then my phone service went down, up, down, up, ... for 3 days. Someone up there is definitely pissed at me, I'm sure. If He's listening, I'm very sorry for whatever I did.

Sorry about the venting, but it's very therapeutic.

Doug

Edited by Legacy712, 28 April 2007 - 03:52 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users