NVMe errors

[mytech]

Hi i was looking at event manager and i noticed that i have tons of errors.

I have looked at these errors and doesn't seem to tell me wth is wrong.

my nvme drive is one a few weeks old so i shouldn't be getting errors

As you can see in Crucial Storage Executive my drive is fine.

When i click on the first error at top of image,the error only shows binary numbers.

[SpookyCitrus]

Just because crucial executive says the drive is fine it could still be having a problem. Try CrystalDiskInfo and see what that says. Is the drive your OS drive or is it a storage drive?

[DigitalGoat]

23 minutes ago, mytech said:

Hi i was looking at event manager and i noticed that i have tons of errors.

I have looked at these errors and doesn't seem to tell me wth is wrong.

my nvme drive is one a few weeks old so i shouldn't be getting errors

As you can see in Crucial Storage Executive my drive is fine.

When i click on the first error at top of image,the error only shows binary numbers.

These are not errors, they are warnings, usually hardware corrected issues, could be a mis functioning driver, an interrupt conflict, a permissions issue even a BIOS issue.

Start with one thing when troubleshooting before trying something else.

Check the reliability monitor to see if maybe this is coincides with an app crash. Use a separate disk checking utility as mentioned above, or several, they all tend to look at different areas and no two are written at the same level of competency.

Disable all non essential start up and background apps, disable/ remove all 3rd party Windows customisation utilities, the less non Windows stuff you have running and trying to access the drive the better.

[mytech]

1 hour ago, SpookyCitrus said:

Just because crucial executive says the drive is fine it could still be having a problem. Try CrystalDiskInfo and see what that says. Is the drive your OS drive or is it a storage drive?

checked with CrystalDiskInfo and kind of looks good.Yes the NVMe ssd has windows installed am using other sata ssd for storage.

1 hour ago, DigitalGoat said:

These are not errors, they are warnings, usually hardware corrected issues, could be a mis functioning driver, an interrupt conflict, a permissions issue even a BIOS issue.

Start with one thing when troubleshooting before trying something else.

Check the reliability monitor to see if maybe this is coincides with an app crash. Use a separate disk checking utility as mentioned above, or several, they all tend to look at different areas and no two are written at the same level of competency.

Disable all non essential start up and background apps, disable/ remove all 3rd party Windows customisation utilities, the less non Windows stuff you have running and trying to access the drive the better.

I have all my games on an sata ssd so am thinking it could be that as i have just noticed CrystalDiskInfo says 95% of health.

Nothing has been changed in bios.All i did was install windows on the nvme ssd, formatted the sata ssd for storage then installed my game clients.

i didn't think i had to change anything in the bios as am not running RAID.

 

I have ran 2 tests this one is NVMe drive

 

This is Sata ssd drive

[DigitalGoat]

1 hour ago, mytech said:

checked with CrystalDiskInfo and kind of looks good.Yes the NVMe ssd has windows installed am using other sata ssd for storage.

I have all my games on an sata ssd so am thinking it could be that as i have just noticed CrystalDiskInfo says 95% of health.

Nothing has been changed in bios.All i did was install windows on the nvme ssd, formatted the sata ssd for storage then installed my game clients.

i didn't think i had to change anything in the bios as am not running RAID.

 

I have ran 2 tests this one is NVMe drive

 

This is Sata ssd drive

I mentioned the BIOS as sometimes there are updates to improve compatibility with NVME protocols/ support specifically, that may not be the case for your issues, but may be worth checking.

A 95% health report is nothing to worry about, spare capacity will decrease over time, the more the drive is used and the lower the endurance rating of the NAND cells, the quicker that % will decrease, but if you notice it getting lower rapidly (say 1% every 1- 3 days, without major file operations) then that shows a possible failure on it's way.

My point about these being warnings rather than errors is because not all warnings are bad, for example a firewall may generate a warning when it blocks an incoming connection, that is not an error, the firewall did it's job and the warning was simply about the connection attempt.

So in your case it is highly probable your issue is a soft issue, maybe corrected by the hardware (doing it's job) rather than a hardware problem, it is just a case of detective work to find out what the warning relates to, why it is being generated, maybe searching for the event id number (using the log type as well) and/ or including the id numbers/ hex codes listed under details.

You could also use an app like Sysinternals Process Explorer with disk access filters to determine where the issue originates from that is causing the warning.

[mytech]

16 hours ago, DigitalGoat said:

I mentioned the BIOS as sometimes there are updates to improve compatibility with NVME protocols/ support specifically, that may not be the case for your issues, but may be worth checking.

A 95% health report is nothing to worry about, spare capacity will decrease over time, the more the drive is used and the lower the endurance rating of the NAND cells, the quicker that % will decrease, but if you notice it getting lower rapidly (say 1% every 1- 3 days, without major file operations) then that shows a possible failure on it's way.

My point about these being warnings rather than errors is because not all warnings are bad, for example a firewall may generate a warning when it blocks an incoming connection, that is not an error, the firewall did it's job and the warning was simply about the connection attempt.

So in your case it is highly probable your issue is a soft issue, maybe corrected by the hardware (doing it's job) rather than a hardware problem, it is just a case of detective work to find out what the warning relates to, why it is being generated, maybe searching for the event id number (using the log type as well) and/ or including the id numbers/ hex codes listed under details.

You could also use an app like Sysinternals Process Explorer with disk access filters to determine where the issue originates from that is causing the warning.

Thanks for the info, bios and firmware are updated so no new updates.Do you know if there is any new drivers for Microsoft Storage Spaces Controller ? as am using 2006 driver. On the image i noticed that "Search automatically for drivers" it doesn't say windows will search your computer and windows updates.I don't know if microsoft has changed that or maybe i did :S .

[DigitalGoat]

43 minutes ago, mytech said:

Thanks for the info, bios and firmware are updated so no new updates.Do you know if there is any new drivers for Microsoft Storage Spaces Controller ? as am using 2006 driver. On the image i noticed that "Search automatically for drivers" it doesn't say windows will search your computer and windows updates.I don't know if microsoft has changed that or maybe i did :S .

I believe MS and Intel have changed the date format of their drivers recently to, in theory, not conflict with newer 3rd party drivers (assuming drivers are newer if the date is later) when searching for updates. The 2006 driver is most likely the current one for Windows storage spaces as supplied by MS, the version number is more relevant when comparing drivers from both MS and Intel now.

[mytech]

5 minutes ago, DigitalGoat said:

I believe MS and Intel have changed the date format of their drivers recently to, in theory, not conflict with newer 3rd party drivers (assuming drivers are newer if the date is later) when searching for updates. The 2006 driver is most likely the current one for Windows storage spaces as supplied by MS, the version number is more relevant when comparing drivers from both MS and Intel now.

Yeah i noticed that when searching for windows storage controller, the dates are the same to what i have.

Am amd + windows.I didn't see that NVMe driver had any conflicts which is gd.

 

1 more ?.

should my sata ssd "D" drive have a page file ? as it hasn't got one but one on local C just in case that's why am getting the errors

[DigitalGoat]

3 minutes ago, mytech said:

Yeah i noticed that when searching for windows storage controller, the dates are the same to what i have.

Am amd + windows.I didn't see that NVMe driver had any conflicts which is gd.

 

1 more ?.

should my sata ssd "D" drive have a page file ? as it hasn't got one but one on local C just in case that's why am getting the errors

You can have page files on as many or as few drives as you like, at any size you like, or have none.

You may get issues with older apps expecting to see a page file on the boot drive, and Windows needs a minimum page file on C: at I think 96Mb to enable error logging/ crash dumps.

In general let the system manage the page file settings unless you have a specific need to customise the settings/ locations, also setting page file options to default can help with troubleshooting, you can always set to custom again after finding the cause of any issues.

[mytech]

Am gonna test a few games as they are on the sata ssd drive which i have just paged.

Thank you for every bit of info you have given me.

Am hoping that they main game i play atm doesn't crash if it does then i can turn off paged file off.

Thanks again.