BSOD when updating W10 Insider Preview (installation)

Code:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  504320 file records processed.                                                         
File verification completed.
  4309 large file records processed.                                    
  0 bad file records processed.                                      

Stage 2: Examining file name linkage ...
  12586 reparse records processed.                                       
  607602 index entries processed.                                                        
Index verification completed.
  0 unindexed files scanned.                                         
  0 unindexed files recovered to lost and found.                     
  12586 reparse records processed.                                       

Stage 3: Examining security descriptors ...
Cleaning up 769 unused index entries from index $SII of file 0x9.
Cleaning up 769 unused index entries from index $SDH of file 0x9.
Cleaning up 769 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
  51642 data files processed.                                            
CHKDSK is verifying Usn Journal...
  40109712 USN bytes processed.                                                            
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  504304 files processed.                                                                
File data verification completed.

Stage 5: Looking for bad, free clusters ...
  16503314 free clusters processed.                                                        
Free space verification is complete.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

 125044261 KB total disk space.
  58262984 KB in 210240 files.
    152596 KB in 51645 indexes.
         0 KB in bad sectors.
    615425 KB in use by the system.
     65536 KB occupied by the log file.
  66013256 KB available on disk.

      4096 bytes in each allocation unit.
  31261065 total allocation units on disk.
  16503314 allocation units available on disk.

Internal Info:
00 b2 07 00 06 ff 03 00 1a 86 07 00 00 00 00 00  ................
b9 00 00 00 71 30 00 00 00 00 00 00 00 00 00 00  ....q0..........

Windows has finished checking your disk.
Please wait while your computer restarts.

Attachment 165804Attachment 165805Attachment 165806

The Samsung Magician says the SSD is in "Good" condition.

The event viewer had displayed corruption on the drive file system.
This was confirmed in the chkdsk /x /f /r results:
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

There should be no BSOD during Memtest86+ testing.
Whenever there are any new BSOD please post a new zip:
BSOD - Posting Instructions - Windows 10 Forums

Now that the disk errors have been corrected the OP needs to attempt the upgrade again. If it continues to fail then I think MS needs to be sent feedback in case it is a problem that relates to the new insider build.

philc43 said:

Now that the disk errors have been corrected the OP needs to attempt the upgrade again. If it continues to fail then I think MS needs to be sent feedback in case it is a problem that relates to the new insider build.

I did. And got BSOD again.

I don't know if it's build-related, as I've seen only few people having this issue? Also it happened to me on the latest 2 builds.

I left Memtest86+ running when I left to work this morning. Will post the new minidumps when I get back home.

It seems it managed to do only 3 passes in 11 hours using only 1 core. If I used 4/4 it got stuck.

Here are the new dumps.Attachment 165920

I would expect the memtest86+ to require around 24h for 16GB of RAM - possibly even longer. The test must run for at least 8 passes to be sure you have thoroughly tested the RAM.

New BSOD new minidumps.

Attachment 165977

For Memtest86+ version 5.01 it will display 1 core while testing and this normal.
Testing takes approximately 1 - 2 hours /GB RAM
The computer has 16 GB RAM.
There are 2 DIMM in use with 8 GB RAM in each DIMM.
Testing will take approximately 24 hours to test 16 GB RAM.
The testing needs to be made as 1 continuous test.
The testing is not done by time but by passes.
The greater the number the better the test.

All of the BSOD mini dumps when debugged displayed bugcheck C2
Bug Check 0xC2: BAD_POOL_CALLER
The BAD_POOL_CALLER bug check has a value of 0x000000C2.
This indicates that
the current thread is making a bad pool request.

For the workup of this bugcheck, RAM testing and Windows driver verifier, are suggested tools to find the cause.
Read the links below but do not turn on windows driver verifier.
We will let you know if and when to use the tool.

Download and install Everything: voidtools
It will index files on all drives.
The software can be set to start on boot or start when you need it.
In comparison to file explorer search as you type a character into search there will be instantaneous results.
The more the characters the narrower the search results.

Windows generates hidden files and folders when there are failed upgrades.
By default the Panther files may be hidden.
Everything search should be able to display them if they are available.
Search for these folders and files and for any of the files found use one drive or drop box to post share links into the thread.

C:\$windows.~BT\sources\panther
C:\windows\panther
setuperr.log
setupact.log
setupmem.dmp
setupapi/dev/log
bluebox.log
$windows.~bt\sources\rollback*.evtx
C:\$windows.~bt\sources\rollback

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

Saw a lot of setuperr/setupact files.

No setupmem.dmp, though.

Hope I got the right files.

Desktop(2)