-
Various errors! The Saga Continues!
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:
Quote:
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):
Quote:
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.
-
Re: Various errors! The Saga Continues!
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
-
Re: Various errors! The Saga Continues!
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:
Quote:
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.
-
Re: Various errors! The Saga Continues!
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?
-
Re: Various errors! The Saga Continues!
Way above my head. Beer ?
-
Re: Various errors! The Saga Continues!
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:
I'm still seeing TCG errors during my startup process, also getting this:
Quote:
Microsoft-Windows-DeviceSetupManager/Admin
Also had this error:
Quote:
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.
-
Re: Various errors! The Saga Continues!
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?
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
Phage
Way above my head. Beer ?
and a bag of crisps with mine, please :p .
Quote:
Originally Posted by
MrRockliffe
Seems you're having much luck...
+1, sorry got no insight KeyboardDemon , but hope you sort it :) .
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
KeyboardDemon
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.
-
Re: Various errors! The Saga Continues!
I believe he's done this previously unfortunately :/
-
Re: Various errors! The Saga Continues!
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:
- 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.
- 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).
- 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.
- 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).
- Install the graphic card driver. Use the like of Occt or a simple game to stress test it
- Finally if all the others were fine, try the gamin which was causing you the problem.
-
Re: Various errors! The Saga Continues!
Are you running the GTA V ready nvidia 350.xx driver?
If so, don't. Revert to the previous version.
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
MrRockliffe
I believe he's done this previously unfortunately :/
Yes, 3 times now.
Quote:
Originally Posted by
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:
- 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.
- 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).
- 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.
- 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).
- Install the graphic card driver. Use the like of Occt or a simple game to stress test it
- 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.
Quote:
Originally Posted by
abaxas
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.
-
Re: Various errors! The Saga Continues!
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.
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
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.
Thanks. Hopefully I'll get time to post that tonight.
-
Re: Various errors! The Saga Continues!
NP KD, hope I'm awake when you post it :D
-
Re: Various errors! The Saga Continues!
@satrow: I have PM'd you some links with the requested reports, let me know if you got them ok.
I was looking through the PerfMon report, there are a couple of things that might be pointing towards a solution or they might be red herrings, first there was this:
Quote:
tv_ConfigMgrErr43
Cause: A device has a configuration problem that prevents it from working properly.
Details: The device, Intel(R) Management Engine Interface , is reporting "tv_ConfigMgrErr43". This device will not be available until the issue is resolved. The Plug and Play ID for this device is PCI\VEN_8086-DEV_1E3A-SUBSYS_84CA1043-REV_04\3-11583659-0-B0.
Then in the Basic System Checks under Hardware Device and Driver Checks I got a red light which means it Failed the Survey of Windows Management Infrastructure supported devices and when I drill down into that section everything listed looks like it has failed.
The report is massive, it makes War and Peace look like light reading, it even makes War and Peace look interesting, lol.
*** edit *** I just drilled down into my Device Manager and found an exclamation mark that I hadn't seen before and guess what, it was for the Intel(R) Management Engine Interface device, so I right clicked it and updated the driver using the Option to "Let me pick from a list of device drivers on my computer".
*** edit 2 ***
After updating the driver I just ran another report and no longer have any failed hardware, about to test now. Fingers crossed.
But thanks all, and particularly satrow as, unless I'm being a bit premature, I think your advice has pointed me in the right direction, I'll post how well testing went soon.
-
Re: Various errors! The Saga Continues!
Ok. I successfully managed to play two full rounds of BF4 with no crashes or issues, hooray and then got a BSOD with a SYSTEM_SERVICE_EXCEPTION whilst watching a YouTube video.
So I don't know why, but it's still not fixed!
I think I need to go to bed.
-
Re: Various errors! The Saga Continues!
Ha - War and Peace - lightweight :D
Well done on sorting that Intel/WMI bug, MSInfo32 reported it as being a Problem Device: "Intel(R) Management Engine Interface PCI\VEN_8086&DEV_1E3A&SUBSYS_84CA1043&REV_04\3&11583659&0&B0 This device is working properly." I didn't know whether to laugh or cry - first time in reading hundreds of those reports that I've seen anything as contradictory as that!
Ok, amuse bouche over, let's step up to the bigger plates: Bugchecks appear to be GFX/DirectX -related, with a hint of networking.
Code:
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Debug session time: Sat May 16 11:40:43.506 2015 (UTC + 1:00)
System Uptime: 2 days 4:26:25.804
BugCheck 1E, {ffffffffc0000005, fffff8019102b316, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!SMKM_STORE_MGR<SM_TRAITS>::SmFeAddInitiate+16a )
BUGCHECK_STR: 0x1E_c0000005_R
PROCESS_NAME: chrome.exe.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Debug session time: Sun May 17 23:53:21.699 2015 (UTC + 1:00)
System Uptime: 0 days 1:17:23.392
BugCheck 3B, {c0000005, fffff80021afc881, ffffd00023224cf0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeTerminateThread+23d )
BUGCHECK_STR: 0x3B
PROCESS_NAME: bf4.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
Debug session time: Sat May 9 23:05:44.223 2015 (UTC + 1:00)
System Uptime: 0 days 5:37:16.924
BugCheck 1000007E, {ffffffffc0000005, fffff80094349535, ffffd000204cba78, ffffd000204cb280}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+149535 )
BUGCHECK_STR: AV
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Debug session time: Sun May 17 21:58:52.527 2015 (UTC + 1:00)
System Uptime: 0 days 0:35:46.221
BugCheck 19, {d, ffffe000ead47000, ce7c29b53c348ef8, cc7c29b53c348ef8}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+e9e )
BUGCHECK_STR: 0x19_d
PROCESS_NAME: audiodg.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Debug session time: Sun May 17 09:26:09.626 2015 (UTC + 1:00)
System Uptime: 0 days 0:16:18.318
BugCheck 3B, {c0000005, fffff80315bdbf6a, ffffd0002279cd30, 0}
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+0 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: NvBackend.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Debug session time: Tue May 12 23:02:44.923 2015 (UTC + 1:00)
System Uptime: 0 days 5:58:43.619
BugCheck 1E, {ffffffffc0000005, fffff801dcc06d7b, 0, ffffffffffffffff}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+53b )
BUGCHECK_STR: 0x1E_c0000005_R
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Debug session time: Sun May 10 01:31:05.328 2015 (UTC + 1:00)
System Uptime: 0 days 1:09:11.025
BugCheck 19, {d, ffffe0018150f000, 4a541062b58a226b, 48541062b58a226b}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+2fb )
BUGCHECK_STR: 0x19_d
PROCESS_NAME: bf4.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Debug session time: Sun May 17 13:22:35.340 2015 (UTC + 1:00)
System Uptime: 0 days 1:01:50.030
BugCheck 19, {e, ffffe000952bb000, 99f7460024901850, 9bf7460024901850}
Probably caused by : afd.sys ( afd!AfdPollGetInfo+21 )
BUGCHECK_STR: 0x19_e
PROCESS_NAME: bf4.exe
To try to reduce interference on the GFX side, I suggest you reduce the current nVidia gfx install to the bare minimum, what we want is clean and simple during testing. (A drivers only install might be best to begin with, remove all then follow the procedure here: http://www.sysnative.com/forums/wind...procedure.html)
There are some drivers that aren't needed, might be a source of interference or relatively old:
IntelRST, only needed for RAID or SSD -caching, not needed for JBOD, uninstall it.
Corsair headset and Roccat Kova+, uninstall their software, uninstall the both from Device Manager, including removal of drivers. You should be able (I hope) to use them as generic devices, if not, try to get hold of basic mouse/'phones to use during testing.
Once you've done that, enable Driver Verifier (http://www.sysnative.com/forums/bsod...87.html#post87 study it carefully, it's designed to crash when it detects a bad driver - but it can prevent a normal startup - workaround provided) and then use the computer as normal, it will feel laggy with DV enabled; once you have got a couple of new crash dumps, upload/attach them for analysis; if DV doesn't flush/crash anything withing 24-48 hours, turn it off again.
EDIT: for the SFC errors in the OP, try SFCFix or follow the full procedure here (later?): http://www.sysnative.com/forums/wind...html#post35484
-
Re: Various errors! The Saga Continues!
Thanks Satrow. It looks like I'm moving in the right direction, mostly with help from you, I'll try as much of that as I can when I get home from work tonight. With larger files I'll upload and PM the links as before if that suits you.
-
Re: Various errors! The Saga Continues!
You're doing fine, KD :thumbsup:
Take your time, you'll get a better understanding that way, ask if you're unsure of anything and PMing links to your uploads is OK by me!
-
Re: Various errors! The Saga Continues!
My main issue as a PC Troubleshooting 'n00b' is that I know what tools are available but I don't have the knowledge or disciplined approach to know how or when to use them. That's changing now. Before my general approach was to get an error, put up with it till I can't put up with it anymore and then reinstall. But lately I actually want to find out what's causing the issues and how I can use the tools to put it right. Strangely, I am actually quite excited about having these issues because I have been able to learn some new stuff as a result. Your help and the suggestion from MaddAussie to use DISM have taken me a lot closer to getting my PC fixed, and this thread is keeping a record for documentation purposes.
-
Re: Various errors! The Saga Continues!
Don't look to me for ideas on a disciplined approach to anything, I'm more inclined to be intuitive - if the description includes something I've come across previously, I go there first.
I'd just reached the top of a local ridge ~10 years ago when I got a text 'Help, PC's slow to boot, slow to do anything' or similar, I replied 'Google pio node10' and a short time later got a very grateful response.
I do work off the top of my head most of the time and I'm inclined to forget little bits of info that might later prove to have been important - so it's best (and easier for me) if you try to follow what we're trying to do and why ;)
-
Re: Various errors! The Saga Continues!
Maybe disciplined is not the word I was reaching for, what I wanted to say was methodical.
My typical approach has been guess at something and try and fix that, what we have been doing here is look at the information available to see what issues need to be addressed. What I've got from this is a little bit more on how to use that information constructively and that's exciting me (I know that sounds sad!) what I want to learn now is how to read through that PerfMon report to establish that the issues might GFX/DX, networking or other drivers etc...
I'm happy with my small victories like when I spotted the issues with my Intel drivers that are being reported as both healthy and not working and fixed the not working part. lol But that wasn't all me, I had a gentle nudge to point me in the right direction.
-
Re: Various errors! The Saga Continues!
Yes, always try to get some details from logs, reliability monitor and all the other tools within Windows first - and/or build up a good description of what was happening at the time of the problem - anything really to get a feel for which set of components are most likely to be playing a part. It's usually only later that you might need a few specific external tools to help drill down further.
I hate trying to read PerfMon reports, they never seem to reveal the exact details that I need to understand what was happening on the machine during the test; it really needs to be read on the machine it was done on, in the same session with the same software running for best results imo. Gimme an MSinfo32, an Autoruns.arn and a few crash dumps, along with a good description of what was happening and I can (usually) go a long way on that.
Any progress, anything new learned is great, worthy of excitement; what we strive to do early on is to clear the stage ready for the entrance of the real villain of the piece. Sometimes it's only then that the real work begins...
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
KeyboardDemon
Ok. I successfully managed to play two full rounds of BF4 with no crashes or issues, hooray and then got a BSOD with a SYSTEM_SERVICE_EXCEPTION whilst watching a YouTube video.
So I don't know why, but it's still not fixed!
I think I need to go to bed.
Those errors have always been graphics card/driver related when I have seen them....Even to the point where certain flash sites were causing them to happen in browsers......which seems odd as most (if not all) of those driver bugs were fixed a while ago and many people are using Youtube in HTML5 now anyway.
-
Re: Various errors! The Saga Continues!
@satrow: I have done the following things in the following order.
- Removed Intel RST and Corsair Headset with no issues
- Went into Device manager and found I had about 9 HID devices relating to my Kova [+] mouse (according to the properties) I tried removing them but they re-spawned after a restart so I removed the Kova [+] (my logitech has a broken button so I'm trying to get it RMA'd as if I didn't have enough issues)
- Replaced the Kova [+] with a Logitech V220 laptop mouse so I could uninstall the Roccat PNP drivers
- Removed nVidia Drivers and then installed driver only following instructions in the link provided
- Set a restore point in case I need to rollback
- Before running the driver verifier I used bcdeit /set bootmenupolicy legacy so I can use F8 to get into safemode just in case
- Ran driver verifier following instructions
- Got a System_Service_Exception BSOD during restart so have uploaded minidump which should be in your PM soon
I think verifier is still running so will try and do some typical stuff over the course of tomorrow morning and after work, I might leave it a little longer than the suggested 24 hours.
-
Re: Various errors! The Saga Continues!
As per PM reply, no new files in the linked collection, the crash might have happened too early in the boot process to have been recorded, or perhaps you made a slip with the link or file attached?
You're making good progress :) The next dump should furnish me with details on which 'suspect' drivers are left loading, if it's also Verified and indicates a 3rd party driver, we might have this cracked.
Keep working/gaming as normal, try to remember and describe what other User Mode (stuff you started) processes were also active in the background when a crash happens again. I'm wondering whether there's a program common to all crashes (Chrome?) that could be playing a part.
A 0x3B crash, System_Service_Exception, we've had 2x before, a quick breakdown on the dumps and what might have triggered them:
Code:
3x 0x19: Running: not recorded, bf4 (dxgmms1.sys image corrupt), bf4 (win32k image corrupt).
Usual causes: Device driver.
http://www.carrona.org/bsodindx.html#0x00000019
2x 0x3B: Running: bf4, NvBackend.
Usual causes: System service, Device driver, graphics driver, ?memory
http://www.carrona.org/bsodindx.html#0x0000003B
2x 0x1E: Running: Chrome, System.
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.
http://www.carrona.org/bsodindx.html#0x0000001E
1x 0x7E: Running: System (nvlddmkm.sys image corrupt).
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.
http://www.carrona.org/bsodindx.html#0x0000007E
Running: = the Process that was active at the time of the crash, not recorded might indicate the CPU was switching between Cores/Processes when the error occurred. Note that they all have a heavy bias towards GFX involvement.
Image corrupt: = the file (drivers here) held in working memory wasn't the same as that loaded from disk, 'something', maybe a 3rd party driver, had written or modified some or all of the data.
Usual causes: = set out in order of probability based on studies over a number of years of thousands of cases where causes for a BSOD crash were proven. As you can see, Driver is the only common factor, for 1 type listed, it's the only proven cause.
Yup, the above only illustrates what you've suspected for some time, now we need to pinpoint a driver, or we have to suspect hardware. Hardware trumps software.
-
Re: Various errors! The Saga Continues!
Ok, dump collection was successful this time. Bottom line, tl:dr keep on with DV for a day or so, if no verified dumps by then, we should turn off DV and, I think, move on to changing driver versions.
The dump shows no sign of any drivers that were removed, here's the remaining 3rd party driver list, no need to do anything with these yet/info only:Basic Windbg details of the latest dump:
Code:
Debug session time: Tue May 19 23:34:32.402 2015 (UTC + 1:00)
Loading Dump File [C:\SysnativeBSODApps_2_0_0_0\051915-7234-01.dmp]
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
System Uptime: 0 days 0:16:00.093
BugCheck 3B, {c0000005, fffff802bbca3881, ffffd00148d05ee0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeTerminateThread+23d )
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff802`bbca3881 ffffd001`48d05ee0 00000000`00000000
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: 0x3B_nt!KeTerminateThread
MaxSpeed: 3500
CurrentSpeed: 3500
BiosVersion = 2104
BiosReleaseDate = 08/13/2013
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MS says:
Quote:
Cause
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
If it's any consolation/encouragement for you, the only 0x3B with the same trigger as this one I could find as [Solved] (http://www.eightforums.com/bsod-cras...s-backups.html) was apparently cured by a reinstall - but - that was claimed as fixed after only ~3 days of the fresh install.
-
Re: Various errors! The Saga Continues!
Right a mini update, I spent a couple of hours running Adventure Capitali$t (a Steam game) as it was a game that I could leave running without having to sit by my PC. Anyway the game ran ok for a short time but then started shutting down unexpectedly, I re-tried the game and the crashes persisted, I think I must have got it to crash about 4 times.
I decided I would look at the driver verifier status to see how things were going and given that previous errors have suggested paging issues I was looking at drivers that were reporting high levels of paging activity, am I looking for the right things with that?
This is what I found:
Quote:
Name: ndis.sys, Loads: 1, unloads: 0
CurrentPagedPoolAllocations: 59
CurrentNonPagedPoolAllocations: 1419
PeakPagedPoolAllocations: 61
PeakNonPagedPoolAllocations: 1446
PagedPoolUsageInBytes: 4538
NonPagedPoolUsageInBytes: 573869
PeakPagedPoolUsageInBytes: 5036
NonPeakPagedPoolUsageInBytes: 592685
Quote:
Name: nvhda64v.sys, Loads: 1, unloads: 0
CurrentPagedPoolAllocations: 16
CurrentNonPagedPoolAllocations: 42
PeakPagedPoolAllocations: 17
PeakNonPagedPoolAllocations: 42
PagedPoolUsageInBytes: 10048
NonPagedPoolUsageInBytes: 26626
PeakPagedPoolUsageInBytes: 10068
NonPeakPagedPoolUsageInBytes: 26626
Quote:
Name: rtkhd64 , Loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 706
PeakPagedPoolAllocations: 2
PeakNonPagedPoolAllocations: 708
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 217880
PeakPagedPoolUsageInBytes: 650096
NonPeakPagedPoolUsageInBytes: 218216
Quote:
Name: dump_storahci.sys, Loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
NonPeakPagedPoolUsageInBytes: 0
Quote:
Name: dumpdumpfve, Loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 16400
PeakPagedPoolUsageInBytes: 0
NonPeakPagedPoolUsageInBytes: 16400
Quote:
Name: nvlddmkm.sys, Loads: 1, unloads: 0
CurrentPagedPoolAllocations: 186
CurrentNonPagedPoolAllocations: 16599
PeakPagedPoolAllocations: 210
PeakNonPagedPoolAllocations: 22255
PagedPoolUsageInBytes: 966852
NonPagedPoolUsageInBytes: 12539743
PeakPagedPoolUsageInBytes: 1448276
NonPeakPagedPoolUsageInBytes: 14120579
The other drivers just showed zeroes throughout except in loads and unloads where they were showing 1 load and 0 unloads.
Does any of that mean anything?
Are we going in the right direction?
-
Re: Various errors! The Saga Continues!
nvlddmkm.sys is certainly showing a lot of activity but I've no clue if that's normal for the type of load it was under or not.
Can you check the entries in Reliability Monitor? It might give hints that are hard to track down elsewhere. Control Panel\System and Security\Action Center\Reliability Monitor
-
Re: Various errors! The Saga Continues!
Ok. I'm out at the moment but will check and post back later tonight. Thanks.
-
Re: Various errors! The Saga Continues!
I got home much later than expected, hopefully I'll get this done very soon.
-
Re: Various errors! The Saga Continues!
There were a few recent entries:
First this one:
Quote:
Description
The previous system shutdown at 1:41:07 AM on 5/21/2015 was unexpected.
I think that was from the time when Chrome crashed to BSOD whilst watching a Youtube video.
Quote:
Description
Faulting Application Path: C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17709_none_fa7932f59afc2e40\TiWorker.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: TiWorker.exe
Application Version: 6.3.9600.17477
Application Timestamp: 5452bcc4
Fault Module Name: msdelta.dll
Fault Module Version: 6.3.9600.17475
Fault Module Timestamp: 5450367c
Exception Code: c0000005
Exception Offset: 00000000000404c1
OS Version: 6.3.9600.2.0.0.256.103
Locale ID: 2057
Additional Information 1: f2e9
Additional Information 2: f2e969eb9fa9bb042728cc5a77f592e6
Additional Information 3: 7fdc
Additional Information 4: 7fdc736ea95ff608d27b47136c243c3d
Extra information about the problem
Bucket ID: c9e3fd70f357221a9eade47ea6e4802f (85990479358)
This one is labelled as Windows Modules Installer Worker.
Quote:
Description
Windows Installer installed the product. Product Name: Microsoft Visual C++ 2005 Redistributable. Product Version: 8.0.59193. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
Thought I would install Witcher (the first game) and this error came up during installation of Microsoft Visual C++ 2005 Redistributable, but that might just be due to have a more recent version already installed. I haven't had a chance to see if the game runs, I have to get ready for work so don't have much time for that right now.
After checking in my Device Manager last night I spotted that the Intel Management Engine Interface had a yellow exclamation mark next to it, so could this either mean that a persistent issue is corrupting this driver or that this driver could be the root cause of the other issues? Or is it still too early to tell?
-
Re: Various errors! The Saga Continues!
Most of the issues seem relatively 'normal' and I don't think they'd cause, or be implicated in, any of the main problems you're facing.
The Intel Management Engine Interface is what I'd assumed to be the cause of that contrary 'error' in MSInfo32 and the PerfMon report, perhaps it's time to run both of them again and see if there is any relationship?
If there's something wrong with the base 'board/chipset or drivers, it might well be affecting the GFX in some way.
-
Re: Various errors! The Saga Continues!
I have had an idea, now this is more guess work than anything more intelligent or intuitive but here's my idea following my uneducated trip through MSInfo32. First here is what I have based my conclusion on:
Under Hardware Resources - Conflicts/Sharing:
Code:
I/O Port 0x00000000-0x00000CF7 PCI Express Root Complex
I/O Port 0x00000000-0x00000CF7 Direct memory access controller
I/O Port 0x00000067-0x00000067 Motherboard resources
I/O Port 0x00000067-0x00000067 Motherboard resources
I/O Port 0x000003C0-0x000003DF NVIDIA GeForce GTX 780 Ti
I/O Port 0x000003C0-0x000003DF Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
I/O Port 0x00000070-0x00000070 Motherboard resources
I/O Port 0x00000070-0x00000070 System CMOS/real time clock
I/O Port 0x00000065-0x00000065 Motherboard resources
I/O Port 0x00000065-0x00000065 Motherboard resources
Memory Address 0xE8000000-0xEFFFFFFF NVIDIA GeForce GTX 780 Ti
Memory Address 0xE8000000-0xEFFFFFFF Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
I/O Port 0x000004D0-0x000004D1 Programmable interrupt controller
I/O Port 0x000004D0-0x000004D1 Motherboard resources
Memory Address 0xF7300000-0xF7307FFF ASMedia USB 3.0 eXtensible Host Controller - 0096 (Microsoft)
Memory Address 0xF7300000-0xF7307FFF Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 5 - 1E18
I/O Port 0x0000E000-0x0000E07F NVIDIA GeForce GTX 780 Ti
I/O Port 0x0000E000-0x0000E07F Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
Memory Address 0xF6000000-0xF6FFFFFF NVIDIA GeForce GTX 780 Ti
Memory Address 0xF6000000-0xF6FFFFFF Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
Memory Address 0xFF000000-0xFFFFFFFF Motherboard resources
Memory Address 0xFF000000-0xFFFFFFFF Intel(R) 82802 Firmware Hub Device
IRQ 16 Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
IRQ 16 NVIDIA GeForce GTX 780 Ti
IRQ 16 Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10
IRQ 16 Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 5 - 1E18
IRQ 16 Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
Memory Address 0xE0000000-0xE0000FFF Motherboard resources
Memory Address 0xE0000000-0xE0000FFF PCI Express Root Complex
IRQ 18 Standard SATA AHCI Controller
IRQ 18 Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 7 - 1E1C
IRQ 19 Standard SATA AHCI Controller
IRQ 19 Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 8 - 1E1E
IRQ 19 Standard SATA AHCI Controller
Memory Address 0xA0000-0xBFFFF NVIDIA GeForce GTX 780 Ti
Memory Address 0xA0000-0xBFFFF PCI Express Root Complex
Memory Address 0xA0000-0xBFFFF Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
Memory Address 0xF7200000-0xF72001FF Standard SATA AHCI Controller
Memory Address 0xF7200000-0xF72001FF Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 7 - 1E1C
Memory Address 0xF7100000-0xF71001FF Standard SATA AHCI Controller
Memory Address 0xF7100000-0xF71001FF Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 8 - 1E1E
I/O Port 0x000003B0-0x000003BB NVIDIA GeForce GTX 780 Ti
I/O Port 0x000003B0-0x000003BB Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
I/O Port 0x0000C000-0x0000C01F Standard SATA AHCI Controller
I/O Port 0x0000C000-0x0000C01F Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 8 - 1E1E
I/O Port 0x00000080-0x00000080 Motherboard resources
I/O Port 0x00000080-0x00000080 Motherboard resources
I/O Port 0x00000063-0x00000063 Motherboard resources
I/O Port 0x00000063-0x00000063 Motherboard resources
I/O Port 0x0000D000-0x0000D01F Standard SATA AHCI Controller
I/O Port 0x0000D000-0x0000D01F Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 7 - 1E1C
I/O Port 0x0000FFFF-0x0000FFFF Motherboard resources
I/O Port 0x0000FFFF-0x0000FFFF Motherboard resources
Looking through that section suggests that there are quite a few components clashing, some of those components are parts that I can have little influence over, however one thing I can do is move my GPU to a different PCI-e slot, would that then move it away from IRQ 16 to a someplace where it might not clash as much or even at all?
-
Re: Various errors! The Saga Continues!
Good to see you still digging :D
IRQ allocations/sharing is miles better than it once was, I honestly can't remember seeing an issue since the very restrictive older limitations were changed.
Go ahead and try it, even a x8 PCIe slot should give you 95%+ of x16 perfomance, you've got the original data logged so that you can quickly compare - then, assuming the GFX card's IRQ changes, it's a case of wait and see.
-
Re: Various errors! The Saga Continues!
I'm willing to bet it's yet another case of a sh*tty Anus.. pardon.. Asus motherboard doing what they do best.. not work properly :)
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
Bambooz
I'm willing to bet it's yet another case of Asus motherboard doing what they do best.. not work properly :)
You might be correct: "4,35% ASUS Sabertooth Z77" 4.35% is a pretty high return rate http://www.hardware.fr/articles/893-8/conclusion.html
"4,95% ASUS SABERTOOTH Z77" and it got worse before the Z87/97 appeared http://www.hardware.fr/articles/920-2/cartes-meres.html
-
Re: Various errors! The Saga Continues!
I've been quite busy with work and family over the last few days so not really had the time to think about this but I was wondering if there was anything I could do at BIOS level to try and resolve some of the hardware conflicts?
-
Re: Various errors! The Saga Continues!
Don't worry, real world takes priority.
Resetting the BIOS to defaults is the only thing that springs to mind.
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
satrow
Don't worry, real world takes priority.
Resetting the BIOS to defaults is the only thing that springs to mind.
Surprisingly I didn't think of that, for some reason I was thinking about using the BIOS to change IRQ allocation etc...
BIOS reset is a simple thing to try, I'll reset it now.
-
Re: Various errors! The Saga Continues!
Ok. I reset the BIOS then went into BF4 and the game crashed after a couple of rounds.
Next I swapped the GPU over and checked MSInfo32, this is what I found under Conflicts/Sharing:
Code:
I/O Port 0x00000000-0x00000CF7 PCI Express Root Complex
I/O Port 0x00000000-0x00000CF7 Direct memory access controller
I/O Port 0x00000067-0x00000067 Motherboard resources
I/O Port 0x00000067-0x00000067 Motherboard resources
I/O Port 0x000003C0-0x000003DF NVIDIA GeForce GTX 780 Ti
I/O Port 0x000003C0-0x000003DF Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0155
I/O Port 0x00000070-0x00000070 Motherboard resources
I/O Port 0x00000070-0x00000070 System CMOS/real time clock
I/O Port 0x00000065-0x00000065 Motherboard resources
I/O Port 0x00000065-0x00000065 Motherboard resources
Memory Address 0xE8000000-0xEFFFFFFF NVIDIA GeForce GTX 780 Ti
Memory Address 0xE8000000-0xEFFFFFFF Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0155
I/O Port 0x000004D0-0x000004D1 Programmable interrupt controller
I/O Port 0x000004D0-0x000004D1 Motherboard resources
Memory Address 0xF7300000-0xF7307FFF ASMedia USB 3.0 eXtensible Host Controller - 0096 (Microsoft)
Memory Address 0xF7300000-0xF7307FFF Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 5 - 1E18
I/O Port 0x0000E000-0x0000E07F NVIDIA GeForce GTX 780 Ti
I/O Port 0x0000E000-0x0000E07F Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0155
Memory Address 0xF6000000-0xF6FFFFFF NVIDIA GeForce GTX 780 Ti
Memory Address 0xF6000000-0xF6FFFFFF Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0155
Memory Address 0xFF000000-0xFFFFFFFF Motherboard resources
Memory Address 0xFF000000-0xFFFFFFFF Intel(R) 82802 Firmware Hub Device
IRQ 16 Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
IRQ 16 Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0155
IRQ 16 Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10
IRQ 16 Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 5 - 1E18
IRQ 16 Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
Memory Address 0xE0000000-0xE0000FFF Motherboard resources
Memory Address 0xE0000000-0xE0000FFF PCI Express Root Complex
IRQ 18 High Definition Audio Controller
IRQ 18 Standard SATA AHCI Controller
IRQ 18 Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 7 - 1E1C
IRQ 19 Standard SATA AHCI Controller
IRQ 19 Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 8 - 1E1E
IRQ 19 Standard SATA AHCI Controller
Memory Address 0xA0000-0xBFFFF NVIDIA GeForce GTX 780 Ti
Memory Address 0xA0000-0xBFFFF PCI Express Root Complex
Memory Address 0xA0000-0xBFFFF Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0155
Memory Address 0xF7200000-0xF72001FF Standard SATA AHCI Controller
Memory Address 0xF7200000-0xF72001FF Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 7 - 1E1C
Memory Address 0xF7100000-0xF71001FF Standard SATA AHCI Controller
Memory Address 0xF7100000-0xF71001FF Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 8 - 1E1E
I/O Port 0x000003B0-0x000003BB NVIDIA GeForce GTX 780 Ti
I/O Port 0x000003B0-0x000003BB Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0155
I/O Port 0x0000C000-0x0000C01F Standard SATA AHCI Controller
I/O Port 0x0000C000-0x0000C01F Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 8 - 1E1E
I/O Port 0x00000080-0x00000080 Motherboard resources
I/O Port 0x00000080-0x00000080 Motherboard resources
I/O Port 0x00000063-0x00000063 Motherboard resources
I/O Port 0x00000063-0x00000063 Motherboard resources
I/O Port 0x0000D000-0x0000D01F Standard SATA AHCI Controller
I/O Port 0x0000D000-0x0000D01F Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 7 - 1E1C
I/O Port 0x0000FFFF-0x0000FFFF Motherboard resources
I/O Port 0x0000FFFF-0x0000FFFF Motherboard resources
Now I just need to find some time to test it. lol
I think that the most noteworthy point is that the GTX780 is now no longer listed under IRQ 16 but I guess some stress testing is what will prove whether or not this is relavent.
-
Re: Various errors! The Saga Continues!
Can you update me with any recent crash dumps as well ;) ?
-
Re: Various errors! The Saga Continues!
-
Re: Various errors! The Saga Continues!
Thanks, just downloading the data, I'm not likely to be online for ~2 hours or so now.
-
Re: Various errors! The Saga Continues!
ok. I have to go out unexpectedly anyway.
-
Re: Various errors! The Saga Continues!
The latest crash dump was verified and flags a Windows DirectX driver, dxgmms1.sys DirectX Graphics MMS driver. DV flagging a Windows driver, if it is consistent, is usually indicative of a hardware issue.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8005785c378, The address that the exception occurred at
Arg3: ffffd000577662f8, Exception Record Address
Arg4: ffffd00057765b00, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+18
fffff800`5785c378 488b1a mov rbx,qword ptr [rdx]
EXCEPTION_RECORD: ffffd000577662f8 -- (.exr 0xffffd000577662f8)
ExceptionAddress: fffff8005785c378 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000018)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffd00057765b00 -- (.cxr 0xffffd00057765b00;r)
rax=0000000000000000 rbx=ffffe000d8113008 rcx=ffffe000da440000
rdx=fdffe000d8783be0 rsi=000000000000008e rdi=ffffe000dc4d9020
rip=fffff8005785c378 rsp=ffffd00057766530 rbp=ffffd00057766680
r8=0000000000000001 r9=0000000000000000 r10=ffffe000d7ec1ee8
r11=ffffd00057766960 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=ffffe000da440000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x18:
fffff800`5785c378 488b1a mov rbx,qword ptr [rdx] ds:002b:fdffe000`d8783be0=????????????????
Last set context:
rax=0000000000000000 rbx=ffffe000d8113008 rcx=ffffe000da440000
rdx=fdffe000d8783be0 rsi=000000000000008e rdi=ffffe000dc4d9020
rip=fffff8005785c378 rsp=ffffd00057766530 rbp=ffffd00057766680
r8=0000000000000001 r9=0000000000000000 r10=ffffe000d7ec1ee8
r11=ffffd00057766960 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=ffffe000da440000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x18:
fffff800`5785c378 488b1a mov rbx,qword ptr [rdx] ds:002b:fdffe000`d8783be0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8031d9f2138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+18
fffff800`5785c378 488b1a mov rbx,qword ptr [rdx]
BUGCHECK_STR: AV
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8005785b5d3 to fffff8005785c378
STACK_TEXT:
ffffd000`57766530 fffff800`5785b5d3 : ffffe000`d8113008 ffffd000`57766680 00000000`0000008e 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x18
ffffd000`57766580 fffff800`57856711 : ffffd000`55840180 00000008`f9a23a08 ffffe000`d9ac9340 ffffe000`d8baa110 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x433
ffffd000`57766800 fffff800`5786c1d2 : ffffe000`d87a93e0 ffffe000`00000000 ffffe000`00000000 ffffe000`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x1f1
ffffd000`57766b50 fffff800`5786bf7d : ffffe000`da402000 ffffe000`00000000 00000000`00000080 ffffe000`d9e19880 : dxgmms1!VidSchiRun_PriorityTable+0x252
ffffd000`57766bc0 fffff803`1d78f36c : ffffd000`5575a3c0 ffffe000`d9e19880 ffffd000`57766c90 fffff803`1d7e307d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`57766c00 fffff803`1d7e62c6 : ffffd000`5574e180 ffffe000`d9e19880 ffffd000`5575a3c0 ffffc000`1aa0aed0 : nt!PspSystemThreadStartup+0x58
ffffd000`57766c60 00000000`00000000 : ffffd000`57767000 ffffd000`57761000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+18
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54505506
IMAGE_VERSION: 6.3.9600.17415
STACK_COMMAND: .cxr 0xffffd00057765b00 ; kb
BUCKET_ID_FUNC_OFFSET: 18
FAILURE_BUCKET_ID: AV_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation
BUCKET_ID: AV_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_vrf_dxgmms1!vidmm_global::referenceallocationforpreparation
FAILURE_ID_HASH: {32da7b95-4bf8-29f4-76ca-72aac4aa0d11}
Followup: MachineOwner
-
Re: Various errors! The Saga Continues!
Given the state that my drivers were in when I last tested a different GPU in my rig to how they are now, what can I do to determine the source of the hardware error?
I'm inclined to say it will be either mobo (most likely) or GPU (a possibility). I'm saying mobo due to the Intel Management Engine Driver issues but it could be GPU due to the IRQ conflicts. If the issues persist now that I have removed the GPU from IRQ 16 what can we assume from that information? What if it resolves the issues, would that prove a hardware fault?
I really don't want to have to send hardware for RMA as that would a royal PITA. But I guess what's more important now is to eliminate the probable causes until we can isolate the actual cause, rather than jumping at conclusions and buying more hardware that won't fix my problems.
Also, how do I stop the driver verifier?
-
Re: Various errors! The Saga Continues!
I don't think it's an IRQ issue, I've not seen any of those in W7, that problem has vanished in recent years.
It could still be 'board, PSU or GFX I reckon, best test would be to switch out the GFX card with a friend/colleague for a few days... OCCT might pick up an error?
-
Re: Various errors! The Saga Continues!
Disclaimer:
I accept no responsibility for any damage to anyone’s computer by following this.
It worked for me, but please if you are unsure do not use the utility in the optional part as it is dangerous. (no really it is)
Best case it works! Worse case you need a new pre-programmed Bios chip.
Easy Bit
Have You updated your Management Engine FIRMWARE to 8.1 (ships with 8) IntelME81_Updating_Tool_V10001.zip (Asus using same link for all Z77 Boards).
After doing this you MUST reset (via Jumper) your Bios & after booting normally, reboot to bios and check your settings(as it can sometimes cause issues (corrupt/missing options))
[optional]If you still have M.E. issues or corrupt options : (the hard bit)
Download latest Bios
Download this BIOS flasher: http://www.ami.com/?AMIBIOS_and_Apti...te_Utility.zip
Extract the zip, navigate to: AMIBIOS_and_Aptio_AMI_Firmware_Update_Utility\Aptio\AFUWIN
Depending on your OS architecture, either open the 64 or 32 folder
Open the zip in the folder you just opened
Extract the folder within the zip
Either restart your computer or close every application that's running, this step is important!
Return to your extracted folder and run AFUWINGUI.exe
save your old bios as a backup, just in case
Click "Open" then browse to the latest BIOS file
Under the Setup tab, tick the "Program All Blocks" check box (see below image)
http://www.overclock.net/content/typ.../1000/flags/LL
FLASH.... (can take some time as it is a full bios rebuild)
Hold breath.....
BOOT
Profit (hopefully)
NB. You may have to fully reinstall windows for that fresh feel but you should be able to to see if it worked.
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
aramil
Disclaimer:
I accept no responsibility for any damage to anyone’s computer by following this.
It worked for me, but please if you are unsure do not use the utility in the optional part as it is dangerous. (no really it is)
Best case it works! Worse case you need a new pre-programmed Bios chip.
Easy Bit
Have You updated your Management Engine FIRMWARE to 8.1 (ships with 8)
IntelME81_Updating_Tool_V10001.zip (Asus using same link for all Z77 Boards).
After doing this you MUST reset (via Jumper) your Bios & after booting normally, reboot to bios and check your settings(as it can sometimes cause issues (corrupt/missing options))
[optional]If you still have M.E. issues or corrupt options : (the hard bit)
Download latest Bios
Download this BIOS flasher:
http://www.ami.com/?AMIBIOS_and_Apti...te_Utility.zip
Extract the zip, navigate to: AMIBIOS_and_Aptio_AMI_Firmware_Update_Utility\Aptio\AFUWIN
Depending on your OS architecture, either open the 64 or 32 folder
Open the zip in the folder you just opened
Extract the folder within the zip
Either restart your computer or close every application that's running,
this step is important!
Return to your extracted folder and run AFUWINGUI.exe
save your old bios as a backup, just in case
Click "Open" then browse to the latest BIOS file
Under the Setup tab, tick the "Program All Blocks" check box (see below image)
http://www.overclock.net/content/typ.../1000/flags/LL
FLASH.... (can take some time as it is a full bios rebuild)
Hold breath.....
BOOT
Profit (hopefully)
NB. You may have to fully reinstall windows for that fresh feel but you should be able to to see if it worked.
WHAT??? OMG. Could all of this have been resolved months ago? I didn't know anything about this, and have probably been having issues for as long as I've been running 8.1, which I think is October 18th. I can't do anything now, but if that resolves it then I will have a top notch PC, running at it's best with the cleanest Windows Installation that I have ever had, thanks to satrow and other helpful posts on here.
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
KeyboardDemon
WHAT??? OMG. Could all of this have been resolved months ago? I didn't know anything about this, and have probably been having issues for as long as I've been running 8.1, which I think is October 18th. I can't do anything now, but if that resolves it then I will have a top notch PC, running at it's best with the cleanest Windows Installation that I have ever had, thanks to satrow and other helpful posts on here.
LOL. Hopefully it should sort your PC.
NB. later asus bios's reset the motherboards MAC address to 88:88:88:88:87:88, without serial numbers etc. (a none issue unless you use several asus z77 motherboards on the same network) can be edited before flashing using this: https://github.com/LongSoft/FD44Edit...ases/tag/0.9.2 (all the info, should you need it, is on the motherboard stickers)
Section 7 of THIS POST has instructions for the editor.
Not something you have to do, but just in case you want to.
Any Questions just ask :telephone:
-
Re: Various errors! The Saga Continues!
It looks like I have the latest Intel ME Firmware as I got this error in the error log when I tried to update it:
Quote:
Error 8772: Invalid usage, -allowsv switch required to update the same version firmware
-
Re: Various errors! The Saga Continues!
Perhaps under the Hardware_id in Device Manager ... Properties > Details (example: PCI\VEN_8086&DEV_1E3A&SUBSYS_1E3A1849&REV_04)?
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
KeyboardDemon
Is there anyway to check what version of the Intel ME firmware I am currently running before I run the update?
http://www.mediafire.com/download/h4...and7series.zip
extract & run the windows version in an admin command prompt
\MEInfo_6and7series\MEInfo 6and7series\Windows64\MEInfoWin64.exe
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
KeyboardDemon
It looks like I have the latest Intel ME Firmware as I got this error in the error log when I tried to update it:
I can only only assume either a bad F/W or bios flash or corrupt drivers (but as you have reinstalled several times, i guess you have downloaded several).
You Could try the full AMIBios flash [optional] in my first post.
it's either that or the board itself
-
Re: Various errors! The Saga Continues!
This is what I got:
http://i153.photobucket.com/albums/s...ps12tsivd4.png
I might try doing a full jumper BIOS reset though as I have just been resetting using the BIOS options to load optimised defaults. But I won't be able to do that now as the kids are asking me to watch some netflix with them and maybe play a board game. lol
-
Re: Various errors! The Saga Continues!
OK. Completed the BIOS jumper reset and an unusual thing happened, something that I have come to expect as a normal operation when I start up my PC is no longer happening. When I hit the power button what used to happen was my fans would ramp up to full speed and scream for about a second then they would slowly ease down to a normal operating speed. What just happened now was I had a completely silent startup, which was nice.
I ran OCCT CPU:Linpack with 64 bits, AVX Capable Linpack and Use all Logical Cores enabled, it crashed after five minutes with an error but I can't remember where it save the screen shots of the graphs! I'll try it again and then I'm going to leave my PC and spend the rest of the evening with my kids.
See you all later.
-
Re: Various errors! The Saga Continues!
Something is wrong my FW version is higher?
[IMG]http://i1193.photobucket.com/albums/...ps4lhyn9b2.png[/IMG]
on the plus side i am updating my drivers lol
Quote:
Originally Posted by
KeyboardDemon
OK. Completed the BIOS jumper reset and an unusual thing happened, something that I have come to expect as a normal operation when I start up my PC is no longer happening. When I hit the power button what used to happen was my fans would ramp up to full speed and scream for about a second then they would slowly ease down to a normal operating speed. What just happened now was I had a completely silent startup, which was nice.
I ran OCCT CPU:Linpack with 64 bits, AVX Capable Linpack and Use all Logical Cores enabled, it crashed after five minutes with an error but I can't remember where it save the screen shots of the graphs! I'll try it again and then I'm going to leave my PC and spend the rest of the evening with my kids.
See you all later.
Np. looks like a bad bios flash.
-
Re: Various errors! The Saga Continues!
Do you mean a bad mobo BIOS flash or Intel Memory Engine Chipset?
If it's the mobo it shouldn't be a problem to download the latest version and re-flash it right?
This is what happens when I try and run the IME Updater:
http://i153.photobucket.com/albums/s...psbwww7lhe.png
-
Re: Various errors! The Saga Continues!
Ok, I've manually updated the driver to 11.0.0.1115 using the device manager and that worked fine.
I can't seem to upgrade my MEI BIOS though, the American Megatrends program doesn't seem to recognise the .bin file that I've downloaded and I'm not sure if I want to change the extension to fit the type .cap or .rom that it is expecting. I think I need to sleep on it, but I feel confident that things are moving in the right direction. Hopefully I'll have more joy after work tomorrow.
Oh yeah, it looks like the silent startup I had straight after my BIOS reset was only a temporary thing as my fans are back to their normal noisy startup that I used to get before.
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
KeyboardDemon
Ok, I've manually updated the driver to 11.0.0.1115 using the device manager and that worked fine.
I can't seem to upgrade my MEI BIOS though, the American Megatrends program doesn't seem to recognise the .bin file that I've downloaded and I'm not sure if I want to change the extension to fit the type .cap or .rom that it is expecting. I think I need to sleep on it, but I feel confident that things are moving in the right direction. Hopefully I'll have more joy after work tomorrow.
Oh yeah, it looks like the silent startup I had straight after my BIOS reset was only a temporary thing as my fans are back to their normal noisy startup that I used to get before.
to flash a bin file use http://www.mediafire.com/download/ae....1.40.1456.rar
latest z77 8.* firmware http://www.mediafire.com/download/c1...281.5MB%29.rar
extract to same folder
admin command prompt then
Code:
FWUpdLcl64.exe -f ME8_1.5m_production.bin
you must fully shutdown your computer after this (not just reboot)
As always with firmware flashes you do them at your own risk.
just done mine to prove it works :)
http://i1193.photobucket.com/albums/...ps84qx6nod.png
-
Re: Various errors! The Saga Continues!
I know some boards are picky about upgrading the IME if the BIOS is below a certain point....and while you may have the latest BIOS, you probably don't have all the newest modules in it.
Might be worth upgrading the various parts using UEFI BIOS Updater (UBU)
-
Re: Various errors! The Saga Continues!
Hopefully this brings an end to the saga.
I decided on using the links provided by aramil as that looked like less work than the suggestion offered by shaithis, though I'm grateful for all suggestions and the time people have taken to help me this far.
Now for the arduous task of playing many rounds of BF4 to see if I still have stability issues. Uhh! It's a tough job, but somebody has to do it! :devilish:
http://i153.photobucket.com/albums/s...psudpnhtnc.png
***edit*** OCCT used to encouter an error and stop testing on Linpack after about 5 minutes, it's now been running for close to 10 with no errors and I'm using my PC to post this message while it runs. I think that's a good thing. :D
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
shaithis
I know some boards are picky about upgrading the IME if the BIOS is below a certain point....and while you may have the latest BIOS, you probably don't have all the newest modules in it.
Might be worth upgrading the various parts using
UEFI BIOS Updater (UBU)
It's a good tool to have, personally I like to do it manually (helps with the understanding of the how why what etc.)
Quote:
Originally Posted by
KeyboardDemon
Hopefully this brings an end to the saga.
I decided on using the links provided by aramil as that looked like less work than the suggestion offered by shaithis, though I'm grateful for all suggestions and the time people have taken to help me this far.
Now for the arduous task of playing many rounds of BF4 to see if I still have stability issues. Uhh! It's a tough job, but somebody has to do it! :devilish:
http://i153.photobucket.com/albums/s...psudpnhtnc.png
***edit*** OCCT used to encouter an error and stop testing on Linpack after about 5 minutes, it's now been running for close to 10 with no errors and I'm using my PC to post this message while it runs. I think that's a good thing. :D
Hopefully :thumbsup:
If not i can post up a reworked 2104 bios with fully up to date modules etc (as Shaithis stated, although in testing i have not noticed any issues so far with vanilla or updated 2104 with ME 8.1.52.***)
-
Re: Various errors! The Saga Continues!
Man, seems to me like a right pain in the back side. But I would love to 'have it' and sort it out (eventually).
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
Bonebreaker777
Man, seems to me like a right pain in the back side. But I would love to 'have it' and sort it out (eventually).
It was a complete royal PITA, but it has to be said that I learnt so much through this experience. I really hope it is sorted now. I still need to stop the driver verifier from running, I think that just means issuing a reset instruction through an elevated command prompt.
-
Re: Various errors! The Saga Continues!
Quote:
To turn Driver Verifier off - verifier /reset then re-boot
Is that easy enough?
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
satrow
Is that easy enough?
Excellent, it was simply reset through an elevated prompt, but what's not so excellent is I had another Blue Screen this morning. :(
I got this minidump for it, but have to go to work now. I can't do much now till maybe early next week.
-
Re: Various errors! The Saga Continues!
And the dump was Verified, indicating that DV was (still?) active with the 'faulting' driver being the Wdf01000.sys which is the WDF Dynamic - Kernel Mode Driver Framework Runtime. I very much doubt that it's the true cause of the crash.
I think it's best to ignore this one, check through this and ensure DV is not running: https://msdn.microsoft.com/en-us/Lib...=vs.85%29.aspx
Quote:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80323bcc929, ffffd0002262ed10, 0}
Probably caused by : Wdf01000.sys ( Wdf01000!FxDevice::DispatchWithLock+2a5 )
Followup: MachineOwner
---------
0: kd> kd: Reading initial command '!analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q'
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80323bcc929, Address of the instruction which caused the bugcheck
Arg3: ffffd0002262ed10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
fffff803`23bcc929 498b08 mov rcx,qword ptr [r8]
CONTEXT: ffffd0002262ed10 -- (.cxr 0xffffd0002262ed10;r)
rax=00000002a92c0002 rbx=ffffe000a7f4caf0 rcx=ffffe000a9c11ec0
rdx=fdffe000ac080ac0 rsi=0000000000000000 rdi=ffffe000a9b05440
rip=fffff80323bcc929 rsp=ffffd0002262f740 rbp=ffffd0002262f7c9
r8=fdffe000ac080ac0 r9=ffffe000a7f4cf68 r10=ffffe000a9c11ec0
r11=ffffe000ab216b00 r12=0000000000000000 r13=ffffe000a9c11f48
r14=ffffe000a9be7530 r15=ffffe000a9c11ec0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!ExpInterlockedPopEntrySListFault:
fffff803`23bcc929 498b08 mov rcx,qword ptr [r8] ds:002b:fdffe000`ac080ac0=????????????????
Last set context:
rax=00000002a92c0002 rbx=ffffe000a7f4caf0 rcx=ffffe000a9c11ec0
rdx=fdffe000ac080ac0 rsi=0000000000000000 rdi=ffffe000a9b05440
rip=fffff80323bcc929 rsp=ffffd0002262f740 rbp=ffffd0002262f7c9
r8=fdffe000ac080ac0 r9=ffffe000a7f4cf68 r10=ffffe000a9c11ec0
r11=ffffe000ab216b00 r12=0000000000000000 r13=ffffe000a9c11f48
r14=ffffe000a9be7530 r15=ffffe000a9c11ec0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!ExpInterlockedPopEntrySListFault:
fffff803`23bcc929 498b08 mov rcx,qword ptr [r8] ds:002b:fdffe000`ac080ac0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x3B
PROCESS_NAME: adventure-capi
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8012ca5e4e5 to fffff80323bcc929
STACK_TEXT:
ffffd000`2262f740 fffff801`2ca5e4e5 : 00000000`00000080 00000000`00000801 00000000`00000508 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault
ffffd000`2262f750 fffff803`240ee911 : ffffe000`ab27cfe0 00000000`00000000 ffffe000`a9c11d00 ffffe000`ac00a801 : Wdf01000!FxDevice::DispatchWithLock+0x2a5
ffffd000`2262f830 fffff803`23e9a77f : 00000000`00000001 ffffd000`2262fb80 ffffe000`a7f4caf0 ffffe000`ab27cf40 : nt!IovCallDriver+0x3cd
ffffd000`2262f880 fffff803`23e99d22 : 00000000`00000000 fffff803`23e14915 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa4f
ffffd000`2262fa20 fffff803`23bd14b3 : 00000000`00000001 fffff803`23b3746d ffffe000`ab4c2080 ffffd000`2262fb80 : nt!NtDeviceIoControlFile+0x56
ffffd000`2262fa90 00000000`77212352 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01b4e948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77212352
FOLLOWUP_IP:
Wdf01000!FxDevice::DispatchWithLock+2a5
fffff801`2ca5e4e5 488bf8 mov rdi,rax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Wdf01000!FxDevice::DispatchWithLock+2a5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f850
IMAGE_VERSION: 1.13.9600.16384
STACK_COMMAND: .cxr 0xffffd0002262ed10 ; kb
BUCKET_ID_FUNC_OFFSET: 2a5
FAILURE_BUCKET_ID: 0x3B_VRF_Wdf01000!FxDevice::DispatchWithLock
BUCKET_ID: 0x3B_VRF_Wdf01000!FxDevice::DispatchWithLock
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x3b_vrf_wdf01000!fxdevice::dispatchwithlock
FAILURE_ID_HASH: {348b091b-efa4-fbc2-9baf-d03d1166d7e2}
Followup: MachineOwner
-
Re: Various errors! The Saga Continues!
I haven't stopped DV yet, so I'll do that when I get home and keep testing from there.
-
Re: Various errors! The Saga Continues!
I blame the Russians they caused the Issue KD :S !
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
Jace007
I blame the Russians they caused the Issue KD :S !
They probably snuck in through my internet connection while I was playing on the US side in BF4, they're quite sneaky that way, either that or it was the Chinese.
-
Re: Various errors! The Saga Continues!
https://www.youtube.com/watch?v=dTcgaEfszTg Dam those BF4 Chinese sneaky :D ... I'm still playing BF3. any closer to your PC problem?
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
Jace007
Sorry to say no, not got any closer to fixing my problems. Still getting blue screens, not as frequent now but some weird poop all the same.
I found an app that's part of the Windows SDK that lets me read minidump files, when I get home I'll post some of the juicy highlights. lol.
I think I might have to raise a ticket for an RMA on the motherboard.
-
Re: Various errors! The Saga Continues!
Last resort?
Fully updated 2104 sabertooth bios .CAP file http://d-h.st/uuZ
needs to be flashed via usb stick as per http://event.asus.com/2012/mb/USB_BIOS_Flashback_GUIDE/
Acquire a USB Thumb Drive
Format the USB drive with a FAT32 file system, copy Cap file to usb
from powered off.
Refer to your user manual to make sure to us the USB port that support USB BIOS Flashback, and plug the USB storage device to the specific USB port. Then press the USB BIOS Flashback button for three/five seconds till the LED begins to blink, then release.
Wait till the LED stops blinking, indicating that BIOS flashing has been completed.
boot, reset bios, turn off.
Jumper reset bios,
Boot to bios (apply any setting you need)
save/reboot.
-
Re: Various errors! The Saga Continues!
This Z77ST.CAP file is 8192KB and the original Asus version is 8194KB so clearly they are different, do you know what changes have been made by any chance?
-
Re: Various errors! The Saga Continues!
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
aramil
sorry header removed version (would not of flashed.)
usb flash version (correct size)
Phew... good I thing I checked. I might not have bricked it, but I thought it would be good idea to see exactly what I'm installing and it looks like this correct file is a massive change, the Intel RST<e> ORMO and EFI SataDriver appear to have major revisions going from 11.x to 14.x, with another major revision further down the list for the EFI Intel Pro/1000 UNDI, which looks like it controls something networking related, everything else has had a minor revision update, very little appears to be unchanged, at least to my untrained eye.
I'll drop that in later, I have to go out at the moment.
BTW: How are you bringing up that BIOS information?
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
KeyboardDemon
I'll drop that in later, I have to go out at the moment.
BTW: How are you bringing up that BIOS information?
this:
Quote:
Originally Posted by
shaithis
Easier to show than in the AmiBios toolset.
-
Re: Various errors! The Saga Continues!
Oh, from a couple of pages back, I have to admit that upgrading individual parts of my BIOS scares me, a lot more than just running a standard BIOS update. But if this update doesn't work then I think I will have to go back to the solution that shaithis posted.
*** edit ***
I think I understand the UBU tool a little more now, it scare me at first, maybe because I didn't understand it. So lets check that first, because if my basic understanding of this set of tools is wrong then in my hands it might be more dangerous then I had previously imagined. So the way I read that page, the tool looks at a current version of the BIOS file and replaces the different component parts of the BIOS with more up to date components, then it finally renames the BIOS file to the name that would work with BIOS flashback for the version of mobo you need to update. Is that right?
I'm assuming that the last BIOS linked by aramil is a version that's been modified with the UBU tool, but I was unable to find the currently installed BIOS component versions such as the screenshots in aramil's post on the previous page and in the end just flashed that version of the BIOS update.
I'll test over the next few days to see if I'm getting weird or random errors that are consistent with the weirdness that I had been getting prior to flashing my BIOS.
I would be great if someone could point to a tool that would let me read the version numbers of my BIOS modules so that I can confirm that I have got it updated to the latest version of everything.
*** edit ***
Having flashed with aramil's BIOS .CAP file, I started OCCT and left the PC for an hour or so, when I got back to it I found my temps were reporting at 55 degree maximum where they used to report back at just under 90. OCCT used to stop with an error at around about the 4 to 5 minute mark, today it stopped with an error at the 7 minutes and 40 seconds mark, again with an 'error'. I really wish the error reporting could be a little bit more specific, at the moment all I know is that something went wrong and OCCT stopped running.
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
KeyboardDemon
I think I understand the UBU tool a little more now, it scare me at first, maybe because I didn't understand it. So lets check that first, because if my basic understanding of this set of tools is wrong then in my hands it might be more dangerous then I had previously imagined. So the way I read that page, the tool looks at a current version of the BIOS file and replaces the different component parts of the BIOS with more up to date components, then it finally renames the BIOS file to the name that would work with BIOS flashback for the version of mobo you need to update. Is that right?
yeah each section of a bios has a GUID (string) which identifies make/model/type/Version etc.
http://files.homepagemodules.de/b602...3_KFhUxSqG.png
Quote:
I would be great if someone could point to a tool that would let me read the version numbers of my BIOS modules so that I can confirm that I have got it updated to the latest version of everything.
use the Amiflash tool (posted in my first post) and use it to save a version of your current BIOS.
download UBU & copy this file into the UBU folder run UBU.BAT as admin and it will load your bios and show you it's versions (as per screenshots) watch it load you can see it find the GUID's.
Quote:
I started OCCT and left the PC for an hour or so, when I got back to it I found my temps were reporting at 55 degree maximum where they used to report back at just under 90. OCCT used to stop with an error at around about the 4 to 5 minute mark, today it stopped with an error at the 7 minutes and 40 seconds mark, again with an 'error'. I really wish the error reporting could be a little bit more specific, at the moment all I know is that something went wrong and OCCT stopped running.
90 Degrees Tcase temp or Core temps (TJMax)? either way to hot lol.
Have you run http://www.memtest.org/ ? (i know you have moved ram around etc (just being safe)).
what does event viewer say about why OCCT stopped?
have you tried to re-seat your CPU? (ie take it out , check pins, and refit?)
-
Re: Various errors! The Saga Continues!
OCCT doesn't crash, what happens when I run a Linpack test on my CPU is that it runs for about 5 to 7 minutes and then the information window reports that the testing has stopped with an error, OCCT in the meantime continues to run the monitoring software and I can see from the sensor information what my current, minimum and maximum temps were, along with voltages etc... I could find nothing in my Event Viewer to explain why OCCT stopped working, I checked the Overview and Summary under Critical, Error and Warning and could see nothing there that seemed to reference OCCT. Then in Windows Logs I looked into Applications and System but could find nothing that seemed to relate to OCCT there either.
I'm not really sure where else I can look or what to look for, I'm sort of picking this up as I go along, I bet no-one could tell though :surprised:.
As for temps, OCCT is the only software package that was reporting high temps under load, when I was monitoring temps whilst playing BF4 the highest I was recording was 65 with my fans on low and about 60 with my fans on high. After that last BIOS update my temps are more consistent now with OCCT reporting up 60 degrees under load when running Linpack.
-
Re: Various errors! The Saga Continues!
I've been using my PC for just general browsing today, installed Hyper-V Manager but not installed any virtual OS's yet and not really noticed any major issues but then not really done much to tax the system either. I have spotted one error over the last hour, which is this one, from the Event Viewer:
Quote:
Metadata staging failed, result={97C89BEE-F697-11E4-8255-3085A994A274} for container '0x80070490'
So I have found that the GUID=FCBB06BB-6A2A-46E3-ABAA-246CB4E508B2, which is what I found here:
Code:
- System
- Provider
[ Name] Microsoft-Windows-DeviceSetupManager
[ Guid] {FCBB06BB-6A2A-46E3-ABAA-246CB4E508B2}
EventID 131
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x4000000000000000
- TimeCreated
[ SystemTime] 2015-06-08T21:13:07.540698900Z
EventRecordID 1434
Correlation
- Execution
[ ProcessID] 1064
[ ThreadID] 1844
Channel Microsoft-Windows-DeviceSetupManager/Admin
Computer DemonsKeyboard
- Security
[ UserID] S-1-5-18
- EventData
Prop_ContainerId {97C89BEE-F697-11E4-8255-3085A994A274}
HRESULT 2147943568
So, I'm not sure if it would help to work out what the GUID belongs to, or how to do that?
But I think or at least hope that the number of errors is decreasing, and I might be getting closer to having a working rig. Either that or I need to revert back to Windows 7 or stick it till 10 is launched and hope/pray that Windows 10 will be my salvation.
-
Re: Various errors! The Saga Continues!
Here's an update on what's happening with this PC.
Still getting BSOD's, still not sure how I can read into the Minidump files properly, I found a couple of utilities but they are not reading the files properly.
Since my last post I have updated 24 drivers that relate to my mobo, chipset, GPU, USB controller, ASMedia and various storage related drivers.
I noticed that driver such as the Microsoft TCG Storage silo was on version 6.3.9600.16384 which has a release date of 21/06/2006, I have also mentioned in a few posts above that one of the recurring errors and causes of BSODs is down to TCG related errors but I can't seem to find a more recent version than that. Is this the right driver that I should have installed? The driver is nine years old and I'm running an SSD that's been around less than 18 months, surely there should be a more recent driver to run this?
As for the SSD itself, I am running the most recent version of the firmware (MU02) and have uninstalled the Intel AHCI drivers and replaced them with the Microsoft AHCI drivers instead but I am still getting the errors. I am starting to think that my issues are more SSD related than mobo even though I have gone from a Samsung 240gb SSD to this Crucial M550 after the blue screens started.
Any thoughts, ideas or suggestions?
*** edit ***
Memtest ran for 4 and a bit cycles with no errors detected, it took a little under 5 hours to complete that much.
-
Re: Various errors! The Saga Continues!
Have you upgraded the Intel RAID/AHCI modules in your BIOS?
-
Re: Various errors! The Saga Continues!
I have upgraded the BIOS using the updated image that aramil posted a couple of pages back. This, to the best of my knowledge, has all of the latest BIOS modules using the same method that you posted previously.
To the best of my knowledge my BIOS should now match the BIOS on aramil's computer, this is his after picture:
http://i1193.photobucket.com/albums/...psohmpx735.png
It doesn't seem to mention RAID/AHCI modules though.
I have not been able to confirm this though, aramil suggested that I try using the UEFI BIOS Updater (UBU) to look at what's installed in my BIOS but I couldn't figure out which program I needed in order to get that information displayed.
-
Re: Various errors! The Saga Continues!
Quote:
Metadata staging failed, result={97C89BEE-F697-11E4-8255-3085A994A274} for container '0x80070490'
I typically get similar error that is related to USB device, in my case scanner but my next event reports success.
If you got to the event logs -> Applications and Service logs -> Microsoft -> Windows -> DeviceMangerSetup and you should see the next event if it is success after the error and what device it is.
The TCG issue... is this the error you are sort of getting?
Quote:
A TCG Command has returned an error.
Desc: AuthenticateSession
Param1: 0x1
Param2: 0x60000001C
Param3: 0x900000006
Param4: 0x0
Status: 0x1
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
stilkun
I typically get similar error that is related to USB device, in my case scanner but my next event reports success.
If you got to the event logs -> Applications and Service logs -> Microsoft -> Windows -> DeviceMangerSetup and you should see the next event if it is success after the error and what device it is.
The TCG issue... is this the error you are sort of getting?
That is exactly the error I am getting, the only difference is in the status number at the end.
I checked this last night and my Canon LIDE 120 scanner was the next event in the log, as I had my scanner connected at the time, I only have my scanner connected when I have been scanning and tend to disconnect it and put it away as I haven't got the space on my desk to keep it there permanently. On rebooting there was no error.
I started up the PC this morning and got the same TCG error, this time the I can't figure out what the next device is, here are the details:
Code:
- System
- Provider
[ Name] Microsoft-Windows-DeviceSetupManager
[ Guid] {FCBB06BB-6A2A-46E3-ABAA-246CB4E508B2}
EventID 112
Version 0
Level 4
Task 0
Opcode 0
Keywords 0x4000000000000000
- TimeCreated
[ SystemTime] 2015-06-19T16:08:42.123645100Z
EventRecordID 1854
Correlation
- Execution
[ ProcessID] 1152
[ ThreadID] 3040
Channel Microsoft-Windows-DeviceSetupManager/Admin
Computer DemonsKeyboard
- Security
[ UserID] S-1-5-18
- EventData
Prop_DeviceName Fax
Prop_ContainerId {CA0F309A-F5CF-11E4-824C-3085A994A274}
Prop_TaskCount 4
Prop_PropertyCount 0
Prop_WorkTime_MilliSeconds 578
What I noticed was that the event ID for my scanner and then the event ID for this device were the same so I looked them up and found a technet article, then I looked up event ID 131 which is the one that's coming up as the reason for my error and found this which is pointing to a NetBIOS configuration error, I've followed the instructions but now I have to go out so will check on progress shortly.
-
Re: Various errors! The Saga Continues!
I had TCG error before which indicate something to do with bitlocker or secureboot on Windows 8.1 but I could be wrong. This guy had 0x12: http://forum.crucial.com/t5/Crucial-.../165222#M47022
I believe the DeviceSetupManager typically log events about device connecting to Windows Update to check if there are latest drivers available. I have canon 100 lide scanner and logs event ID 131 whenever I plug it in so it could be false alarm or it can't find connect to windows update to compare driver versions.
Strangely, if you look at the bottom at EventData, it list the device as Fax. Open up regedit, go to HKLM\System\CurrentControlSet\Control\DeviceContainer and see if GUID there. If it exists, expand BaseConfiguration and Select the GUID and you should a registry something like USB\VID_ etc.
Edit:
Actually the better way to find out is copy the GUID and Open up Regedit the browse to HKLM\System\CurrentControlSet\Enum. Press Control + F and paste in your GUID to see if it matches something. It will contain some information to indicate what the device is.
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
stilkun
After looking through this I Deleted my keys in my BIOS and rebooted, but this has not changed anything, I'm still getting TCG error but it is showing up as Event ID 10 now where it used to be Event ID 131.
Quote:
Originally Posted by
stilkun
I believe the DeviceSetupManager typically log events about device connecting to Windows Update to check if there are latest drivers available. I have canon 100 lide scanner and logs event ID 131 whenever I plug it in so it could be false alarm or it can't find connect to windows update to compare driver versions.
Strangely, if you look at the bottom at EventData, it list the device as Fax. Open up regedit, go to HKLM\System\CurrentControlSet\Control\DeviceContainer and see if GUID there. If it exists, expand BaseConfiguration and Select the GUID and you should a registry something like USB\VID_ etc.
Edit:
Actually the better way to find out is copy the GUID and Open up Regedit the browse to HKLM\System\CurrentControlSet\Enum. Press Control + F and paste in your GUID to see if it matches something. It will contain some information to indicate what the device is.
I don't feel confident enough to poke around my registry yet, I might try and see if I can talk to the support guys at Crucial and see if they can suggest a solution.
-
Re: Various errors! The Saga Continues!
It looks like I might never get to the bottom of this saga, having spoken to a few tech support people and shown my minidump files to one, it looks like it might be a RAM issue. However Memtest is not picking up any errors. What else can I use to run diagnostics on my RAM?
-
Re: Various errors! The Saga Continues!
OMG! There's even a post on these very forums. I've not been finding any issues with my RAM because I've been using the wrong version of Memtest86. I've just tested my RAM with Memtest86+ and found heaps of errors.
Time to RMA.
On the positive side, my mobo and Intel Management Engine Interface should be completely up to date now thanks to everyone that's pitched in with helpful tips and suggestions. Which is good news. ;) :cool:
I'm going to mark this one as solved, hopefully there are no further issues with this.
-
Re: Various errors! The Saga Continues!
Ah, it's 86+ that I suggest when I suspect memory errors - 8 passes because I've seen a number come back with errors on the 7th. 12+ passes greatly increases the false positive chances, over 20 before a fail and it's pretty sure to be wrong.
Good work for persevering with this and finding it out.
-
Re: Various errors! The Saga Continues!
The really annoying thing is that people such as Biscuit to name one, have been saying it sounds like a memory fault from the start and I have been blindly accepting what Memtest86 was telling me with regards to no errors.
Another lesson learnt.
-
Re: Various errors! The Saga Continues!
Great news that you've finally found the cause of all your PC instability problems! Although I thought you said in the past that you'd tried swapping out the memory? Still, you must be very relieved to have finally sorted it out...a saga indeed!
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
MrJim
Great news that you've finally found the cause of all your PC instability problems! Although I thought you said in the past that you'd tried swapping out the memory? Still, you must be very relieved to have finally sorted it out...a saga indeed!
I have two identical kits, both are Corsair CMZ8GX3M2A1866C9R kits, I think at some point I might have removed a kit and then put the same kit back in, I did swap them a few times though, so it's also possible that when both kits were in, one in 1+3 and the other in 2+4, I took the wrong pair out. Who knows? I can only guess as to how I ended up with the dodgy ram in my PC and good set in storage!
RMA application has been completed, hopefully I'll hear back from Corsair in a day or two and once I have my pack and dispatch instructions I can get the RMA process started.
-
Re: Various errors! The Saga Continues!
Glad its finally sorted mate. What a mission!
-
Re: Various errors! The Saga Continues!
Quote:
Originally Posted by
Biscuit
Glad its finally sorted mate. What a mission!
Agreed, deserves Seriously emboldened in his user title for this epic.