Windows 10 Error 158, 454, 161, 624 - Causes crashing

  • Thread starter Thread starter Tufty11
  • Start date Start date
T

Tufty11

Hi,


I have an issue where in a specific application, it crashes, every time this happens I get a number of different errors, all relating to storage. This inlcudes:

(disk 1 is my SSD where windows 10 is installed, disk 0 is my HDD)


158 - disk - Disk 1 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (Microsoft Support) and search for KB2983588 to resolve the issue.


454 - DeviceManagement-Enterprise-Diagnostics-Provider - MDM ConfigurationManager: Command failure status. Configuraton Source ID: ({481BDFA2-6CA2-4514-84D7-F6A4B0544EC8}), Enrollment Type: (FamilySafety), CSP Name: (AppLocker), Command Type: (Clear: first phase of Delete), Result: (./Vendor/MSFT/AppLocker/FamilySafety/FamilySafetyGroup).


161 - volmgr - Dump file creation failed due to error during dump creation.


624 - ESENT - (a few different ones for this)


1) Video.UI (12816,R,98) {AB5E7A67-B765-4AEB-8078-B031879320A2}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

2) Music.UI (11456,R,98) {07A7283B-A549-4102-8B23-0DDBD5712E65}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

3) Catalog Database (4148,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).


most of these errors happen just before the 'critical error' of rebooting or occur in clumps of 5-10 in a row


is diskpart its shows that disk 1 is not gpt and disk 0 is gpt



Does anyone know the source of the issue? or anyway to fix or stop the issue entirely so my application no longer crashed?

Continue reading...
 

Similar threads

E
Replies
0
Views
19
Edgaras Narvilas
E
R
Replies
0
Views
17
Reid Snyder
R
N
Replies
0
Views
84
NVFOX
N
U
Replies
0
Views
145
UMM607
U
Back
Top