A odd windows or hardware problem?

Phil2008 · 31 Jul 2013 at 13:49

I built a ITX PC for a mate over a year ago, and a few months ago windows wouldn't completely boot and kept hanging and if I booted it up in safe mode it always stopped after "classpnp.sys"

He brought the pc back to me and the first thing I did was to back up the SSD just incase that was failing. Then after that I tried.....

Using the recovery option on the windows cd, but no luck at all.
Tried fdisk, but it couldnt access the ssd at all

So I thought I would try cloning the ssd to one of my spare hdds using true image. This is where it gets odd, when it had finished cloning, I rebooted the pc expecting it to hang again but it loaded windows fine. So I thought "how odd". I checked the ssd, no probs with that, then I ran all windows updates. I must have rebooted the pc about 15times and it never hanged once. so I told my mate, I had no idea what the prob was, as it just started working again.

Yesterday he message me again after about a month, saying pc is playing up again, so Im guessing windows wont boot again. So have you guys got any ideas what could be causing this odd fault? Im going to update the ssd's firmware and do a bios update, and see if that will jumpstart it again, and if not, I'll try the cloning trick again.

wazza300 · 31 Jul 2013 at 13:56

what make/model ssd? its probably that

Phil2008 · 31 Jul 2013 at 14:02

wazza300 said:
what make/model ssd? its probably that

crucial M4 120GB. Ive checked the speed, health and ran fdisk and all looked fine.

wazza300 · 31 Jul 2013 at 14:04

look for the 5400 hour bug

load ssdlife and see what fw version and the hours use

Sliver · 31 Jul 2013 at 14:14

Just for info - The firmware version for the M4 that had the 5400 hour bug was 0309.

Phil2008 · 31 Jul 2013 at 14:16

wazza300 said:
look for the 5400 hour bug

load ssdlife and see what fw version and the hours use

I updated the fw when I built the pc to fix that bug. If I remember rightly the ssd has only had about 20hrs of use or even less then that and its been powered up a stupid number of times.

wazza300 · 31 Jul 2013 at 14:22

using latest motherboard bios?

can't think what else it could be

EDIT: checked all internal cables,sata data cables ect? swapped them out for another cable just to be sure

Phil2008 · 31 Jul 2013 at 14:30

wazza300 said:
using latest motherboard bios?

can't think what else it could be

Thats what Im going todo this time, update the bios for the motherboard and firmware for ssd. Hopefully that will jumpstart windows again.

If windows loads fine after, my mate will just have to see how it goes, but Im thinking if it happens again I could let him borrow my 64gb M4 SSD and see if that fixes the prob?

Phil2008 · 31 Jul 2013 at 14:33

wazza300 said:
EDIT: checked all internal cables,sata data cables ect? swapped them out for another cable just to be sure

Yeah I might swap the data cable aswel, thanks

Merlin5 · 31 Jul 2013 at 14:43

The problem doesn't seem to be hardware. It seems to be the classpnp.sys you first mentioned. It would appear to be corrupted.

http://social.technet.microsoft.com...nantly-fix-classpnpsys-after-successful-login

The error named classpnp.sys is caused by the registry changed, if you have a registry backup, please restore it. If not, you may run “sfc /scannow”(without quotes) command to repair system.
If the issue persists, you’d better have an In-Place upgrade to repair system.

Phil2008 · 1 Aug 2013 at 08:02

Well Ive got the pc , updated the bios and the ssd firmware but windows still wont boot, so Ive left it for now as there isn't any rush to fix it. Any ideas guys?

Phil2008 · 1 Aug 2013 at 08:05

Oh yeah and Ive tried replacing the "classpnp.sys" file with mine, but still no joy

Merlin5 · 1 Aug 2013 at 16:41

Perhaps reinstall windows, Phil? That might fix it. I found this out about classpnp

"It is not easy to fix classpnp.sys boot error manually because of unknown problem areas. You can copy this file from another system and paste it to the same location. Sometimes it might help but the fact is, there is a very small chance to fix this error by this method.

The classpnp.sys boot error may occur due to various reasons:
classpnp.sys files missing, delete or damaged
Virus, Malware.
Outdated or incompatible driver installed.
Corrupted Reg files, dll files, exe files, etc"

Phil2008 · 5 Aug 2013 at 22:49

Well it looks like the SSD is bust, as it wont secure erase or chkdsk. Ive restored my mates data on my spare hdd and it booted up into windows no problem. Then I tried connecting the ssd as a 2nd drive, and booted up again, but got stuck at the "classpnp.sys" file, even tho it was booting from my hdd. So Im guessing after windows loads "classpnp.sys" it detects the drives, but is has trouble detecting the SSD so it just hangs.

I have sent the e-retailer a email saying all of this and asked for a refund or replacement, but I haven't heard back from them yet, but Im guessing they will say get in contact with the manufactures as its 14-15 months old.