Various errors! The Saga Continues!

[KeyboardDemon]

Ok, will try and cut a long story short.

For some time I've been having stability issues with my PC under load, this goes back to well over 6 months ago, ask any of the people I play BF4 with. lol

Error reports have been relating to NV drivers, Storage, Bad_Pool_Header, KMODE_EXCEPTION_NOT_HANDLED and System_Service_Exception.

Symptons are games will crash to desktop or the system will blue screen under load.

• Have tried reinstalling, refreshing and even pleading.
• Have swapped RAM for other RAM modules, and tried in different slots.
• Have changed the SSD.
• Tried a different GPU.
• Swapped out PSU.

Since swapping the PSU games that use to crash and blue screen are now just crashing to desktop, but still crashing.

I ran sfc /scannow in safemode and got the following error:

Windows Resource Protection found corrupt files but was unable to to fix some of them. Details are included in the CBS.Log

This is what I'm getting from the log (it's not the full log):

2015-05-16 23:53:46, Info CSI 000004af [SR] Verify complete
2015-05-16 23:53:46, Info CSI 000004b0 [SR] Verifying 100 (0x0000000000000064) components
2015-05-16 23:53:46, Info CSI 000004b1 [SR] Beginning Verify and Repair transaction
2015-05-16 23:53:46, Info CSI 000004b2 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-16 23:53:46, Info CSI 000004b3 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17807, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-16 23:53:46, Info CSI 000004b4 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-16 23:53:46, Info CSI 000004b5 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17807, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-16 23:53:47, Info CSI 000004b6 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-16 23:53:47, Info CSI 000004b7 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17807, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-16 23:53:47, Info CSI 000004b8 [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3022345~31bf3856ad364e35~amd64~~6.3.2.0.3022345-1_neutral_GDR"
2015-05-16 23:53:47, Info CSI 000004b9 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-16 23:53:47, Info CSI 000004ba [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17807, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-16 23:53:47, Info CSI 000004bb [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3022345~31bf3856ad364e35~amd64~~6.3.2.0.3022345-1_neutral_GDR"
2015-05-16 23:53:47, Info CSI 000004bc Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-16 23:53:47, Info CSI 000004bd Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-16 23:53:47, Info CSI 000004be [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
2015-05-16 23:53:47, Info CSI 000004bf Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-16 23:53:47, Info CSI 000004c0 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-16 23:53:47, Info CSI 000004c1 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted
2015-05-16 23:53:47, Info CSI 000004c2 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17807, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

I'm going to reinstall GPU drivers and go through device manager updating other drivers and I think I'm moving in the right direction but need some help working out what to do next, any help, advice, pointers or just a comforting shoulder to cry on would be greatly appreciated.

Thanks.

[MaddAussie]

Mate try running sfc in safe mode and check that the PendingDeletes and PendingRenames exist under %WinDir%\WinSxS\Temp folder.

If that doesnt work try DISM, open a command prompt as administrator and run

Dism /Online /Cleanup-Image /RestoreHealth

[KeyboardDemon]

I have both folders, the PendingDeletes folder has 778 files and the PendingRenames folder contains 8574 files.

What are these files?

Also why are there 13,190 folders called amd64_*********? I take it that has nothing to do the chip manufacturer, right?

Oh, and I've just run the Deployment Image Servicing and Management tool with the modifiers suggested, it said:

The restore operation completed successfully. The component store corruption was repaired.

The operation completed successfully.

I'm going to restart my PC and then check Event Viewer to see if it is reporting any new errors.

[KeyboardDemon]

I did get two errors on startup:

Microsoft-Windows-DeviceSetupManager/Admin - [Process ID] 520/[THREAD]5048
Microsoft-Windows-EnhancedStorage-EhStorTcgDrv [ProcessID]4/[ThreadID]8

This has reduced some of the other errors, but what (if anything) do I need to do about the ones shown here?

[Phage]

Way above my head. Beer ?

[KeyboardDemon]

Thought I would test it out, played two rounds of BF4 TDM with no issues, got a blue screen on the third round with a:

BAD_POOL_HEADER

I'm still seeing TCG errors during my startup process, also getting this:

Microsoft-Windows-DeviceSetupManager/Admin

Also had this error:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x000000000000000e, 0xffffe000952bb000, 0x99f7460024901850, 0x9bf7460024901850). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 051715-6000-01.

[MrRockliffe]

Seems you're having much luck...

I'm assuming you've updated the BIOS on your motherboard? What about going to a different firmware on it?

[gupsterg]

Way above my head. Beer ?

and a bag of crisps with mine, please .

Seems you're having much luck...

+1, sorry got no insight KeyboardDemon , but hope you sort it .

[kalniel]

Also why are there 13,190 folders called amd64_*********? I take it that has nothing to do the chip manufacturer, right?

Yes and no. When CPUs starting using 64 bit instruction sets Intel created their own set which didn't really take off because they weren't so backwards compatible. AMD in turn created their own which were a superset of the 32bit instructions, so vastly more backwards compatible. Guess which won? So now, all baseline 64 bit instruction sets for the CPU are using AMD's, which is called, you've guessed.. amd64 (since standardised to x86-64, but all the files are still called amd64). They cross-license this instruction set to Intel and Intel chips use this now.

Fixing windows is quite a task. The obvious, but slightly painful, suggestion is to back up and reinstall windows, just to rule out software.

[MrRockliffe]

I believe he's done this previously unfortunately :/

[kompukare]

I see you said you tried re-installing, but have you done so since swapping the PSU?

Because one or more of your crashes could very well have corrupted some Windows files.

My approach to random error is usually something along these lines:

1. boot of a live Linux CD/DVD/USB: this rules out most serious hardware issues but tells you nothing about specific Windows errors like gaming.
2. Find a spare HDD/SSD or partition and install a new copy of Windows on there (take great care not to wipe anything on the old drive).
   
   
   

   1. before installing anything but the most important drivers, test the stability. Yes, without all the drivers this might be tricky but the like of Intel burnTest (Linpack CPU) should work.
   2. Install the chipset and SATA drive. Repeat testing, this time add something to stress the SATA controller and maybe the audio too (if that was part of the chipset drivers, otherwise test it later).
   3. Install the graphic card driver. Use the like of Occt or a simple game to stress test it
   4. Finally if all the others were fine, try the gamin which was causing you the problem.

[abaxas]

Are you running the GTA V ready nvidia 350.xx driver?

If so, don't. Revert to the previous version.

[KeyboardDemon]

I believe he's done this previously unfortunately :/

Yes, 3 times now.

I see you said you tried re-installing, but have you done so since swapping the PSU?

Because one or more of your crashes could very well have corrupted some Windows files.

My approach to random error is usually something along these lines:

1. boot of a live Linux CD/DVD/USB: this rules out most serious hardware issues but tells you nothing about specific Windows errors like gaming.
2. Find a spare HDD/SSD or partition and install a new copy of Windows on there (take great care not to wipe anything on the old drive).
   
   
   

   1. before installing anything but the most important drivers, test the stability. Yes, without all the drivers this might be tricky but the like of Intel burnTest (Linpack CPU) should work.
   2. Install the chipset and SATA drive. Repeat testing, this time add something to stress the SATA controller and maybe the audio too (if that was part of the chipset drivers, otherwise test it later).
   3. Install the graphic card driver. Use the like of Occt or a simple game to stress test it
   4. Finally if all the others were fine, try the gamin which was causing you the problem.

Do you think re-installing the mobo chipset drivers might help? I might just give that a go before I go through your other suggestions and thanks for those.

Are you running the GTA V ready nvidia 350.xx driver?

If so, don't. Revert to the previous version.

I am on 350.12 but was also experiencing issues using 347.52 and I don't have GTA V at the moment.

[satrow]

0x19 bugcheck = device driver, could be hardware, utility, security but almost never a default Windows driver.

Follow the routine here and post the required zipped folder back here and I'll see what I can find.

[KeyboardDemon]

0x19 bugcheck = device driver, could be hardware, utility, security but almost never a default Windows driver.

Follow the routine here and post the required zipped folder back here and I'll see what I can find.

Thanks. Hopefully I'll get time to post that tonight.

[satrow]

NP KD, hope I'm awake when you post it