S
Success007
Guest
Hello everyone.
My pc has ever since the fall creators update continuously been getting these errors, along with the pc freezing up when the error occurs. I've been able to consistently replicate these errors and I know some of the actions where the errors occur, but very far from all of them. It happens a least the first time a program prompts for a file to open, which causes the program and the majority of the system to lock up for a good amount of time, which is extremely debilitating for the use of the pc, as the only thing I can only really do is use the multitask function and move the cursor around, trying to do anything else while this is going on only prolongs the issue and won't actually execute the attempted action until the system freed up again. Also, I'm not sure how much this is affecting the pc, but there is currently a flood of errors from the source: Windows Error Reporting - which is mainly in regards to updating.
The ESENT errors below are just a few examples, as they are variants of the ESENT error, because the first part of the number is different, and I'm also not sure what the G and second number represents, but I do know that the first is the process id.
DllHost (7508,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
svchost (7664,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
taskhostw (5800,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
SearchIndexer (9056,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
Furthermore, I've been getting these more specific ESENT errors, which might be the cause of some of the ESENT and other issues I've been facing.
svchost (3968,D,0) SRUJet: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -529.
svchost (3968,D,11) SRUJet: Unable to rollback operation #-36031 on database C:\WINDOWS\system32\SRU\SRUDB.dat. Error: -529. All future database updates will be rejected.
taskhostw (1508,R,98) WebCacheLocal: The shadow header page of file C:\Users\Brian\AppData\Local\Microsoft\Windows\WebCache\V01.chk was damaged. The primary header page (4096 bytes) was used instead.
svchost (3968,D,0) SRUJet: An attempt to write to the file "C:\WINDOWS\system32\SRU\SRUtmp.log" at offset 0 (0x0000000000000000) for 65536 (0x00010000) bytes failed after 0.000 seconds with system error 112 (0x00000070): "Der er ikke tilstrækkelig plads på disken. ". The write operation will fail with error -1808 (0xfffff8f0). If this error persists then the file may be damaged and may need to be restored from a previous backup.
svchost (3968,D,0) SRUJet: The logfile sequence in "C:\WINDOWS\system32\SRU\" has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup.
svchost (4356,D,0) SRUJet: A request to write to the file "C:\WINDOWS\system32\SRU\SRU.log" at offset 45056 (0x000000000000b000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (43 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
svchost (4356,D,0) SRUJet: A request to write to the file "C:\WINDOWS\system32\SRU\SRU.log" at offset 45056 (0x000000000000b000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
I do have a few suspicions as to what is going on, both due to having read about this on various forums as many are affected by this error, but also from trying to do some research of my own, and this issue is probably also causing other issues to happen. One of my suspicions comes from having read in the event viewer from the source "User Profile Service" that a lot of registry entries are still in use by other applications or services, where it's also stating that a lot of registry handles has been leaked, which seems a bit concerning.
I've tried a lot of troubleshooting steps, and from what I can see from others is that resetting the pc or reinstalling the OS won't fix the issue.
What can be done to fix this?
I need specific instructions to fix these issues.
More...
My pc has ever since the fall creators update continuously been getting these errors, along with the pc freezing up when the error occurs. I've been able to consistently replicate these errors and I know some of the actions where the errors occur, but very far from all of them. It happens a least the first time a program prompts for a file to open, which causes the program and the majority of the system to lock up for a good amount of time, which is extremely debilitating for the use of the pc, as the only thing I can only really do is use the multitask function and move the cursor around, trying to do anything else while this is going on only prolongs the issue and won't actually execute the attempted action until the system freed up again. Also, I'm not sure how much this is affecting the pc, but there is currently a flood of errors from the source: Windows Error Reporting - which is mainly in regards to updating.
The ESENT errors below are just a few examples, as they are variants of the ESENT error, because the first part of the number is different, and I'm also not sure what the G and second number represents, but I do know that the first is the process id.
DllHost (7508,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
svchost (7664,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
taskhostw (5800,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
SearchIndexer (9056,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
Furthermore, I've been getting these more specific ESENT errors, which might be the cause of some of the ESENT and other issues I've been facing.
svchost (3968,D,0) SRUJet: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -529.
svchost (3968,D,11) SRUJet: Unable to rollback operation #-36031 on database C:\WINDOWS\system32\SRU\SRUDB.dat. Error: -529. All future database updates will be rejected.
taskhostw (1508,R,98) WebCacheLocal: The shadow header page of file C:\Users\Brian\AppData\Local\Microsoft\Windows\WebCache\V01.chk was damaged. The primary header page (4096 bytes) was used instead.
svchost (3968,D,0) SRUJet: An attempt to write to the file "C:\WINDOWS\system32\SRU\SRUtmp.log" at offset 0 (0x0000000000000000) for 65536 (0x00010000) bytes failed after 0.000 seconds with system error 112 (0x00000070): "Der er ikke tilstrækkelig plads på disken. ". The write operation will fail with error -1808 (0xfffff8f0). If this error persists then the file may be damaged and may need to be restored from a previous backup.
svchost (3968,D,0) SRUJet: The logfile sequence in "C:\WINDOWS\system32\SRU\" has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup.
svchost (4356,D,0) SRUJet: A request to write to the file "C:\WINDOWS\system32\SRU\SRU.log" at offset 45056 (0x000000000000b000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (43 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
svchost (4356,D,0) SRUJet: A request to write to the file "C:\WINDOWS\system32\SRU\SRU.log" at offset 45056 (0x000000000000b000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
I do have a few suspicions as to what is going on, both due to having read about this on various forums as many are affected by this error, but also from trying to do some research of my own, and this issue is probably also causing other issues to happen. One of my suspicions comes from having read in the event viewer from the source "User Profile Service" that a lot of registry entries are still in use by other applications or services, where it's also stating that a lot of registry handles has been leaked, which seems a bit concerning.
I've tried a lot of troubleshooting steps, and from what I can see from others is that resetting the pc or reinstalling the OS won't fix the issue.
What can be done to fix this?
I need specific instructions to fix these issues.
More...