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

Windows 7 Startup issues


  • Please log in to reply
7 replies to this topic

#1 sg1974

sg1974

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 13 April 2013 - 05:16 PM

All,

I am a newbie to this forum. I swapped my XP hard drive with Win 7 and I am experiencing boot up issues while starting my computer.

After reading through different posts, I generated all logs including Farbar Recovery Scan Tool logs. I am not able to identify the  problem from FR Scan log. So I want your help on fixing this issue. 

 

Start up Repair log

 

 

Problem signature:
  Problem Event Name: StartupRepairOffline
  Problem Signature 01: 6.1.7600.16385
  Problem Signature 02: 6.1.7600.16385
  Problem Signature 03: unknown
  Problem Signature 04: 21199818
  Problem Signature 05: AutoFailover
  Problem Signature 06: 6
  Problem Signature 07: BadDriver
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033
 
Diagnosis and Repair details
Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ?4/?10/?2013 8:34:55 PM (GMT)
Number of repair attempts: 7
 
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = D:\Windows
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 125 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 156 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Root cause found: 
---------------------------
Startup Repair has tried several times but still cannot determine the cause of the problem.
 
---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = D:\Windows
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 109 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 156 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 436 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 62 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms
 
Root cause found: 
---------------------------
Startup Repair has tried several times but still cannot determine the cause of the problem.
 
---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = D:\Windows
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 125 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 172 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 405 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms
 
Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Test Performed: 
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 1014 ms
 
Test Performed: 
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 4727 ms
 
Test Performed: 
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code =  0x0
Time taken = 2137 ms
 
Test Performed: 
---------------------------
Name: Access control test
Result: Completed successfully. Error code =  0x0
Time taken = 7816 ms
 
Test Performed: 
---------------------------
Name: File system test (chkdsk)
Result: Completed successfully. Error code =  0x0
Time taken = 32214 ms
 
Test Performed: 
---------------------------
Name: Software installation log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Root cause found: 
---------------------------
A recent driver installation or upgrade may be preventing the system from starting.
 
---------------------------
---------------------------
Below is the Farbar Recovery Scan Tool result
Mod Edit:  Removed FRST data, malware log...not allowed/used in this forum - Hamluis.

Edited by hamluis, 13 April 2013 - 07:22 PM.
Edited post - Hamluis.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 42,580 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:58 PM

Posted 13 April 2013 - 07:13 PM

<<I swapped my XP hard drive with Win 7...>>

 

What doe that mean?

 

You installed a legal version of Win 7...over an XP install?

 

You switched hard drives from two different systems?

 

Exactly what did you do...and why?

 

Louis



#3 sg1974

sg1974
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 13 April 2013 - 07:24 PM

Thanks for reply. Its my work pc. My XP machine crashed and they gave a Win 7 image hard drive. I installed new hard drive with Win7 image in old pc. I am able to narrow it down to "classpnp.sys" and renamed it .old. After that now when its loading in safe mode I am getting stuck at disk.sys.driver now.


Edited by sg1974, 13 April 2013 - 07:25 PM.


#4 dougphillip

dougphillip

  • Banned Spammer
  • 5 posts
  • OFFLINE
  •  
  • Local time:07:58 AM

Posted 14 April 2013 - 11:00 AM

Could be a registry issue man. It's probably worth a try using a registry cleaner like the one at the top of suitablelinks.com.

 

Good luck



#5 Queen-Evie

Queen-Evie

    Official Bleepin' G.R. I. T.S. (and proud of it)


  • Global Moderator
  • 8,723 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:My own little world. They know me here.
  • Local time:03:58 PM

Posted 14 April 2013 - 12:42 PM

Bleeping Computer DOES NOT recommend the use of registry cleaners/optimizers for several reasons:
  • Registry cleaners are extremely powerful applications that can damage the registry by using aggressive cleaning routines and cause your computer to become unbootable.
    The Windows registry is a central repository (database) for storing configuration data, user settings and machine-dependent settings, and options for the operating system. It contains information and settings for all hardware, software, users, and preferences. Whenever a user makes changes to settings, file associations, system policies, or installed software, the changes are reflected and stored in this repository. The registry is a crucial component because it is where Windows "remembers" all this information, how it works together, how Windows boots the system and what files it uses when it does. The registry is also a vulnerable subsystem, in that relatively small changes done incorrectly can render the system inoperable. For a more detailed explanation, read Understanding The Registry.
  • Not all registry cleaners are created equal. There are a number of them available but they do not all work entirely the same way. Each vendor uses different criteria as to what constitutes a "bad entry". One cleaner may find entries on your system that will not cause problems when removed, another may not find the same entries, and still another may want to remove entries required for a program to work.
  • Not all registry cleaners create a backup of the registry before making changes. If the changes prevent the system from booting up, then there is no backup available to restore it in order to regain functionality. A backup of the registry is essential BEFORE making any changes to the registry.
  • Improperly removing registry entries can hamper malware disinfection and make the removal process more difficult if your computer becomes infected. For example, removing malware related registry entries before the infection is properly identified can contribute to system instability and even make the malware undetectable to removal tools.
  • The usefulness of cleaning the registry is highly overrated and can be dangerous. In most cases, using a cleaner to remove obsolete, invalid, and erroneous entries does not affect system performance but it can result in "unpredictable results".
Unless you have a particular problem that requires a registry edit to correct it, I would suggest you leave the registry alone. Using registry cleaning tools unnecessarily or incorrectly could lead to disastrous effects on your operating system such as preventing it from ever starting again. For routine use, the benefits to your computer are negligible while the potential risks are great.

#6 Cyrus not the Virus

Cyrus not the Virus

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:58 PM

Posted 15 April 2013 - 05:49 AM

I totally agree that registry cleaners are extremely powerful applications that corrupt the registry and render your system 'Not Responding' all the time.

I am crying right now over my laptop. How about using ERUNT or CCleaner to backup the registry?


Edited by Cyrus not the Virus, 15 April 2013 - 05:50 AM.


#7 noknojon

noknojon

    Almost Retired


  • Members
  • 9,645 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Victoria Australia
  • Local time:06:58 AM

Posted 15 April 2013 - 06:33 AM

Could be a registry issue man. It's probably worth a try using a registry cleaner like the one at the top of xxxxxxxxxxx

I would request that what looks like a Spam link, be removed from the above post, as the program looks like a waste of time.

I downloaded it in spare box, and it was generally a waste of time ................

 

Please read the post from Queen-Evie, and take notice of that -

 

Each "so called" RegCleaner / Speed Up My PC type program will harm your system and cause problems.

 

Once installed these programs can also leave Tracking programs and send information back to a data base.

Often these are setups by Scammers to steal information and are totally useless for repairs -



#8 hamluis

hamluis

    Moderator


  • Moderator
  • 42,580 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:58 PM

Posted 15 April 2013 - 07:31 AM

Can we please...return to the topic at hand...see title.  Thanks :).

 

<<My XP machine crashed and they gave a Win 7 image hard drive. I installed new hard drive with Win7 image in old pc>>

 

If this is a work system...your IT person in charge should know that inserting a hard drive from a different system...and with a different O/S...is unlkely to boot/run properly.  I don't know the origin of this drive but the settings/drivers installed probably do not match up with your work system.

 

In any case, this issue should be taken up with your work IT personnel, IMO.

 

Louis


Edited by hamluis, 15 April 2013 - 07:37 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users