Tech problems… at the worst time

So apparently my desktop has decided to try and give up the ghost at the worst.fucking.time possible. So I’m throwing my GoFundMe link back out there. Now I’m looking at a new PSU, two hard drives, and video cards that can do better graphics.

ETA: A generous benefactor donated the remainder of my goal so when the funds clear I’ll be pricing out a new computer. #happycreys

Secondly, my computer had crashed out twice this week, both times while watching Twitch streams at the same exact time of night. Technical details, and error reports under the cut. If you can help me figure this out and keep me from getting CTD or BSOD on this damn thing I will be your friend forever. Even though the crashes happened yesterday and today, I still got these error logs dated October 2014.

Google fu has failed me multiple times on trying to resolve these errors and the sudden crashes could be either:

  • PSU failure
  • HDD Failure
  • CPU Failure
  • OS Corruption
  • A combination of the above to create a clusterfuck of fail.

WhoCrashed Info: System Information (local)


computer name: CYPHER
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Gigabyte Technology Co., Ltd., AMD Corporation, 990FXA-UD3
CPU: AuthenticAMD AMD FX(tm)-6100 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 25735983104 total

Video Card: nVidia GTX 550Ti 1GB PCIe video card. (I had installed an AMD 960 that Bianca sent me, both wouldn’t fit for crossfire and it turns out the PSU can’t keep it running anyway. I had to put the old card back and the computer finally booted up. 

Peripherals: 2TB External HD for back up, Logitech 5.1 surround sound speaker system, USB 2.0 Hub, Logitech K750 Solar keyboard, USB Game pad.

I also keep getting a pop up with the Microsoft.net errors as follows:

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. Unable to load DLL ‘hppatusg01dll’: The specified module could not be found. (Exception from HRESULT: 0x8007007E)See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.DllNotFoundException: Unable to load DLL ‘hppatusg01.dll’: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at Com.HP.App.HPToolkit.HPStreams.HBCDLLStreamsInterface.IsDeviceConnected(String pPortName)
at Com.HP.App.HPToolkit.HPDevice.ClientDevice.IsDeviceConnected()
at Com.HP.PLS.UsageTracking.ClientDeviceWrapper.get_IsConnected()
at Com.HP.PLS.UsageTracking.PE.MarsHost.IsOptedInAndConnected(OptInLoader loader, List`1 proxies)
at Com.HP.PLS.UsageTracking.PE.MarsHost.ShouldExit(OptInLoader loader, List`1 proxies)
at Com.HP.PLS.UsageTracking.PE.MarsHost.ShouldExit()
at Com.HP.PLS.UsageTracking.PE.App.OnMainTimer(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
—————————————-
hppusg
Assembly Version: 1.1.0.1
Win32 Version: 1.1.0.1
CodeBase: file:///C:/Program%20Files%20(x86)/HP/HP%20UT/bin/hppusg.exe
—————————————-
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
—————————————-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
—————————————-
HPTools
Assembly Version: 5.1.0.1
Win32 Version: 5.1.0.1
CodeBase: file:///C:/Program%20Files%20(x86)/HP/HP%20UT/bin/HPTools.DLL
—————————————-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
—————————————-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
—————————————-
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5488 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
—————————————-
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
—————————————-
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
—————————————-
HPUsageTracking
Assembly Version: 1.1.0.1
Win32 Version: 1.1.0.1
CodeBase: file:///C:/Program%20Files%20(x86)/HP/HP%20UT/bin/HPUsageTracking.DLL
—————————————-
interop.hpqusg
Assembly Version: 130.0.287.0
Win32 Version: 130.0.287.0
CodeBase: file:///C:/Program%20Files%20(x86)/HP/HP%20UT/bin/interop.hpqusg.DLL
—————————————-
HPToolkit
Assembly Version: 5.1.0.1
Win32 Version: 5.1.0.1
CodeBase: file:///C:/Program%20Files%20(x86)/HP/HP%20UT/bin/HPToolkit.DLL
—————————————-
v9z6tc-g
Assembly Version: 5.1.0.1
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
—————————————-
Enumeration
Assembly Version: 5.1.0.1
Win32 Version: 5.1.0.1
CodeBase: file:///C:/Program%20Files%20(x86)/HP/HP%20UT/bin/Enumeration.DLL
—————————————-
System.Runtime.Serialization.Formatters.Soap
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Serialization.Formatters.Soap/2.0.0.0__b03f5f7f11d50a3a/System.Runtime.Serialization.Formatters.Soap.dll
—————————————-
f3cll8jy
Assembly Version: 5.1.0.1
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
—————————————-
w1gpqma3
Assembly Version: 5.1.0.1
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
—————————————-
HPStreamsInterface
Assembly Version: 5.1.0.1
Win32 Version: 5.1.0.1
CodeBase: file:///C:/Program%20Files%20(x86)/HP/HP%20UT/bin/HPStreamsInterface.DLL
—————————————-************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.For example:<configuration>
<system.windows.forms jitDebugging=”true” />
</configuration>When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Crash Dump Analysis


Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 10/26/2014 11:51:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102614-46301-01.dmp
This was probably caused by the following module: tdx.sys (0xFFFFF88001A12245)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001A12245)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tdx.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TDI Translation Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.