New
#11
Here Desktop
Still having problems even after a fresh windows installation. This time the computer blue screened while windows was installing updates. Could there be a problem with one of the updates or is it just that this hard drive seen its last days?
No crash dump. The Bugcheck code was 0x1A, but it failed to record the crash dump.
Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.
Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.
Also Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
As there are lots of windows update failure, I will request NoelDP to have a look.
Hmm - the 'regulated' errors in the windowsupdate.log file simply mean that the server is overloaded, so we can ignore them for the moment.
There are a couple of errors there that may indicate registry problems
Please follow the Windows Update Posting Instructions and post the requested data
Update:
Since having the crashes this morning during windows update, there have been no problems so far. Following NoelDP link to the Windows Update Posting Instructions part of the forums, I downloaded System Update Readiness Tool. I ran the tool which then restarted the computer with Windows Updates working again. This time though all the updates worked fine with no bsod. After I ran a full scan of MSE to see if that would cause a bsod like yesterday. This time there were no crashes nor anything found. That led me to try Malwarebyte full scan which had similar results.
With that working well at the moment, should I test my memory with Memtest86+? I have no problems so far browsing chrome with multiple tabs open and watching videos. I will try to game later to see it any problems surface.
Well it crashed again . This time I was trying to re-install FFXIV but I was catching a snag on the download. I was uninstalling the files that could download than crash.
The error was:
Locale ID: 1033
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8002005470
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\111613-23540-01.dmp
C:\Users\PotatoV4\AppData\Local\Temp\WER-58703-0.sysdata.xml
I would also like to note that I having problems with getting the 13.9 whql the. Since the AMD auto detect tool does not recognize OS or Card, I used the link you provided Arc. I also ran in to a problem their. I followed the instructions and click custom install to select the driver only. The problems was there was no 13.9 driver option only the hdmi audio driver. I am not sure if its a Asus thing or cannot get it since its the new R9 270x.
Here is the cbs for you NoelDP. Had to split what was inside to 2 different zips because I was having trouble uploading it as one. Would the CheckSUR produce a log after its done?
Edit: I ran sfc /scannow and it came up with an error.
Did you actually read the instruction or not?
From the SFC results
From the background CBS data...Code:2013-11-17 08:57:30, Info CSI 000002fd [SR] Repairing 1 components 2013-11-17 08:57:30, Info CSI 000002fe [SR] Beginning Verify and Repair transaction 2013-11-17 08:57:30, Info CSI 00000300 [SR] Cannot repair member file [l:30{15}]"NlsData0011.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
I'll post a fix for the file error later - please post the CheckSUR data.Code:2013-11-17 08:28:22, Info CSI 000002ed@2013/11/17:13:28:22.058 CSI Transaction @0x7f53250 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [65]"TI2.0_0:0/Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0" 2013-11-17 08:28:22, Info CBS Exec: Staging Package: Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2834140-1_neutral_LDR 2013-11-17 08:28:22, Info CBS Exec: Staging Package: Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2834140-1_neutral_LDR, PinDeployment: amd64_625642d59cbd9b78ffba236f626be496_31bf3856ad364e35_7.1.7601.22313_none_43c43e854bf640c0 2013-11-17 08:28:22, Info CBS Exec: Staging Package: Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2834140-2_neutral_GDR 2013-11-17 08:28:22, Info CBS Exec: Staging Package: Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2834140-2_neutral_GDR, PinDeployment: amd64_dd5c53d2d61e65bdc0f21e7393b667dc_31bf3856ad364e35_7.1.7601.18142_none_b02a69e93371bf1f 2013-11-17 08:28:22, Info CBS Exec: This is a PSF Package. Job has been saved and we are returning to client. 2013-11-17 08:28:22, Info CSI 000002ee@2013/11/17:13:28:22.105 CSI Transaction @0x7f53250 destroyed 2013-11-17 08:28:22, Info CBS Exec: DPX job state saved for one or more packages, aborting the staging and install of execution. 2013-11-17 08:28:22, Info CBS Perf: Stage chain complete. 2013-11-17 08:28:22, Info CBS Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED] 2013-11-17 08:28:22, Error CBS Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
I am uploading a batch images from my updates history since no errors are shown on the windows update screen. A common occurrence I notice that the batch of failed updates I revived from November 15, 2013 had an error detail of Code80073712 and from November 16, 2013 a batch had an error detail of 80070002. The November 16 batch code switched to code80070003 at "Security Updates for Windows 7 64x based systems (KB2631813).