Various errors! The Saga Continues!

[aramil]

I'll drop that in later, I have to go out at the moment.

BTW: How are you bringing up that BIOS information?

this:

Might be worth upgrading the various parts using UEFI BIOS Updater (UBU)

Easier to show than in the AmiBios toolset.

[KeyboardDemon]

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.

[aramil]

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.

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.

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?)

[KeyboardDemon]

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 .

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.

[KeyboardDemon]

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:

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:

- 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.

[KeyboardDemon]

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.

[shaithis]

Have you upgraded the Intel RAID/AHCI modules in your BIOS?

[KeyboardDemon]

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:



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.

[stilkun]

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?

A TCG Command has returned an error.
Desc: AuthenticateSession
Param1: 0x1
Param2: 0x60000001C
Param3: 0x900000006
Param4: 0x0
Status: 0x1

[KeyboardDemon]

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:

- 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.

[stilkun]

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.

[KeyboardDemon]

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

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.

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.

[KeyboardDemon]

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?

[KeyboardDemon]

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.

I'm going to mark this one as solved, hopefully there are no further issues with this.

[satrow]

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.

[KeyboardDemon]

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.