Win2k pro reboots on startup

 
I don't know if anyone has a take on this.
Turned on my computer 2 days ago, win2k startup screen appears, the blue bar completes, and then chkdsk appears. It runs, reports no problems w/ windows files/folders, and then  reboots!
This repeats ad nauseum. win2k starts up only in safe mode.
I checked for viruses and spyware. Nothing reported.
I ran emer disc repair. When it finished checking, computer reboots and reboots, and reboots.
Temp are ok in bios. 39c +/-  1-2c. No settings were changed.
IN normal startup, it will go to chkdsk, report no errors, and reboot.
I installed win2k Pro, sp4 about 2 months ago. Have had no problems since. I have not added any new programs recently. The last session experienced no lockups, & normal shutdown.
My system is: win2k-sp4 -fat32 file system
MSI K7N2 (6570) MB, Athlon XP 3200+, 1GB DD corsair memory (2-512mb sticks),  cooler master variable speed cpu cooler, ATI 9700 Pro video w/128mb, onboard sound,  60gb 7200rpm maxtor HD, TDK 40x CD burner, LS-120 floppy, SBC DSL with online protection- anti-spy & anti-virus,
Any ideas on this weird rebooting? I don't want to have to go thru a reinstall if I can fix this.

 
Thanks All for your feedback.
The problem was my SBC DSL software was corrupted. Uninstalled it and the computer started right up. I'll reinstall it tomorrow.
The system log was the key. The error messages seem to point to network related issues.
There is a turn offf to the automatic boot, but it doesn't help.
I was about to reinstall win2k when I read your posts. Saved me a lot of hastle.
Thanks again.

Similar Messages

  • Not all users are displayed for log on after a reboot or startup...

    Problem summary: Not all users are displayed for log on after a reboot or startup...
    This problem only occurs after a fresh start-up or restart. The only users displayed are the initial (admin user) and "Guest". Two other (non-admin) users are not shown for log on.
    To work around this problem and get them to log on we have to log on as the admin user, then we can see the other users in the Fast User Switching menu (top right-hand corner of the screen), listed under the current logged on user. After selecting the non-admin user we can log in and use the laptop as normal.
    If we lock the screen, use fast user switching or log out all users; all users are available for log in, until a reboot is done; at which point the non-admin users disappear again and we have to log in as the admin user and use fast user switching again.
    The laptops are both brand new MacBook Airs. The initial configuration of Mac OS X Yosemite was done using the Apple ID of the purchaser (parent) and then the OS was patched, immediately, through the App store (no further updates available as of the date of this posting). After this Family Sharing was activated and new users set up for the two children who will be using these laptops.
    Has anybody else experienced this problem with Yosemite?
    Cheers,
    David.

    David,
    Users not enabled for FileVault unlock are only able to log into the computer after an unlock-enabled user has started or unlocked the drive. Once unlocked, the drive remains unlocked and available to all users, until the computer is restarted.
    FileVault has to be On.
    To Enable the users to be able to unlock FileVault Go to:
    System Preferences > Security & Privacy > FileVault ( Tab ) > Click the Lock in the bottom left > Put in your administrator password > Should see an option to Enable Users > Enable User.
    Hope that helps,
    Weston
    Supporting Articles,
    OS X: About FileVault 2 - Apple Support

  • My macbook pro went from startup screen to grey vertical stripes

    my macbook pro went from startup screen to grey vertical stripes with a bit of flashing.  Force quit twice and it is still doing it.  Had a bit of problem last time I started it with flashing screen, but it settled.  After leaving it on screen went black (as usual) and on waking had desktop up but continued to flash.  Any suggestions?

    Hi there Lochside,
    You may find the troubleshooting steps in the article below helpful.
    Apple computers: Troubleshooting issues with video on internal or external displayshttp://support.apple.com/kb/ht1573
    -Griff W. 

  • TS1365 My MacBook Pro will not startup.  At all.  The suggestions from Apple Support are not helping.  At all.  Someone help?!?

    My MacBook Pro will not startup.  Its not responding at all.  Does anyone have any suggestions on how I can correct this?

    HI Catherine,
    First, make sure it it shut down by holding down the power button for 5-10 seconds. Plug in the power adapter. Press the power button and hold down the shift key to see if you can start in Safe Mode.
    If the power adapter and/or battery are known good, the next thing I'd check would be the RAM to make sure it is securely seated. If batt and/or power adapter are questionable, then you'll want to find one or both and try them out; if you don't know someone with a similar MBP, this might be most easily accomplished by making a free appointment at an Apple Store "genius" bar.

  • My macbook pro will not startup, startup disc is full

    my macbook pro will not startup, startup disc is full

    Freeing Up Space on The Hard Drive
      1. See Lion/Mountain Lion/Mavericks' Storage Display.
      2. You can remove data from your Home folder except for the /Home/Library/ folder.
      3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
      4. Also see Freeing space on your Mac OS X startup disk.
      5. See Where did my Disk Space go?.
      6. See The Storage Display.
    You must Empty the Trash in order to recover the space they occupied on the hard drive.
    You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
    Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.
    If you are no longer able to boot your computer, then the drive is too full and has become corrupted. You may be able to repair it using Disk Utility on your Installer DVD:
    Repair the Hard Drive and Permissions
    Boot from your Tiger Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    If this doesn't work, then you will have to erase the drive and install OS X from scratch. From the Tiger installer disc you will choose the Erase and Install install option.

  • MacBook Pro will not startup, cursor spins forever

    MacBook Pro refuses to startup no matter how long I wait for the spinning cursor to finish. I suspect hardware, because the last successful startup generated some strange bursts of static as it started up.
    I've tried a few successive startups all with the same result. The very last time I held down the "D" key but no diagnostics ever appeared to run.

    If I bought OS from apple store, can I just reload onto the new disk, plug it into bad machine and then select it with opt/alt key at power on?
    Yes.
    The Mac will boot just as easily from an external drive, so if you have an enclosure, you could put your spare drive there initially, or swap drives immediately if you prefer.
    The rub is: if your MacBook is older than about 2011, it needs a Recovery_HD to get the re-download.

  • Help~My 2012 macbook pro won't startup

    Help~My 2012 macbook pro won't startup, it just the black screen. I tried to reset the SMC,but doesn't work.
    I still in the warranty, if I need to replace the parts, do I need to charge for the replace? Thank you~!

    Warranty repairs are ALL FREE! 

  • After updating to Lion my macbook pro does not startup, it is stuck to the grey apple screen

    After updating to Lion my macbook pro does not startup, it is stuck to the grey apple screen

    See Here for Troubleshooting Grey Screen on Startup:
    http://support.apple.com/kb/TS2570

  • My 13" MacBook Pro freezes at startup

    While using Firefox, my Macbook pro frooze about 2 days ago. The screen was only showing the multi-colour spinning circle.
    Pressed [Command + Option + Esc] to force quit. No response
    Pressed Power Button for 10 sec.Power OFF
    Again Pressed Power Button, the MacBook Pro freezes at startup, the MAC makes the startup music, enters a white Screen and is stuck there. There is a light clicking noise continously heard.
    Followed instructions to RESET SMC.
    1. Power OFF.
    2. Press [Shift + CNT + OPT + Power Key] and release at same time.
    3. Power ON.
    There was no response.
    Attempted multiple times to switch-ON and OFF MAC-Book. No response
    Attempted RESET SMC multiple times. No response.
    Then suddenly when I gave up, it unfreeze after 15 minutes and enters the login screen.
    Did a normal shut-down and power up. It was OK.
    Then, ran the Firefox in debug mode and disabled the plug-ins.
    It was stable for a 2 hours.
    Then again, got the spinning colour circle.
    So, took it to the service center last afternoon here at North Point, Hong Kong. The engineer there instructed me to backup the hard-disk and recover the CD.
    Brough the machine back to my home.
    Since the spinning colour circle would not stop, powered OFF the device.
    On POWER ON, the screen freeze. Just like the first time.
    Tried RESET SMC, Nor esult. Left the device power-on for an hour. No result.
    Then, inserted the recovery CD. Powered OFF the Macbook Pro. Powered ON  and pressed "C" immediately. No response. The CD is now stuck inside the MACBook Pro.
    Still have the white Screen at Power-On.
    Advice how to solve this problem

    Disconnect all peripherals from your computer. 
    Troubleshoot the spinning beach ball
    Common symptoms of a dying hard drive
    Hard drive is making a clicking, whirring, grinding, ping pong ball noise or any other type of unusual noises.
    Hard drive is not spinning.
    Computer is not recognizing the hard drive.
    Sluggish loading of applications.
    System freezes and hangs.
    An interesting site - Hard Drive Sounds by drive manufacturer.
    Mac OS X: Starting up in Safe Mode
    Apple Portables: Troubleshooting the slot load optical disc drive

  • Running Weblogic in Cluster mode on Win2K Pro

    Hi :
              I am running WL5.1 (sp8) on Win2K Pro, Is there any limitation that I cannot
              run Weblogic as Clustered in Win2k Pro ??.
              and how to setup Multicast IP Address ?. I tried with the default 237.0.0.1
              (using it with -D option to start the server) and other MultiCastIPs too I
              am having some problems :
              Note : I dont have any weblogic cluster / other applications that use the
              above MIP.
              =====================
              C:\weblogic>java utils.MulticastTest -n server111 -a 237.0.0.1
              ***** WARNING ***** ***** WARNING ***** ***** WARNING *****
              This utility should NOT be run on the same multicast address as a running
              WLAS cluster.
              Pausing for 5 seconds prior to starting test.
              Starting test. Hit any key to abort
              Set up to send and receive on Multicast on Address 237.0.0.1, on port 7001
              Will send a sequenced message under the name server111 every 2 seconds.
              Will also inform console every 600 seconds if no messages received
              New Neighbor server111 found on message number 1
              I (server111) sent message num 1
              java.net.SocketException: socket closed
              at java.net.PlainDatagramSocketImpl.receive(Native Method)
              at java.net.DatagramSocket.receive(DatagramSocket.java:392)
              at utils.MulticastTest$Receiver.run(MulticastTest.java, Compiled
              Code)
              I (server111) sent message num 2
              can anyone help me understand what the above problem is all about ?
              thanks
              Balaji.
              

    Balaji Venkataraman wrote:
              > Hi :
              >
              > I am running WL5.1 (sp8) on Win2K Pro, Is there any limitation that I cannot
              > run Weblogic as Clustered in Win2k Pro ??.
              Not that I know of. Does this happen all the time.
              -- Prasad
              >
              > and how to setup Multicast IP Address ?. I tried with the default 237.0.0.1
              > (using it with -D option to start the server) and other MultiCastIPs too I
              > am having some problems :
              > Note : I dont have any weblogic cluster / other applications that use the
              > above MIP.
              > =====================
              > C:\weblogic>java utils.MulticastTest -n server111 -a 237.0.0.1
              > ***** WARNING ***** ***** WARNING ***** ***** WARNING *****
              > This utility should NOT be run on the same multicast address as a running
              > WLAS cluster.
              >
              > Pausing for 5 seconds prior to starting test.
              >
              > Starting test. Hit any key to abort
              >
              > Set up to send and receive on Multicast on Address 237.0.0.1, on port 7001
              > Will send a sequenced message under the name server111 every 2 seconds.
              > Will also inform console every 600 seconds if no messages received
              >
              > New Neighbor server111 found on message number 1
              > I (server111) sent message num 1
              > java.net.SocketException: socket closed
              > at java.net.PlainDatagramSocketImpl.receive(Native Method)
              > at java.net.DatagramSocket.receive(DatagramSocket.java:392)
              > at utils.MulticastTest$Receiver.run(MulticastTest.java, Compiled
              > Code)
              > I (server111) sent message num 2
              >
              > can anyone help me understand what the above problem is all about ?
              >
              > thanks
              > Balaji.
              

  • After Effects CS6 and Premiere Pro CS6 Long Startup and Application Hang

    Problem:
    After Effects and Premiere Pro CS5.5 and CS6 are very slow to start all of a sudden.  Around 5 minutes to get to/by the intro dialogue box.  For AE, the majority of the time is spent on the "initializing user interface." Then, if I can make a comp, and even a layer inside that comp, it will "Hang" if I attempt to open AE's General preferences for example (no preferences window ever comes up).  This "hang" is what the Event Viewer in windows calls it, with the faulting module being afterfx.exe.  Premiere is not much different.   It makes it to the new project window fast, but after setting project parameters and creating the first sequence, I can't get into the preferences either and the application hangs.  It is important to note that if I have another application open, like Chrome or Firefox for example at the time the application hangs, they will freeze as well.  As soon as I kill the Afterfx.exe process, they come back to life.
    I have read nearly all threads on the subject, and am struggling to find a solution:
    Deleted preferences folder under my username's appdata.
    Turned off Firewall (network traffic from dynamiclink, qtserver, etc was allowed, but what the hay)
    ran windows system file checker/malwarebytes/rkill/rootkit detection.
    checked for windows compatibility checkboxes under the file.
    Uninstalled Wacom Tablet drivers
    Disabled Aero
    Started with ctrl-alt-shift to delete pref.
    uninstalled video driver and replaced with one 6 months ago.
    uninstalled, reinstalled, and tested various quicktime versions back to version 7.69
    moved plugins folder
    moved opengl's plugin out of the folder temporarily
    Disabled all 3rd party codecs (xvid was the only one installed and for months)
    reinitialized default directshow filters
    checked for adobe font list (none found) and removed any fonts from 1 month ago to present.
    used msconfig to selective startup without other applications/services running.
    Uninstalled all adobe products, and reinstalled.
    I performed all of these in a systematic manner, trying to solve the problem.  None have fixed the problem.
    So it doesn't seem to be a network issue, a codec issue, a plugin issue, a driver issue, font issue, or conflicting application.  Any thoughts?
    System Info:
    PC Windows 7 pro 64-bit SP1
    Core i7 - 960 24GB ram
    AMD Radeon 6750  v12.10
    Adobe CS6 Master Collection

    Who's says that Microsoft can't debug?
    I used msconfig, first disabling startup items, -same result.
    Enabled all startup items, disabled all non-microsoft services - AE worked!
    I re-enabled each service in turn until AE crashed.
    The fault was related to an item for a video streaming device I have in my house.  It was Monsoon-multimedia's Vulkano Service.  Sometimes under the old name of Hava, this is an app that acts like a sling-box to send my Cable TV to my screen.  It does load a couple of virtual devices in device manager, and uses a proprietary codec.
    I uninstalled the vulkano streamer application and rebooted the external Vulkano device.  I reinstalled the Vulkano and verified it connected to the device and could stream.  Once it did, I tried AE again and IT WORKED!
    I wonder if simply rebooting the Vulkano would have fixed it.  Its like opening the garage door to turn on the refridgerator.
    Thanks for the help!
    Jim

  • Mac Pro Reboot or Restart Problems

    I have a Mac Pro G5 that's about 3 months old and whenever I do a reboot (either from the Apple menu or ControlAppleDelete), the MacPro immediately goes to a black screen and sounds began to emunate from the drive area like it's trying to catch. The only way to stop the sound and really reboot is to unplug the G5. Now, sometimes the warning screen appears which mentions there is like 2 minutes before it restarts, but most of the time, it doesn't even appear. Regardless if I get the warning or not, the black screen and skipping sounds always does. I've reported it Apple and they've suggested taking it into a Apple Certified Center as it's still under warrenty.
    Side note: a couple times in the last few days, the G5 has gone to sleep and I could not wake it without having to unplug. Finally, I set the hard drive to Never go to Sleep in the Energy Saver prefs. I think that might be working because it hasn't happened since.
    I don't think its the "85% hard drive is full" or the RAM is suspect (2 gigs installed when purchased from Apple). It's perplexing. We have an identical G5 in the office that is perhaps 2 months older and it doesn't do this when I've tested it.
    While I don't reboot or restart often, my concern is the problem could began to surface on initial start ups. I'm waiting for the local Apple store to return my call but I thought I'd check with a Discussion Thread as well. Thanks for your time!

    +Do those items point to something you installed or use? Aladdin?+
    The only tie to Aladdin I can find is StuffIt Expander, which I don't believe I installed directly on this Mac Pro. However, I did check the Startup Script on my current G4 Mac and it does include the reference to Aladdin in the Startup and on the G4, it says it was successful. On this Mac Pro, it states it was not.
    +There are three tabs in Disk Warrior. Directory you can hold OPTION and it changes to REBUILD... and then you can click on SCAVENGE. There is a file repair tab. And you can manually check hard drive status. I would not use anything extra for drive status and smart. Too many of a good thing.+
    I have already rebuilt the Directory with Disk Warrior. Should I do it again using the OPTION>SCAVENGE approach?
    +When you click on manual drive check, it writes to the system log what the count of bad blocks used, attempts, and stuff.+
    I did the manual drive check but cannot seem to find the system log related to logging this actual event. However, the description box did say the drive checked out okay.
    +I do think it needs some bench time with AppleCare as to what is up.+
    I tend to agree. It would ease my mind knowing that someone who can read these System logs might be able to decipher these log events. A couple of things I'm wondering could be causing some problems: about the time all this reboot issues had started, I had manually changed my Computer Name in the Sharing pane of System prefs. But its my understanding this is where I could change it without causing any issues. Secondly, I had recently downloaded and installed a mp3 encoding program called iLas, as a alternative to the iTunes so-so mp3 encoder. It does tend to run from an AppleScript-- could this be a culprit?
    Thanks again for your help!

  • MacBook Pro frozen on startup screen with progress bar and then it turns off

    Hello, I have a MacBook Pro 15" of early 2012 with a i5 Intel, 4GB of RAM  and a  500 GB HD.
    I was installing the new suit of Adobe, when suddenly my Mac got frozen, vertical coloured lines appeared and the image on screen went distorted. I had to reboot the Mac by holding the power button until the screen turned off and when I turned it on, the lines appeared again and it itself automatically rebooted. Then the screen (now with no vertical lines) got frozen on the startup grey screen with the apple logo and the spinning wheel for hours with no response.
    I tried to follow the steps of the official mac forums like verifying the HD with CMD+R and then Disk Utility, it says everything's fine; the same happens with CMD+S, no errors. I reinstalled Mavericks with the same CMD+R. I already reset the PRAM, SMC  and performed a Safe Boot staring up in Single user mode and Verbose Mode and nothing, the same startup screen. I made too thins thing of holding shift until the progress bar appeared.  Three days later (Today) I repeated the steps again and finally the verbose mode. Now, when I turn it on, the startup screen appears again (Apple Log and spinning wheel) with a progress bar. When it completes, the Mac turn itself off.
    if you can help me, please. I don't know what else to do. The last thing is technical service.

    Hi again ggt15,
    You can find some more information about the Recovery Partition of your hard drive here:
    OS X: About OS X Recovery
    http://support.apple.com/kb/HT4718
    It sounds like you might be trying to reinstall your copy of the operating system. If that's the case, you may also find some helpful information here:
    OS X Lion: Reinstall Mac OS X
    http://support.apple.com/kb/PH3878
    Thank you for using the Apple Support Community. Due to the nature of your issue or question you may find more information by using another one of Apple's support resources - https://expresslane.apple.com/GetproductgroupList.action.
    Cheers,
    Braden

  • Macbook Pro won't startup after installing of 10.8.4

    I just installed the 10.8.4 combo update package anf my Macbok Pro won't restart. After downloading the updates, the computer restarted itself, finished installing the updates, restarted itsalf again, anf when it gets to the gray screen with the Apple logo and the rotation icon underneath the logo, it just hangs. It goes no further than that. I let it run for about an hour before I tried to restart it manually, but I could never get it past that final screen. How do I fix it?

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.   
    There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
         a. Boot into the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
    b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
    Step 3
    Boot in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is damaged and the drive is probably malfunctioning. In that case, go to step 5.
    If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
    If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 4
    Sometimes a boot failure can be resolved by resetting the NVRAM.
    Step 5
    Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
    Step 6
    Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 7
    Repeat step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a backup.
    Step 8
    A dead logic-board battery in a Mac Pro can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions.
    Step 9
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested.

  • Kextcache related reboots on startup with FileVault2?

    I've been encountering some weirdness over the past week or so...and I'd like to see if anyone else had experienced something similar (and maybe has a solution) or if this may be indicative of a bug of some sort.
    First, the basics: MacBook Pro 6,2, i7 processor, 8GB RAM, OS X 10.7.1, Filevault2 enabled.
    The problem - whenever I boot from a cold start (and occasionally on a restart, but not normally) the system will begin the boot process and then reboot partway through.  At every occurance, the boot messages (I boot in verbose mode) immediately before the reboot are the same and always related to the kext cahes, as in the following representative extract from the logs:
    12-09-11 7:23:05.411 PM com.apple.kextcache: rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache
    12-09-11 7:23:06.292 PM com.apple.kextcache: JMicronATA.kext does not declare a kernel dependency; using com.apple.kernel.6.0.
    12-09-11 7:23:06.581 PM com.apple.kextcache: JMicronATA.kext does not declare a kernel dependency; using com.apple.kernel.6.0.
    12-09-11 7:23:06.862 PM com.apple.kextcache: JMicronATA.kext does not declare a kernel dependency; using com.apple.kernel.6.0.
    12-09-11 7:23:28.868 PM com.apple.kextcache: Created prelinked kernel //System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.
    12-09-11 7:23:28.910 PM com.apple.kextcache: /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache out of date.
    12-09-11 7:23:29.205 PM fseventsd: Logging disabled completely for device:1: /Volumes/Recovery HD
    12-09-11 7:23:30.350 PM com.apple.kextcache: Successfully updated helper partition disk0s3.
    After the reboot, everything proceeds normally and the boot process completes successfully.
    I have rebuilt the entire OS from scratch and this still occurs.  I have also, in order to test alternative configurations, tried booting from a cloned backup.  The only difference between the cloned backup and the internal drive of the MBP is that the internal drive is encrypted with FileVault and the clone isn't.  The clone boots cleanly every time, from both a cold start and a restart.
    In summary, the problem seems to be almost uniquely an issue when cold booting from an encrypted disk.  I'm at a loss to explain it.
    So, has anyone else stumbled across this problem, or something similar?

    Hmm.
    I also recently upgraded to Parallels 7.  However, I upgraded from the Parallels 7 Beta, where I had no issues, so I'm not inclined to think that Parallels is the problem (but I won't rule it out either).
    After some explorartion on the Console logs of the other computers in the house (an older MacBook Pro 4,1 and an iMac 10,1) it seems that my laptop is the only one affected.  And the only one running FileVault2 (and, unfortunately, the only one running Parallels which means I can't conclusively rule it out as the culprit...).  In all three cases, JMicronATA.kext is of the same version and has the same date stamp - which seems to rule out that particular kext as the problem.
    I'm wondering if the FileVault encryption is somehow interfering with the way IOKit builds the device tree at boot time...I'm fairly certain that JMicronATA.kext controls the IDE bus - which in my case means the DVD drive...unfortunately, I don't know enough about that part of the boot process to make anything more than uneducated guesses.  Which isn't really even good enough to file a bug report...

Maybe you are looking for