How to create a hard drive BSOD (yes you read it correctly).

Toggle sidebar Toggle sidebar
J

j4g3d

Distinguished
Feb 12, 2012
30
0
18,530
ODD question i know, as most people want to fix this problem lol.

Basically fixed a customers £4,000 workshop/industrial machine as it was blue screening and saying 'Unmountable Boot Volume'.

Customer no longer wants it repaired and wants it back in its original state. Well i've since repaired it, so how do i put it back into its original state?.. Im guessing maybe delete some OS files, but which ones will give this exact blue screen error im after?.

Not vouching on anyone actually knowing this, i may have to play around with it. But worth a pop.

Thanks
 
Sort by date Sort by votes
smorizio

smorizio

Titan
Jan 22, 2010
30,984
9
125,315
your better off not touching the unit and let it fail by itself. if it a hardware or power issue causing the drive to fail it will fail again. if you thought you fixed the issue before warranty service could look at it and now they cant force the error to show up....then it may have been someone fooling with the hardware or a virus. as a tech make sure you have the customer ok to fix stuff before you tuch anything.
 
Upvote 0 Downvote
J

j4g3d

Distinguished
Feb 12, 2012
30
0
18,530


Already he gave the go ahead to try repair, then changed his mind within 1 hour... like i said. At this point a chkdsk repair was already made successfully. I would of then given the customer a new hard disk and put all his files on the new disk (didn't get this far).

Anyway...

back to the question if anyone can help?
 
Upvote 0 Downvote
mcnumpty23

mcnumpty23

Polypheme
Jul 15, 2011
15,519
0
66,960
could delete the boot record

if they agreed to pay you to fix it then they should pay up

could just deny you fixed it and say it started working on its own--only reason i can think of they would want it back as it was is some one offered to fix it far cheaper than your price
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
it is pretty easy to generate that bugcheck, but to get the exact failure you would have to know the exact suberror code contained in the memory dump. IE parameter 1 of the bugcheck code. If you did indeed fix the problem you would undo your fix. If you just blindly applied a bunch to solutions and one of them "fixed" the problem then it would be harder to undo.

here are some examples that would cause this bugcheck:
- a loose data cable can cause these errror but you would have a CRC error code
- hard disk partition logically assigned a different drive letter. (often caused by inserting a USB drive with a active partition on it)
- active partition on the drive deactivated
- BIOS set to boot off a incorrect partition
- logical corruption of a file system data structures (various causes of this)

- then there are actual issues like corruption of the master boot record on the drive that can cause this.
- incorrect drivers for the SATA controller
- various conflicts in hardware BIOS setting (most often caused by changing hardware with out a BIOS reset)

If you don't know what fixed the problem you should just return the drive and not waste more time by trying to break the system again.
 
Upvote 0 Downvote
S

ss202sl

Glorious
May 23, 2012
8,431
35
44,190
Let me get this straight.
You spent time only(no hardware) fixing a computer.
Now customer say's don't fix it.
Now you want to spend more time undoing what you already did?

Just leave it and give it back fixed. It makes no business sense to spend more(unpaid) time on this.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom