[venn]

Hi Guys,

I need some help here.

2 days ago after I closed off my laptop lid, my laptop went into hibernation mode.
After that, the laptop is having some trouble trying to wake up. I remembered I saw an error message saying something like "Windows has failed to wake up from hibernation". So I have no other choices but to restart.

Ever since then, I start to get an error.

STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF880070C25C6, 0xFFFFF880009A8B78, 0xFFFFF880009A83D0)

Here I attach a screenshot.
http://img716.images...20718083504.jpg

I can't get into Windows. Everytime I try, I will be presented with the blue screen of death.

I tried booting in safe mode but in vain. I will get stucked at Classpnp.sys
http://img259.images...20718085116.jpg

-

I am using Windows 7 64 bit, Core i7, 8GB Ram, 2GB Graphics

Thanks,
Venn.

[Advertisements]

Did you make any other changes around that time?
Update video or network driver?
If not, run chkdsk from the Recovery Console.

How to run System File Checker (SFC) or chkdsk from the Recovery Console

• Boot your Vista or Windows 7 installation DVD
• When you see "Press any key to boot from CD or DVD", press Enter
• At the "Language" screen hold the "Shift" key and press the F10 key to open a Command Window
• Run SFC or chkdsk
• For sfc, type sfc /scannow and press Enter.
• For chkdsk, type chkdsk /r and press Enter.

Let this run to completion undisturbed..

Windows 7 only:
If you don't have a install DVD, you can download a legal copy here: Download Windows 7 ISO (Official 32-bit and 64-bit Direct Download Links) « My Digital Life

Make sure you get the same version you have installed: 32 or 64 bit; Starter, Home Premium, Pro or Ultimate.

[Ztruker]

Did you make any other changes around that time?
Update video or network driver?
If not, run chkdsk from the Recovery Console.

How to run System File Checker (SFC) or chkdsk from the Recovery Console

• Boot your Vista or Windows 7 installation DVD
• When you see "Press any key to boot from CD or DVD", press Enter
• At the "Language" screen hold the "Shift" key and press the F10 key to open a Command Window
• Run SFC or chkdsk
• For sfc, type sfc /scannow and press Enter.
• For chkdsk, type chkdsk /r and press Enter.

Let this run to completion undisturbed..

Windows 7 only:
If you don't have a install DVD, you can download a legal copy here: Download Windows 7 ISO (Official 32-bit and 64-bit Direct Download Links) « My Digital Life

Make sure you get the same version you have installed: 32 or 64 bit; Starter, Home Premium, Pro or Ultimate.

[venn]

Thanks for the reply. I am heeding your advice and the outcome is yet to be seen.

So this is what I have done:
1) Boot with Windows 7 CD.

2) When I am in Windows (language selection), I triggered the command prompt by doing Shift + F10. (Good trick!)

3) I realize the drive I am currently running is X: where my usual running drive C: has turned into D: and C: has turned into Recovery.
Screenshot: http://img845.images...20718125835.jpg

4) That is not a big problem as I can change drive using simple DOS command.

5) The problem came, when I was told I can't run Chkdsk unless I dismount the drive as the volume is in used by another. All opened handles to this volume would be invalid if I force a dismount.

6) As I am tired of waiting so I force dismount it and let Chkdsk /r runs.

Here I attach a photo of what I am looking at.
http://img713.images...20718130207.jpg

- - -

Do you guys foresee any future problems?
What happens later? Do I need to mount the drive back? If yes, how?

I will update you guys my progress.

Thanks,
Venn.

[Shintaro]

Mate,

Are you able to zip the files in the c:\windows\minidump directory and upload them?
Looking at a stop code, it could mean anything.

Regards.

[Macboatmaster]

venn

Please continue with the advice from my colleague Ztruker.

In respect of the last from Shintaro the error means

STOP: 0x0000007E (0xFFFFFFFFC0000005)

indicates

The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000007E. This bug check indicates that a system thread generated an exception that the error handler did not catch.

and in your case the first parameter 05 means that a memory violation occurred.

There can be numerous causes, from a incorrect driver, to a lack of space on the hard drive.

As you cannot get a boot into windows even in Safe Mode, you will have to work in the Recovery Environment on the cmd prompt - the reason it shows X:\Sources> is because that is a drive created in ram and as you say the other drive letters are frequently changed.

That all said Ztruker will advice you.

Please complete the chkdsk and post back.

That all said and please do not think I mean that there is anything wrong in asking on more than one site, you have asked on MANY sites. In fact your post 3 on here has been incorporated into your opening post on other sites.

Please be aware that trying to work on many different sites with the same problem is not always good practice, as people assisting on one have no idea what is happening on others.

http://msdn.microsof...9(v=vs.85).aspx

[venn]

Thanks for the help.
Sorry for posting multiple replies on multiple forums as I am desperate.

-

Anyway, it seems that Chkdsk can't help fix the bad sectors I have on my hard disk.
I have no choice but to backup my files and reformat it. That's the best I can do.

[Macboatmaster]

Indeed if you have bad sectors it is time to think of a new drive.

Chkdsk has never fixed bad sectors that is a common misconception.

It attempts to retrieve the data from the bad sector and rewrite it to a good sector. It then marks the sector as bad, so that data is not written to it in future.

[Shintaro]

Venn,

Have you tried the utilities from the hard drive maker?
Maybe you can squeeze a bit more life out of the hard drive, enough to get your data off?
Or there is spinnrite: http://www.grc.com/sr/spinrite.htm

Good luck.

[venn]

Thanks for the tips + facts.

I have re-formatted my hard drive.
By doing that, will that "detox" the bad sectors and make it good again?

Or I have to get a replacement?

What is the next step to prevent further BSOD?

[Shintaro]

Venn,

Every drive has bad sectors, where it becomes a problem is when the bad sectors are increasing.

Do you know what brand your hard drive is?
The makers utility may help, but at the end of the day, as MacBoatMaster said "Indeed if you have bad sectors it is time to think of a new drive."

Generally to prevent BSOD, keep ALL drivers and applications up to date.
A couple of common BSOD are from video drivers and out of date anti-virus. There are many others of course, but keeping everything up to date will help prevent future problems.

Hope this helps.

[venn]

Yes, I am using a Dell XPS 14 laptop. According to the bios, I am having a Samsung SATA.

What makers utility are you talking about?
A utility that will attempt and repair bad sectors?

Dell comes with a PC diagnosis software and it can only check on the hardware problems but not fixing it.

[Ztruker]

If I were you, I would buy a new hard drive then do a Clean Install - Factory OEM Windows 7

chkdsk /r validates/repairs the file system but it also does a surface scan. If it could not fix or reallocate bad sectors then the drive is dying and needs to be replaced. Formatting and reinstalling will not fix the problem.

[Shintaro]

Nothing will fix the bad sectors.
Maybe, the Manufacturer's utility can be of use until you can buy a new drive. Samsung Util ISO

But again, at the end of the day, sorry, but it's time for a new drive. I understand it's a pain, but it's necessary.

[venn]

Yeap, a re-format doesn't fix my bad sectors.

I got a Dell laptop and I have done a diagnosis using the 32bit Dell Diagnosis Utility tool that comes with my laptop. It seems that my SATA has many bad sectors.
I got a feeling the SATA is dying soon. So can I just get any HDD and fix it into my laptop or do I need to make sure the HDD works with my motherboard, etc?

Any pointers in finding a HDD that works?
If you need any information about my laptop do let me know.

The link that @Shintaro posted "Samsung Util ISO" is broken.

Thanks,
Venn.

[Shintaro]

Sorry about that:.

Try this