progressive and recurring BSOD errors (volmgrx, fvevol, msrpc).sys

[Jinian]

And so after 3 years of using my office computer full-time, bsod errors have finally begun to show up from rarely, to moderately and as of today, on a daily basis.

These bsod are more likely to happen when I am pushing my computer resources to the max like when running several x64 applications at once and using up almost all my 16gb of ram, or just the opposite, I am inactive with the use of my computer by not touching the keyboard or mouse at all for a couple of minutes and then the bsod occurs.

I often get stop 07A and stop 0F4 bsod errors caused by usually one of these three(volmgrx, fvevol, msrpc).sys

I am suspecting it probably is a hardware problem, like my harddrive or memory chips are starting to deteriorate. or there is a problem with partmgr.sys a file that manages your hd partitions

Things I have done to resolve it so far but are not working:
1) turn off paging file or changing it.
2) using windows update
3) unplugging my external harddrive
4) using system file checker(sfc /scannow) - it found iassdo.dll.mui as corrupt but could not fix it
5) disk defragmenting and memory diagnostics(found no errors)

- I am now desperate and asking you experts for advice as my last resort, otherwise I will either have to reinstall windows again or replace my hard drive and/or memory sticks.

Uploaded are my BSOD errors, log in my event viewer, my CBS.log and sfc details generated by system file checker, and the minidump generated by your own recommended programs DM log collector and SF_Diagnostic tool.

Hope that is a complete diagnostic submission for your tech support.
Details of my cpu specs are listed in my profile.

Thanks and hope you could help me out.

 

[Thedoctor44]

You are having a lot of errors.
It looks like a failing disk if you ask me.
It's worth giving Memtest86 a shot.

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Post back the results.

The Chkimg command has found this.

[COLOR="Red"]3687 errors : !Ntfs (fffff8800132a001-fffff8800132afff)[/COLOR]

 

[Jinian]

Ok here is what I have done so far, I ran a memtest just like you mentioned, and the results came in positive. no problem with the memory. (results attached below)

Next I ran a disk check, and the results were also good(results attached). NO errors or bad sectors, however when I ran the sfc /scannow afterwards it still gave me the same "corrupted files were found but could not be repaired" message.

Lastly, I installed and ran SEAgate for windows, and I am having a problem with starting it and even getting into its menu window. Once I run the program and it starts scanning the drives before anything else, and next thing you know it hangs my computer. I know this since I left it running the whole night through. So I am now trying the seagate for dos option,

Because of the failed seagate operation for windows, I tried seatools for DOS via CD bootup instead, my SATA configuration is AHCI, however changing to ATA option is not available in my BIOS. Only IDE and RAID. Which one do I choose? My motherboard is ASUS Sabretooth z77, my windows hard drive is an intel ssd and my partition data hard drive is SATA seagate.

I have tried changing my SATA operation to IDE as well and it did not work. Seagate for DOS still doesn't read any hardrive present( see attached)

I also tried SEAgate for DOS bootup via cd on a friend's computer, and it read both his hardrives just fine and his motherboard is more dated. wondering why it doesn't on mine?

I cannot continue on with any further testing, please help.


Thanks

 

[Thedoctor44]

First of all you must run Memtest86 for at least 8 passes.

You choose IDE in the BIOS, it says in the tutorial.

 

[Jinian]

Thanks for your reply, I did test it under IDE and my hard drive still wasn't read by Seagate for DOS. I will try and run memtest 7 more times, but I doubt anything is wrong with the memory.

 

[Thedoctor44]

Have you set up RAID?
SeaTools will not support RAID.

 

[Jinian]

No I do not have RAID set up, but it is available option under my BIOS SATA operation together with IDE and AHCI.

I only have two drives inside my cpu in separate partitions. one intel ssd and one seagate sata drive.

 

[Arc]

Jinian, your Primary disc is an Intel SSD. Intel 330 Series 120GB I think.

Make it sure that the SSD is running with the latest firmware. If not, update it.
How to Upgrade Intel SSD Firmware | StorageReview.com - Storage Reviews

Seatools for DOS is not identifying the HDD despite of the ATA/IDE mode is selected; that is odd. But I am thinking something else. Can you run Data Lifeguard Diagnostic for Windows on the "My Passport USB disc"?

And, does it BSOD even when the "My Passport" is not attached?

 

[Jinian]

I have done another memtest, results came back just fine with another 2 passes. I've done 5 so far, i doubt doing anymore will show any difference

I have installed the latest intel ssd toolbox firmware and even ran a quick diagnostic scan using it. My intel ssd came back with positive results, and its smart details showed no errors.

I also used WD data lifeguard diagnostic on my external hard drive and results are a bit confusing(see attached image). One one hand the quick scan results turned out a "pass", and initial smart status are positive, but for some reason clicking the check icon under smart status, produces an x mark and the smart details show errors. I don't know if this is just a bug in the program or something.

Yes, i still get the BSOD even when the WD external hard drive is plugged out.

SEAgate tools for dos still doesn't read both of my hard drives using IDE,
i don't have RAID setup, but my WD external harddrive functions like a RAID system to my 900 gb SATA drive through an autoback program syncing the two.

 

[Jinian]

on a side note, I did not have my external hard drive plugged when i was booting SEAtools for dos and changing my BIOS sata config

 

[Arc]

I am not thinking about the seatools, despite of it being odd. Because, Seatools is not for the SSD, the SeaGate HDD is not any suspect (at least till now), and the suspect, the external HDD is a WD; we checked it with a different appropriate program.

It is good that you updated the SSD firmware.

And I think you should take a care to the My Passport disc. Either full format it to see if it can solve the issue; or retire it.

Let us know for any further BSOD.

 

[Jinian]

I don't know if what you said solves my BSOD problem? as mentioned, even when I unplug my external WD hard drive, I still keep getting BSOD errors. That definitely proves that is not the culprit.

Running SEAgate tools for windows doesn't even get me to the part where the menu shows up. It hangs my computer just when it is about to scan for drives.

Please review my previous posts and attached documents/images for my results.

 

[Arc]

Reviewed.

I suggested to test the MyPassport knowing that it will not give a pass result, at least. And the end result supports that view:
View attachment 316497

You apply the SATA cables on different SATA ports on the motherboard, and try seatools for windows again?
BTW, SSDs are not subject to test with this tool.

And if you get any more BSOD after applying the latest SSD firmware, post it following the Blue Screen of Death (BSOD) Posting Instructions. Post the data in this thread, in any of your subsequent post.

 

[Jinian]

Thanks. But i currently do not know how to switch SATA cables to a different SATA port. Is there any harm in doing so? Will I need to reconfigure windows or install any software? Sorry, I'm just a layman, I don't know much about tech support.

I suspected that would be the reason why seagate tools for DOS wasn't working, was because maybe it simply wasn't detecting the port that my hard drives are on.

On the other hand if the seagate tools for DOS is not for my main intel ssd drive that has windows in it, then what is the point of testing? If anything, I think the ssd drive may be the main reason bsods are occuring. I don't have windows or any important driver installed in my SATA 900 GB drive.

 

[Arc]

Thanks. But i currently do not know how to switch SATA cables to a different SATA port. Is there any harm in doing so? Will I need to reconfigure windows or install any software? Sorry, I'm just a layman, I don't know much about tech support.

Power off the computer. Open the case. Open the sata cables from the motherboard. Apply those in other unused ports. No reconfiguration or no installation of software is needed.

If it could do any harm, I would never have suggested it to you.

On the other hand if the seagate tools for DOS is not for my main intel ssd drive that has windows in it, then what is the point of testing?

That is why I was always reluctant to pay any attention on it. Running this test is not very required for you. Specially when the Seagate HDD is not a suspect at all.

Let us know about any further BSOD after applying the latest SSD firmware.

 

[Jinian]

Thanks, I'll try opening the case and switching SATA ports. But since my intel SSD does not need to be scanned by seagate tools for DOS, can I leave at least that harddrive in the same port and only switch my 900 gb SATA drive?

 

[Arc]

Better you leave the plan to scan with seatools till any further 0xF4 BSOD appears.

You also feel that it is not very necessary for you.

 

[Jinian]

alright thanks I will. But in the event I do need to scan, can I leave the intel SSD hardrive in its port as is and just change my SATA one?

I have the latest intel SSD toolbox, and its firmware that has to be the latest is what you are talking about, right? Currently it is v3.2.1, the "update" button is phased out since it is probably already at its latest.

 

[Arc]

If you scan using seatools, change the ports to get it recognised. Then test the HDD only, not the SSD.

 

[Jinian]

Although I have had no BSODs since you helped me,( particularly i think updating the ssd toolbox may have something to do with it) Today i have received it again but of a different .sys problem.

This time I get a partmgr.sys , which is A filter driver that sits on top of the disk driver. All disk driver requests pass through the partition manager driver. This driver creates partition devices and notifies the volume managers of partition arrivals and removals. Exposes IOCTLs that return information about partitions to other components, and allow partition configuration.

I have attached my new sfc /scannow log and as usual it found errors it could not fix.
Also uploaded it the updated DM log

Please advise me what to do next but would it make a difference to go through and manually replacing the dll files that showed up in the log with the copy from my windows 7 installation disc or from a friend's BSOD free computer or try using sfc /scannow at BOOT UP?

Here are the links that explain this in better detail,

http://www.sevenforums.com/tutorials/42776-extract-files-windows-7-installation-dvd.html

Use the System File Checker tool to repair missing or corrupted system files

Or otherwise in a desperate attempt,
Use the SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put

tags around the log to break up the text.