Windows error recovery & bsod

Pztm021 · 28 Nov 2015

Hi guys! I am absolutely incapable in the tech world... i hope someone here can help me. I have a dell vostro 3500 running windows 7... ive had it for 5 years so he's an old man but except for getting hot he worked fine. Today i woke up and turned on the computer... the windows error recovery screen came up with 2 options. 1) launch start up repair (when doing this, it says "windoes is loading files... then the screen goes black for about a minute, and then a lightblue screen appears with my mouse cursor. I can move the cursor but thats all i can do. I cannot reach task manager and also i dont get the sticky keys pop up when clicking shift a lot as some people suggested solves their problem. The only thing left to do is force shut down via power button.)

2) start windows normally (when doing this, the "starting windows" screen comes up with the logo.. it gets stuck here for about 1 minute, then for a split second the blue sod comes up and then it reboots and im back at the windows error recovery screen.)

I've tried f8 to safe mode, but it also ends in the bsod, and reboot to error recovery screen.

I have no cds, no other functioning computer around, and some files on the laptop that arent backed up (just great, right? Ughhh)

Help please! Thanks a lot

**axe0** · 28 Nov 2015

Hi Pztm021,

What error code is displayed on the screen?
It looks something like

Driver_irql_not_less_or_equal is the name of the crash, is variable and doesn't always have to be there.

'STOP: 0x000000D1' is the error code, also variable but is always present.
Then there is also the gv3.sys, this is a file and also variable, the file doesn't always have to be there.
The file could give a direction of what could be the cause or from where to start if it is present.

Simply, please make a photo of the bluescreen and post it.

Please have a look at Hardware Diagnostics for some diagnostics tests for the hardware.

If you have any question, please ask :)

Pztm021 · 28 Nov 2015

Hi axe, thanks for your reply. The problem is that the blue screen flashes for a millisecond. I can't even take a picture of it with my phone (ive tried). Its too quick and then reboots back to the error screen. Im now running the extended diagnostics test. Lets see if anything comes out...

Pztm021 · 28 Nov 2015

Diagnostics say: error code 0f00:1344. Ive googled.. says thats a harddisk error. Thats it, computer dead, files lost?

**axe0** · 29 Nov 2015

What test were you doing?
Please give a little more information, this error code could mean a lot of things as it could be from a lot of things.

Pztm021 · 29 Nov 2015

Im doing the extended test. The pop up says the following, ive attached a pic.

**axe0** · 29 Nov 2015

It is a disk read error, this means nothing can properly get access to the files from the hard drive.

As it says, replace the drive, it may be possible to get the files from the hard drive, but you need a docking station.

The first thing to do is make sure you have the tools required to connect this drive to another computer safely. Ideally,some kind of SATA/IDE to USB cable or USB drive enclosure or sled that you can mount the drive into and connect it to your computer easily.
Next, take a look at the drive itself. Is it damaged in any way? Are the pins bent or broken? Make sure that the drive is in good enough condition to actually use before you try anything in the first place that may damage it even further. If the drive is too physically damaged to attempt recovery, you need professional assistance. If everything looks good and you have the equipment required to connect the drive to your system, you can try to recover the data.

Note

It is important to know if the pins are in good condition, if they aren't a docking station won't help because then the drive can't connect

Pztm021 · 29 Nov 2015

Thanks a lot axe0.. that's what I will do. Why does that happen? I didnt drop it or do anything since i last used it...

**axe0** · 29 Nov 2015

Hardware can suddenly fail, especially after years of use.
It is the reason why many replace their hardware after a few years of use, to prevent data loss and recover/back-up while they still can.

It might be difficult to do this sometimes as, as you had it, sometimes the system works perfectly on day 51 and on day 52 you can't boot. In the case of a few months your speaking of faulty, but after years of use your speaking of failing.

Pztm021 · 29 Nov 2015

Thanks a lot axe0. Youre the best :) have a nice day.