Your computer has encountered an error and needs to restart

Not Myself · 20 Dec 2018

I just had another BSOD while I was reading a .pdf file in FoxitReader. At the bottom of the screen I found an entry for what had failed, which I had failed to see before.

I tried to write down the file name before the computer restarted, but did not get it correctly. However, as I had jotted down "mcbt.sys" I tried to search for that, and found nothing, so I searched for "mcb*.sys" to no avail, so searched for "mc*sys" which returned two entries, mcd.sys,one in \System32\Drivers, one in \WinSxs\. These appear to to be referring to same file, as they are both shown as 23KB and as having been installed on the same date (4\11\2018) and both installed at 5:34PM.

(Having again restarted the computer, I got a second BSOD today; this time, as I had disabled auto-restart for the process, I was able to confirm that the culprit is mcd.sys.)

I ran sfc /scannow a few days ago, which did not find anything, but I may have only run it once, so I am going to try running it three times to see if it finds anything. I don't know if it would find a bad driver. I shall first run DISM.exe /Online /Cleanup-image /Restorehealth, again to see if that helps.

===
I took the steps delineated above; sfc; /scanow did find anything. I just installed KB4483234, which for once worked properly without the usual problems I encounter with Windows 10 Updates. Given that I am now on Version 1803, OS Build 17134.472, what should I do next (other than using my 10-pound sledgehammer or my chain saw)?

Bree · 20 Dec 2018

Not Myself said:

tried to write down the file name before the computer restarted...

To make this easier, turn off automatic restart.

Enable or Disable BSOD Automatic Restart in Windows 10 | Tutorials

Not Myself · 20 Dec 2018

Bree said:

To make this easier, turn off automatic restart.

Enable or Disable BSOD Automatic Restart in Windows 10 | Tutorials

Thanks for the reminder; doing that was in the amazing post in this thread of the many things for me to do, one of which (which was not in the list) was to do the things in the list. BSOD auto-restart has now been deselected.

A bit later: In trying to figure out the strange behavior of the period key, I restarted the computer; part way though the log-on procedure, I again got a BSOD. This time, as I had disabled auto-restart, the process stopped, and I was able to verify that the culprit is mcd.sys.

The error handler stated that it had finished collection data, and that I could now restart. The only way I could find to do that was to turn the computer off and back on; is that normal?

Not Myself · 20 Dec 2018

"...update Intel Rapid Storage driver...".

(How very odd that a period is now appearing as two dots.)

Before I do that, I want to be certain that I understand how to do this; as is all too common, a quick on-line search returns conflicting information. I found the proper folder, but i cannot tell which of the many files there is the driver, so I cannot even check the installed version number.

I did find the installation instructions on an Intel site, but perhaps even better, I found the Intel Driver and Support Assistant, which I installed at least once quite a while ago, Should I download and run that; would that be the easiest and safest way for me to update?

krzemien · 21 Dec 2018

Yes, you can use IDSA for this task - Intel is apparently pushing for this tool to be in place first, in order to detect and match the appropriate driver for user's rigs.

However, some direct links to the latest RST driver are here:

https://downloadmirror.intel.com/284...f6flpy-x86.zip
https://downloadmirror.intel.com/284...f6flpy-x64.zip
https://downloadmirror.intel.com/28400/eng/SetupRST.exe
https://downloadmirror.intel.com/284...taneMemory.exe

Obtained via:

Intel Released new RST driver 16.8.0.1000 on 07-12-2018 with supported operating systems are windows 10 32bit , 64bit and windows server 2016 .

Not Myself · 21 Dec 2018

krzemien said:

Yes, you can use IDSA for this task - Intel is apparently pushing for this tool to be in place first, in order to detect and match the appropriate driver for user's rigs.

However, some direct links to the latest RST driver are here:

https://downloadmirror.intel.com/284...f6flpy-x86.zip
https://downloadmirror.intel.com/284...f6flpy-x64.zip
https://downloadmirror.intel.com/28400/eng/SetupRST.exe
https://downloadmirror.intel.com/284...taneMemory.exe

Obtained via:

Intel Released new RST driver 16.8.0.1000 on 07-12-2018 with supported operating systems are windows 10 32bit , 64bit and windows server 2016 .

Thank you. I found too much conflicting and/or confusing information, even from Intel. Using your succinct information, I downloaded and ran SetupRST.Exe, which even recognized that I wanted to update an existing installation. That step in fixing and updating my computer is now finished.

Not Myself · 21 Dec 2018

An interesting development.

This is what I jotted down the first time I got a BSOD: I tried to write down the file name before the computer restarted, but did not get it correctly. However, as I had jotted down "mcbt.sys...", I was not far off in trying to see where the BSOD cause was. Granted that the ensuing BSODs were in a different .sys file, I now wonder if my problem has been solved by my updating Reflect to v7.2.3957 from ...3954.

Here is why I wonder this: "If you have experienced a Windows System BSoD caused by driver mrcbt.sys when running Macrium Reflect release v7.2.3954 then please download and run the appropriate patch below to upgrade your installation to v7.2.3957"

Ztruker · 21 Dec 2018

Could well be as there were other reports of BSODs from Macrium users after an update fairly recently.

I just checked and saw that I was down level as well, at v7.2.3954. My system just completed it. Friday night backups with no problems but I went ahead and updated to v7.2.3957 anyway.

Not Myself · 28 Dec 2018

I had been waiting to declare this as solved, as I wanted to see if any further crashes might occur in the module that was not reported as being caused by the Macrium Reflect update. That there have been no such problems, I would have posted this yesterday, had it not been for the major crash at Centurylink.

Again, my thanks to all who offered assistance in the face of a BSOD problem they could not have realized was due to an external cause.

However, I do think that "BSOT" would be more appropriate. That stands for Blue Screen of Text as there is extensive text on the monitor as Windows prepares to reboot....