BSOD upon exiting sleep 0X00009086 Memory Dump failed

[Platypus5]

For as long as I can remember having my Dell XPS14z (about a year) it has had a problem where it occasionally crashes going out of sleep. The rate of occurance slowly inched up as time passed until in the past few months, it went out of control. At some points, it crashed 100% of the time exiting sleep.

The computer will wake up, and then one of several things may happen. The computer screen will remain blank; The login page will resume but not register clicks; the login page will resume and register my clicking on my account but it will then freeze; etc. Occasionally the problem resolves itself after a minute, but now, it will eventually go to a blue screen of death, most recently with the error code 0x00009086. (I am not sure if this was always the error code that occured, but it has been the one that is occuring now.)

The memory dump always fails with status 0C000009C. Afterwards, the computer will remember nothing of the crash in the event viewer and simply assume that I improperly shut it down. (Edit: Yes, I did go into the system settings and set the computer to create minidump files)

I have contacted Dell multiple times about this. We have reinstalled the Bios, run Dell Fixit, used a startup option to check the hardware for errors, and reinstalled the graphics cards. Each time, the problem would go away for ~24 hours and then suddenly come back. I have additionally tried using the fsc/scannow and system repair, to no avail.

Does anyone have any experience with this sort of error? I would like to know soon, because otherwise I am slated to reformat my harddrive in late November.

 

[x BlueRobot]

The NTSTATUS Error Code of 0xC000009C (STATUS_DEVICE_DATA_ERROR) means there is bad sectors on your hard-drive.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[Platypus5]

Okay. I am clearly doing something wrong, as SeaTools just told me that my hard drive doesn't exist...

 

[x BlueRobot]

Does the hard-drive appear in the BIOS? Have you checked the SATA cables, and tried switching to different SATA ports?

 

[Platypus5]

Sorry for late reply. Yes, it does appear in the BIOS when I am booting normally. As for the cables, I don't feel comfortable opening up my laptop, and again, I don't seem to have any issues booting the computer from my harddrive.

Recently, the problem has more or less gone away following the replacement of... the trackpad. It hasn't crashed from sleep in the past few days (It did twice on the 29th, but nothing more) and I am hopeful that the problem has vanished for good this time. I have no idea why, but oh well.

 

[x BlueRobot]

Does the hard-drive appear in Crystal Disk Info? I think largely there may be a problem with the hard drive.

 

[Platypus5]

Okay. Here is what Crystal Disk has to say.

View attachment 292509

UPDATE: The problem came back in the strangest form yet. After waking it up (I am doing multiple "test sleeps" throughout the day now.) It seemed to boot and go to the login page just fine, but when I reopened my user account, I received a message saying windows explorer had to restart. I said "Okay" and then the message reappeared a moment later. So on and so on. Eventually I said screw it and forced the computer to shut down.

I restarted it and checked the event viewer, and there was an error saying "The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:." A several entries later, the event log said that these errors were successfully repaired. The computer is operating normally as of right now.

 

[x BlueRobot]

Could you please upload or post the Event Viewer log created from chkdsk - http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

 

[Platypus5]

Sorry for the late reply. As far as I can tell, the system did not automatically run a chkdsk scan after the incident. Instead, both the message about the disk corruption and the two repair messages came from the source "Ntfs."

The two repair things included the following details:

25008: Start repair on 11/05/2013 at 16:02:29:571 26084: Deleting an index entry from index 0x55000000014b09 of file 0x102000000000a32. 26084: Deleting an index entry from index 0x55000000014b09 of file 0x102000000000a32. 27094: An index entry of index 0x55000000014b09 points to unused file 0x102000000000a32. 27293: File record 0x102000000000a32 maps to "\Program Files\Common Files\mcafee\AMCore\EM\EMSystemWideDataStore.PDS". 25009: End repair on 11/05/2013 at 16:02:29:571
RepairDataLength 140
RepairData 320A000000000201BB0117000600000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

25008: Start repair on 11/05/2013 at 16:03:35:032 26084: Deleting an index entry from index 0x3000000011a88 of file 0x74a000000000014. 26084: Deleting an index entry from index 0x3000000011a88 of file 0x74a000000000014. 27094: An index entry of index 0x3000000011a88 points to unused file 0x74a000000000014. 27293: File record 0x74a000000000014 maps to "\Users\William H. La\AppData\Roaming\Dell\Dell Stage\{7309bef0-d881-4262-82dc-fef7e931029d}\tile_event.xml". 25009: End repair on 11/05/2013 at 16:03:35:032
RepairDataLength 140
RepairData 1400000000004A07BB0117000600000000000000000000000000000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000200000001000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000

I will run my own dskchk later on today.

 

[x BlueRobot]

The messages seem related to general cleanup and reorganization of the file system, please post an update after running the chkdsk command yourself.

 

[Platypus5]

I don't believe it.... It's refusing to run the chkdsk function. When I schedule one and restart, the computer acts as if it I never scheduled it.

(If I only run the clean "bad sectors" option, the thing will start, but then say that errors were found and that I need to check the other option in order to continue.)

 

[x BlueRobot]

Try running the command from Safe Mode with Command Prompt.

 

[Platypus5]

Err... how do you run chkdsk from command prompt?

 

[x BlueRobot]

It's in my first post - http://www.sevenforums.com/bsod-hel...x00009086-memory-dump-failed.html#post2582710

 

[Platypus5]

Okay, I ran it from the command prompt. After saying that I wanted to restart, I restarted.

The computer booted normally without running the disk check.

 

[x BlueRobot]

Strange, could you provide a screenshot of what happens?

 

[Platypus5]

Unfortunately, there is quite literally nothing to take a screenshot of. The only evidence there might be that I ever scheduled a disk check might be a moderate delay in the boot time. Afterwards, it doesn't even show up in the event log.

Edit: Back to the original problem, I noticed that there was a pattern about the sleep/crash cycle. If there was a large gap between each of the sleeps, the computer would usually be okay. It was only around the 4th or 5th consecutive sleep over the course of a couple days when the computer would resume crashing upon wakeup...

 

[x BlueRobot]

Sleep issues are usually related to drivers not handling or supporting certain dispatch routines and IRPs.

There still may be a problem with your hard drive in my opinion, bad sectors can indicate hard drive failure.

 

[Platypus5]

I was playing with the command console, and I found out that the dskchk is never even scheduled. It isn't that it fails to run on boot. Instead, when I checked to see if a chkdsk had been scheduled using the command chkntfs c: it made no mention of a disk check having been scheduled, even after ordering it through the console.

In regards to reformatting, I have thought about it, and I think I am happy to simply live with the computer's quirk and avoid the pain of a reformatting.

 

[x BlueRobot]

I wouldn't recommend reformatting, usually it's just a waste of time, unless Windows is severely corrupted.

Have you tried doing the Disk Check with this method?

View attachment 293899

View attachment 293900