BSOD after Firefox update, Error c000021a

snsjets · 12 May 2017

c000021a
The verification of a knownDLL failed. system process terminated with a status of 0xc0000020 (0x0102c750 0x0000000).

Tried system repair with and without Windows 7 DVD and last known good configuration. All results in the same BSOD. Computer will not start in any Safe Mode. Startup Repair says it cannot repair automatically.
Unfortunately I cannot load(or don't know how to) the DM Log Collector because I cannot get access to the problematic computer. I used ESET SysRescue and ran several scans without success. I can, however, see the files on my C: drive using the ESET desktop utility.

History: Started having issues with computer freeze up after updating Firefox to 53.0. After the computer ran for half of the day, simply opening a new tab would completely freeze the computer. This happened on 3 computers - 1 desktop, 2 laptops. After the latest freeze up on the desktop, a press of the reset button on the tower lead to the BSOD.

Layback Bear · 12 May 2017

Please complete this needed tutorial by Brink.

Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Help Forums

Jack

**axe0** · 12 May 2017

Hi snsjets,

2 main causes in this kind of situations are the hard drive(s) and RAM.

For 1 of the tests below, HDTune, please use the bootable Win10PE from Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums to run them. This Win10PE has software preinstalled.
You could also try and use Macrium Reflect, also preinstalled, to fix boot issues if the hard drive and RAM appear fine.

Diagnostics Test

HDD TEST

Note

Please run HDTune first, in the order posted!

Run HDTune to

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

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

the health,
the error scan,
the benchmark incl. following
- transfer rate,
- access time,
- burst rate,
- cpu usage.

Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.

Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log

Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

snsjets · 16 May 2017

Hi Axe0,
Thank you for the reply.

I installed and ran Macrium's Fix Boot Problems utility - no change.
I did not run SeaTools since I boot from a SSD.
I also ran Malwarebytes that came with the Win10PE desktop - 0 threats.

I ran HD tune:
Attachment 398760

Attachment 398761

Attachment 398762

Attachment 398763

I ran chkdsk:
Attachment 398764

I tried to install and run DM log collector from the Win10PE desktop but this is what happens:
Attachment 398765

Attachment 398766

Memtest86 is 14 hours in (still going) and no errors yet:
Attachment 398767

**axe0** · 16 May 2017

Those errors with the DM Log Collector are understandable.
Besides of the errors, does the DM Log Collector finish and leave some logs?

Please do note, it is recommended to run the hard drive tests on all partitions/drives. It occurs often that not the boot drive, but a different drive is causing issues.

snsjets · 16 May 2017

I guess I didn't look for DM logs under the error windows. I will look for them next time I'm on the Win10PE desktop.

OK, I will run HD tests on the other partitions and the HDD.

snsjets · 17 May 2017

Hi Axe0,

I ran 8 passes on Memtest86:
Attachment 398806

I ran SeaTools on my HDD:
Attachment 398807

I ran chkdsk on my HDD:
Attachment 398808
Attachment 398809

I ran HDTune on my HDD:
Attachment 398810
Attachment 398811
Attachment 398812
Attachment 398820

I ran DM log collector on the Win10PE desktop (still with errors) and these are the files:
Attachment 398821

**axe0** · 18 May 2017

Run the long test for Seatools.

The rest looks good, unfortunately the uploaded logs aren't of much use since most of it is corrupted (size is 0).

Could you provide your PSU and cooler.

Has SFC been performed on the system?

snsjets · 18 May 2017

Ran SeaTools long test
Attachment 398858

PSU is Antec BP550 Plus

Cooling is provided by 3 fans - front, back, and top of case

I attempted sfc (multiple times) after booting from the Windows 7 disk and this is what comes up: There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again.

I attempted sfc from Win10PE desktop and this: Windows Resource Protection could not perform the requested operation.

**axe0** · 19 May 2017

I presume stock cooling.

Do you have any peripheral attached?