Packard Bell stuck at start up screen

W

Whiskey

New Member
Reaction score
0
Hi all,

I have taken in a Packard Bell Easynote LJ 61 laptop that runs Windows Vista. The machine starts up and then displays Microsoft Corporation with a scrolling green bar indefinitely.

I have tested the ram and hard drive and both appear to be fine. The customer does not have the original disc so I have attempted to launch my own vista oem disc from the cd player. This gets so far through the process before going back to an endless scrolling green bar.

I have tried to access the recovery partition by hitting ALT f10 at start and this results in the message Edit Boot Options, Path\windows\system 32\boot\winload.exe/detecthal/minint/redirect rdimage offset =8192 rd imagelength=3161088rd path =multi (0) disk(0) rdisk (0) partition(1)\sources\boot.wim

Finally, trying to start in safe mode with command prompt ends with a blue screen stop error 0x0000007E (0xc0000005, 0x879260AE, 0x88340BA0, 0X8834089C)
Volswap.sys address 879260AE base at 87921000 datestamp 47918f92.

Would someone be kind enough to suggest where I go from here?

Cheers,

Whiskey
 
If the green loading bar is sat there continually, it's a good indication of a problem with the hard disk. I sugest you slave the drive and run Crystal Disk to check on the SMART status of the hard drive. I would also run HDTune to look for bad blocks.
 
Or just put in UBCD and run one of the manufacturer's test tools.

That 7B stop error looks like it has a problem with a driver called Volswap.sys Did you mean volsnap.sys?
 
Hi guys,

Thank you so much for getting back to me.

A quick update. I have run an Advanced test using the Hitachi test tool and it tried to correct errors before telling me the device was defective!

Your right as well, about the error message being volsnap.sys. Think I must have fallen asleep by the end of typing it all out. My apologies.

Problem now is the chap doesn't have any back up discs if I fit the new drive. I have emailed Packard Bell to see if they will send me some discs out and what the possible cost is. Can anyone see a problem if I change it to a brand new OEM version of windows 7? Certainly the system is powerful enough to run it and it would be a lot better than Vista.

Cheers,

John
 
It sounds like you've found the problem, but I just wanted to mention that volsnap.sys is a commonly infected file. I have found a number of times that replacing it with a good copy fixes a Vista 7E BSOD.
 
You may be able to clone the drive to a good one (possibly after repairing/remapping bad sectors with something like HDD Regenerator or Spinrite) and get it working after solving the volsnap.sys problem, or maybe be able to copy the recovery partition and boot into it thus negating the need for HP reinstall disks.
 
MobileTechie said:
You may be able to clone the drive to a good one (possibly after repairing/remapping bad sectors with something like HDD Regenerator or Spinrite) and get it working after solving the volsnap.sys problem, or maybe be able to copy the recovery partition and boot into it thus negating the need for HP reinstall disks.
Click to expand...

That what I often do, copy the recovery partition to a new hard drive and mark it as active. When you boot, it should go straight into the recovery partition and as MT says, negate the need for the recovery discs.

It more than likley that volsnap.sys is corrupt due to the hard drive being faulty, I don't think it would infected in this instance although it is a common driver to get infected.
 
Last edited:
Thank you all so much once again for responding.

I must admit I didn't think about copying the recovery sector. It's pretty obvious now you mention it, so I will definately use this method in future. I really am thick at times!

Cheers,

John
 
You must log in or register to reply here.
Back
Top