FIVE BSODs this morning in less than one hour

I had five BSODs in less than one hour this morning, one while Windows was still booting up. There was no DMP file for that crash. I ran the beta collector for three of other four crashes. I'm uploading all three beta collector ZIP files here.

Before today, I had no BSODs after my earlier posting in February, once I got the advice to use Windows Defender instead of Norton security. That is, no BSODs until April 26. Then just a few BSODs through May 6, then complete stability until this morning.

I ran memtest86 recently and the RAM was clean, no errors after 8 passes.

I've also uploaded all the dmp files for for all the BSODs since my earlier posting. 17 in all, including the three today that are in the beta collector zip files.

My earlier posting: Lots of IRQ_Less... and KERNEL_SECURITY... BSODs on 2 month old build

Do I need to do a fresh install of Windows? I sure as heck hope not. If so, I'm going to wait until 1903 is available.

x509

Are you encrypting your drive/data? I see fvevol.sys as one of several reported problems and it's listed as BitLocker Drive Encryption.

New hard drive?

Many of the errors are drive related:

Code:

ffffc189`fe529d68  fffff804`4041455cUnable to load image storahci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for storahci.sys
*** ERROR: Module load completed but symbols could not be loaded for storahci.sys
 storahci+0x455c

ffffc189`fe52a878  fffff804`4102f000Unable to load image fvevol.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
 fvevol+0x2f000

ffffc189`fe52a858  fffff804`4120125fUnable to load image EPMVolFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for EPMVolFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for EPMVolFlt.sys
 EPMVolFlt+0x125f

ffffc189`fe52a9d8  fffff804`411d5669Unable to load image iorate.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iorate.sys
*** ERROR: Module load completed but symbols could not be loaded for iorate.sys
 iorate+0x5669

*** WARNING: Unable to verify timestamp for volmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for volmgr.sys
 volmgr+0x1af9

ffffc189`fe52ad68  fffff804`410d1033Unable to load image volume.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for volume.sys
*** ERROR: Module load completed but symbols could not be loaded for volume.sys

ffffc189`fe52ad88  fffff804`4112a79cUnable to load image volsnap.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for volsnap.sys
*** ERROR: Module load completed but symbols could not be loaded for volsnap.sys
 volsnap+0x4a79c

Diagnostics Test
HDD TEST

Run HDTune to

• check the health,
• scan for errors, not quick scan but full scan
• run a benchmark.

Run CrystalDiskInfo Portable and CrystalDiskMark Portable to

• Check health of drive
• Check performance of drive

You can also try the various options available with chkdsk. Also check firmware version of SSD with Samsung Magician again. Did you RMA the drive like you said you were going to do?

Guys,

Some comments and several questions.

First, I really appreciate the quick responses. I don't want to come across as defensive or anything like that. But I do need to say that I travel a lot for my job, sometimes a week or more at a time, and that puts a lot of pressure on my time when I am home. (I have about 250 thousand frequent flyer miles. ) So when my rig stopped having BSOD issues, I figured that all was good so I could deal with other issues. These recent BSODs mean that I was wrong to be complacent. OK, I get that.

And it also means that I need to read your responses carefully, follow the instructions carefully, no debates, and post results when I have them.

I'm thinking that I might be dealing with a combination of hardware and software issues. My motherboard is about six years old now, even though the Windows installation was new last December.

I did check the Samsung SSD firmware and it was up to date. Also the SSD SMART scores were very good. I also installed HD Sentinel several months ago. I did screenshots of HD Sentinel on May 4, and just checked the current error counts, two weeks later. No change. However, two of the three drives in my system do have errors, lots of them. There should not be any disk error counts, certainly not on an SSD that has very good SMART scores. So I'm thinking that maybe the built-in SATA ports on my motherboard are going bad. I know it's time to upgrade the motherboard/CPU/RAM but I honestly don't have the time for that right now.

Because of the disk issues, about two weeks ago I started to investigate SATA port adapter cards. I found several on Amazon that do support boot drives. These BSODs today mean I really need to get one of those boards.

Aside from disk issues, does anything else stand out? When I did some quick searches on the various BSOD categories, some web page said that driver issues could be a problem. However, I keep my system up to date with Windows Update. Should I get a driver management utility? Any recommendations? If one of those programs would solve my problem, spending the $25-$30 is no problem at all for me.

So that's it for now. I'm ordering one of those add-in SATA port cards tonight. Once I get that card, I'll run all the programs as instructed and post results.

x509

I don't know if the motherboard is defective or going bad, ditto the SATA ports. I find that less likely than the drives themselves being defective.

The log collector shows the 500GB SSD, a 6GB SATA and a 4GB SATA drive online when it was run.

Drives that large are difficult to fix by running chkdsk /f against as it will take a long time. Forget about running chkdsk /r, that would takes days for each of the SATA drives.

Ztruker said:

I don't know if the motherboard is defective or going bad, ditto the SATA ports. I find that less likely than the drives themselves being defective.

The log collector shows the 500GB SSD, a 6GB SATA and a 4GB SATA drive online when it was run.

Drives that large are difficult to fix by running chkdsk /f against as it will take a long time. Forget about running chkdsk /r, that would takes days for each of the SATA drives.

Rich,

Every time my system BSODs (a lot these days), I run a chkdsk /x /f /v against all the drive partitions, which are C through G. Drives always test clean.

There are 2 reasons I'm suspecting the SATA ports. First, this motherboard is an 8 RAM slot quad channel. I have four sticks of 8 GB. Recently, the B1 and C1 slots failed. I confirmed this by putting the RAM sticks from those slots into the A1 and D1 slots. (I will try putting all the RAM into slots A2 - D2 and seeing if I still have errors.)

Second, I've been running HD Sentinel, and I have a huge number of data retries on two of the three drives, like this:

Attachment 234678

I am getting a similar result for one of the HGST HDDs.

The SMART data for the SSD shows very good scores. So I'm thinking that maybe the Northbridge or Southbridge or similar chip is beginning to fail.

In a day or two, I'll get that SATA 4 port adapter card, and then I'll run all those tests.

x509

Ah, see what you mean now. $25 - $30 for the SATA card can be a cheap fix but I would go with a new motherboard which I guess the new SATA card will help to prove if it's truly defective or not.

Please let me know how you make out.

SMART results are used to predict drive failure.
We see Sea Tools results displaying failed long generic with excellent SMART scores.
And we see surface or error tests displaying bad sectors with similar SMART scores.
To properly test drives a variety of testing methods are used.

When available please post images of the test results for Sea Tool long generic and HD Tune full error scan.
(these tests can be performed overnight)

For any BSOD please upload V2 results and zipped memory dump share links.

Ztruker said:

Ah, see what you mean now. $25 - $30 for the SATA card can be a cheap fix but I would go with a new motherboard which I guess the new SATA card will help to prove if it's truly defective or not.

Please let me know how you make out.

Rich,

I will provide a full report once I can run all the various tests. Even without these recent problems, I was planning to upgrade by next year. If this motherboard is failing, then maybe I can limp along for a few months until I find the time to research my options for motherboard, CPU, RAM, and GPU. I have several family out of town trips planned between now and August.

x509