New
#1
whea_uncorrectable_error
Hey guys,
When I installed windows update and restarted pc I cant login to windows and having this error.
Attachment 71504
I used DM Log Collecter in safe mode and log file is in the attachment.
Regards.
Hey guys,
When I installed windows update and restarted pc I cant login to windows and having this error.
Attachment 71504
I used DM Log Collecter in safe mode and log file is in the attachment.
Regards.
Unfortunately no dump is present in the zip file.
Please check in %systemroot%\minidump for a dump.
On a side note, I am a bit suspicious about your activation.
Code:+++ WER1 ++: Fault bucket , type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: AutoKMS.exe // This file is known for illegal activating Windows P2: 2.5.1.0 P3: 5329f349 P4: mscorlib P5: 4.6.1073.0 P6: 56b28422 P7: 157f P8: 12f P9: System.UnauthorizedAccess P10: <DiagReport> <LicensingData> <ToolVersion>10.0.10586.0</ToolVersion> <LicensingStatus>SL_LICENSING_STATUS_UNLICENSED</LicensingStatus> <LicensingStatusReason>0xC004F014</LicensingStatusReason> <LocalGenuineState>SL_GEN_STATE_IS_GENUINE</LocalGenuineState> <LocalGenuineResultP>1</LocalGenuineResultP> <LastOnlineGenuineResult></LastOnlineGenuineResult> <GraceTimeMinutes>0</GraceTimeMinutes> <TotalGraceDays>0</TotalGraceDays> <ValidityExpiration></ValidityExpiration> <ActivePartialProductKey>T83GX</ActivePartialProductKey> <ActiveProductKeyPid2>00331-10000-00001-AA156</ActiveProductKeyPid2> <OSVersion>10.0.10586.2.00010100.0.0.048</OSVersion> <ProductName>Windows 10 Pro</ProductName> <ProcessorArchitecture>x64</ProcessorArchitecture> <EditionId>Professional</EditionId> <BuildLab>10586.th2_release_sec.160223-1728</BuildLab> <TimeZone>Pakistan Standard Time(GMT+05:00)</TimeZone> <ActiveSkuId></ActiveSkuId> // These shouldn't be empty <ActiveSkuDescription></ActiveSkuDescription> // These shouldn't be empty <ProductUniquenessGroups></ProductUniquenessGroups> // These shouldn't be empty <ActiveProductKeyPKeyId></ActiveProductKeyPKeyId> // These shouldn't be empty <ActiveProductKeyPidEx>03612-03311-000-000001-03-1033-10586.0000-0852016</ActiveProductKeyPidEx> <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel> <ActiveVolumeCustomerPid></ActiveVolumeCustomerPid> <OfflineInstallationId></OfflineInstallationId> <DomainJoined>false</DomainJoined> <ComputerSid>S-1-5-21-2639586172-3834863156-1688966523</ComputerSid> <ProductLCID>1033</ProductLCID> <UserLCID>1033</UserLCID> <SystemLCID>1033</SystemLCID> <CodeSigning>SIGNED_INFO_PRS_SIGNED</CodeSigning> <ServiceAvailable>false</ServiceAvailable> <OemMarkerVersion></OemMarkerVersion> <OemId></OemId> <OemTableId></OemTableId> <Manufacturer>LENOVO</Manufacturer> <Model>20238</Model> <InstallDate>20160325211125.000000+300</InstallDate> </LicensingData> <HealthCheck> <Result>PASS</Result> <TamperedItems></TamperedItems> </HealthCheck> <GenuineAuthz>
%systemroot%\minidump is where you can find the file as mentioned.
In explorer enter that address in the address balk, you may get an error if the access rights aren't proper but saying yes should be enough to get access.
That means the minidump folder hasn't been created, this very rarely happens when the crash process hassn't been executed proper.
Check in the same directory, C:\Windows, for a file called memory.dmp, if this file is present try to get this file somehow onto a 3rd party uploader and share it.
Unfortunately that means the process didn't finish or the memory was thus far corrupted that creating a dump wasn't possible.
Please search "services.msc" (without quotes) and press enter, this opens a window with all the services.
Scroll down until you see the service 'Windows Error Reporting Service', make sure the startup type is manual, if the startup type is not manual a dump won't be created.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial
Please try following:
- Open an admin command prompt
- Copy/paste "sfc/scannow" (without quotes) and press enter
- When it finished reboot your system
- Open again an admin command prompt
- Enter sfc/scannow again
If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
Windows Error Reporting Service', make sure the startup type is manual = its manual
Minidump created with the following tutorial you provided.
Now its scanning sfc.
There are 2 cbs files
https://www.dropbox.com/s/zsg0rjgorg3sh52/CBS.log
Dropbox - CbsPersist_20160326100627.log
I assume the message "Windows Resource Protection found corrupt files but was unable to fix some of them" didn't show?
Please open control panel, click 'system', look at the left side of the screen and click 'Advanced system settings' which opens a pop-up.
In this pop-up, click on the tab 'Advanced', in the part 'Performance' click 'settings' which also opens a pop-up.
In the 2nd pop-up, click 'Advanced', in the part 'Virtual Memory' click 'change' which again opens a pop-up, make a screenshot of the last pop-up and post it.