W10 BSOD Page fault in non_paged area

[Big Jim]

Have a laptop here that won't boot Windows (10)
Drive is a WD Black 250GB.

on boot it asks to run startup repair which also BSODs with the same error.

On our W7 bench machine it causes our machine to crash with this error if we use an SATA/USB connection, will also crash once rebooted as well in an endless loop.
On a W8 machine it hard locks the machine via USB connection. (power off by holding power button in)

Connected it via USB to a MAC and all data seems in tact.

However I don't know what is causing it, and as I can't access it via a windows machine I can't fix it either.

Any ideas ?

 

[Mick]

You may have already seen this, but... https://www.online-tech-tips.com/computer-tips/page-fault-in-non-paged-area-error/ Since it errors out on other, known good, machines too, you'd have to suspect an HDD issue first off.

 

[nlinecomputers]

Nuke and Pave. Pull data from the HDD and replace with an SSD. If the drive is puking as a secondary drive then obviously the drive is bad. Boot from Linux and pull the data that way as I think that will go smoother than trying to use a Mac.

 

[Porthos]

Nuke and Pave. Pull data from the HDD and replace with an SSD. If the drive is puking as a secondary drive then obviously the drive is bad. Boot from Linux and pull the data that way as I think that will go smoother than trying to use a Mac.

Most of the time I pull data with Fab's and my PE disk. I also use parted magic as well.

 

[nlinecomputers]

Most of the time I pull data with Fab's and my PE disk. I also use parted magic as well.

If he can get it to boot that is the way I would go. But he implies that any Windows based system crashes trying to access the drive.

 

[Porthos]

But he implies that any Windows based system crashes trying to access the drive.

Many times a PE disk works but a live system will not.

 

[nlinecomputers]

Many times a PE disk works but a live system will not.

Yes it is worth a try.

 

[Big Jim]

so its definitely the drive and not something wrong with the file system ?

 

[Porthos]

so its definitely the drive and not something wrong with the file system ?

We did not say that, You still get the files backed up before you try anything else.

 

[nlinecomputers]

so its definitely the drive and not something wrong with the file system ?

Nothing is impossible but I can't see how any kind of file system corruption would cause a BSOD as a secondary drive. As the boot drive sure.

 

[Big Jim]

ok, any recommendations for imaging software in linux ?
(don't use linux very much at all to be honest, wouldn't even know a good distro to use)

We use macrium reflect in windows for 99% of the stuff that comes in and if we screw anything up we can just put the image back on the drive.

I am hoping I can just image the drive and transfer the entire image on to a new drive

 

[Porthos]

I am hoping I can just image the drive and transfer the entire image on to a new drive

You can attempt to use Macrium from the boot cd, But if that wont work I would just get the data and start fresh on a new drive.
I never trust images/clones from a failing drive to restore the system from.

 

[Big Jim]

You can attempt to use Macrium from the boot cd, But if that wont work I would just get the data and start fresh on a new drive.
I never trust images/clones from a failing drive to restore the system from.

purely trying to keep time and therefore costs down.

nobody wants to pay to fix machines around here, a new drive + backup/reinstall labour time will probably write this computer off tbh

 

[Big Jim]

so Windows PE environment crashes the same way.
Tried parted magic from Hirens boot CD.
Couldn't clone the drive because the partition is flagged as "dirty" and needs a check disk, however any attempt to do this in a windows environment will crash/lockup. I did try FSCK but that failed as well.
So I need a way to run checkdisk from DOS that supports a W10 drive.
Tried Hirens DOS options but it only appears to load 1 drive and can't see this one.

I can't even load the W10 recovery environment which is the way I would normally do this.

 

[Mick]

You are cruisin' for a bruisin' here. We're already pretty sure the disk is banjaxed one way or another. Running CHKDSK on it in that state is likely to be the final nail in its coffin. Just get whatever data you can scrape off it and give your client the bad news.

 

[AlexCa]

Yes, and even if you're able to clone it think it's very unlikely that the cloned OS will work fine. You'd probably face more issues ahead.

 

[Larry Sabo]

nobody wants to pay to fix machines around here, a new drive + backup/reinstall labour time will probably write this computer off tbh

Then I think you're wasting your time, and ours. Just tell your customer it's not economically repairable and move on to the next job. I hope you have verified with the customer that his data is not worth the effort to recover it. If they puke at the idea of losing their data, give an estimate of what professional data recovery would cost, plus what your best effort would cost. If the former is out of the question, I'd suggest you clone/image the drive with HDDSuperClone then recover what you can. You've beaten that poor drive to death already so who knows whether any data can be recovered now.

PS: CHKDSK on a failing drive is guaranteed to kill any chance of recovering a lot of data. It you need to run it, do it on a clone, after you've cloned the clone.

 

[nlinecomputers]

Then I think you're wasting your time, and ours. Just tell your customer it's not economically repairable and move on to the next job. I hope you have verified with the customer that his data is not worth the effort to recover it. If they puke at the idea of losing their data, give an estimate of what professional data recovery would cost, plus what your best effort would cost. If the former is out of the question, I'd suggest you clone/image the drive with HDDSuperClone then recover what you can. You've beaten that poor drive to death already so who knows whether any data can be recovered now.

PS: CHKDSK on a failing drive is guaranteed to kill any chance of recovering a lot of data. It you need to run it, do it on a clone, after you've cloned the clone.

This +10,000

Seriously you have already blown away many hours you can't bill. On a semi-decent system, you can install Win 10 in around 15-30 minutes.

 

[Sky-Knight]

That BSOD is either bad ram, or a bad hard disk, every... single... time.

https://www.memtest86.com/

If that runs through 7-8 passes, you're good on RAM, then replace the hard disk.

 

[Big Jim]

Data is recovered. \o/
I connected the drive to anther system running XP that the same customer brought in (just to see if it crashed that as well)
And it worked!

Data recovered with FABS, currently running checkdisk
once that is done will scan the HDD see what kind of state it is in.
memtest is a good shout though will get that going now as well.




Talking about hours not being billable, i had a system in that was data transfer/windows reinstall, then reinstall all programs including office and email config etc, then setup again etc.
Got all the work done, and thought this system isn't running like an I5 system with a fresh install of W10 should.
Ran memtest and it threw up errors, so swapped out the ram, tried some of our (known good) ram and its still throwing up errors.
I assume the damn board is bad, took the laptop apart to inspect the board and find that it is a replacement board as it has a sticker on it from the supplier (chinese company so I assume ebay)

Although I can't categorically say the error is down to the damage I found on the board its pretty likely that it is.
Called the customer and explained what was going on, sold them a refurbed machine, but obviously the work starts again now.

How do you bill for that

I think I will just charge as I originally agreed (which includes the windows install) and have to eat the extra time