BSOD volmgr.sys PXE-M0F check cable connection

vpop · 15 Feb 2015

Four year old Acer Aspire One started having BSOD issues. Alternates between fine to crashing and unable to boot into windows. The file it names in the BSOD is volmgr.sys. Generally after the blue screen crash it cannot detect the hard drive and I get a PXE-M0F error saying no bootable device. I remove the laptop battery and restart until it seems to find the hard drive.

Ran memtest and it said everything was fine. Would like to be sure that something like the hard drive is the problem before I replace it.

Any help is appreciated.

Arc · 16 Feb 2015

Some important files are missing in your upload. See the Blue Screen of Death (BSOD) Posting Instructions ... take both the options. Either of these two will gather all the needed info there.

Also, take two tests.

Test the HDD using Seatools. Take both the short generic and the long generic tests.

SeaTools for DOS and Windows - How to Use

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
__________________________________________

Code:

BugCheck 24, {1904fb, fffff88007a96488, fffff88007a95ce0, fffff80002aa08c9}

Probably caused by : memory_corruption ( nt!MmCheckCachedPageStates+559 )

Followup: MachineOwner
---------

vpop · 20 Feb 2015

Thank you for your reply!

I ran memtest for 9 passes and did not get an error.

I ran short and long generic tests with seatools, and did not receive an error.

I reran the DM Log Collector and have uploaded the new zip. It looks similar to the other zip I uploaded, so if it does not help let me know.

Arc · 21 Feb 2015

There is no newer crash dumps in the zip that you uploaded, which means there is no further BSODs after 16th.
Attachment 350360
But, the crash dumps reported disc errors.

Code:

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

Are you sure that the disc checks found no error? Or there was errors which got recovered?

Anyway, let us know for any further BSOD.

vpop · 25 Feb 2015

There have been several BSODs daily since the 16th. It stops at the Blue Screen when it is copying information and will not progress or restart. I wait a few minutes then remove the battery to get the computer to restart. Otherwise it does not restart on its own.

I reran the long and short generic tests and both of them passed again. Seatools did not mention errors being recovered. How would I know if errors were recovered?

vpop · 04 Mar 2015

If it cannot write crash dumps to the disk after the BSOD is that a disk error?

Arc · 05 Mar 2015

As the crash dumps reported, it is a disc error.

vpop · 05 Mar 2015

Thank you very much Arc! Your help is appreciated. I assume a disc error means I should replace the hard drive? Is that correct?

Arc · 05 Mar 2015

If there is disc error, you must to replace the hard drive.

But this time I am lacking certainty a bit cause as you posted in post #3 ...

Code:

I ran short and long generic tests with seatools, and did not receive an error.

If you have any other disc to install windows on it as a test basis at least, it would better that you do it.