ocman
I was unable as you can see from dump output, to determine what your motherboard model is, but i can say that your current issue is probably not connected to bios.
1: kd> ! sysinfo smbios
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).
That being said, i took a look at your system information file, specifically the error reporting section, and there is no doubt as to what is generating almost all the recent errors and possibly the crashes. Below is a sample and i suspect you have probably
seen this.
There are a lot of these and that leads me to believe that faulting application is playing a big part in you recent problems.
output from sysinfo.txt
2014-02-27 1:02 AM Application Error Faulting application name: hsssrv.exe, version: 2.81.0.0, time stamp: 0x50e79b39
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b96f
Exception
code: 0xc0000005
Fault offset: 0x00039342
Faulting process id: 0x15d0
Faulting application start time: 0x01cf33253eb8396d
Faulting application path: C:\Program Files (x86)\Hotspot Shield\HssWPR\hsssrv.exe
Faulting
module path: C:\Windows\syswow64\ole32.dll
Report Id: e532edf4-9f4a-11e3-b2bc-78acc099422c
hsssrv.exe
fffff88006816000 fffff8800682b000 hssdrv6 hssdrv6.sys
Loaded symbol image file: hssdrv6.sys
Symbol file: hssdrv6.sys
Image path: hssdrv6.sys
Timestamp: Fri Jan 04 22:38:37 2013 (50E7A03D)
CheckSum: 00014D6B
ImageSize: 00015000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Driver Description: Hotspot Shield Routing Driver
Possible BSOD cause seen in mid-2012
Driver Description: Hotspot Shield Routing Driver
Possible BSOD cause seen in mid-2012
Driver Update Site: http://hotspotshield.com/
Here is another driver with a history of causing BSOD's.. please remove
fffff88001843000 fffff8800188c000 dtsoftbus01 dtsoftbus01.sys
Loaded symbol image file: dtsoftbus01.sys
Symbol file: dtsoftbus01.sys
Image path: dtsoftbus01.sys
Timestamp: Fri Jan 13 08:45:46 2012 (4F10358A)
CheckSum: 00046D1E
ImageSize: 00049000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Driver Description: Daemon Tools driver
Possible BSOD issues in Win7
Driver Update Site: http://www.daemon-tools.cc/eng/downloads
This should not be on your system either..
fffff88007060000 fffff88007072100 xusb21 xusb21.sys
Loaded symbol image file: xusb21.sys
Symbol file: xusb21.sys
Image path: xusb21.sys
Timestamp: Thu Aug 13 18:10:17 2009 (4A848F49)
CheckSum: 00020048
ImageSize: 00012100
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Driver Description: XBox USB wireless controller
BSOD issues in Win7 with 2009 driver (found in mid-2012)
Driver Update Site: http://www.microsoft.com/hardware/download/download.aspx?category=Gaming&type=Gaming&sku=JR9-00001
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80060ed758, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff88001fd16f0 fffff80002928ca9 : fffffa80060ed730 fffffa800523a040 0000000000000009 0000000000000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff88001fd1c10 fffff80002809ea7 : fffffa80060ed730 fffff800028832d8 fffffa800523a040 0000000000000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff88001fd1c40 fffff80002771275 : fffff800028e4b40 0000000000000001 fffffa800524e640 fffffa800523a040 : nt!WheapProcessWorkQueueItem+0x57
fffff88001fd1c80 fffff800026e7261 : fffff880011a7e00 fffff80002771250 fffffa800523a000 fffffa800523a040 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff88001fd1cb0 fffff8000297a2ea : fffff88000c560fc fffffa800523a040 0000000000000080 fffffa8005232890 : nt!ExpWorkerThread+0x111
fffff88001fd1d40 fffff800026ce8e6 : fffff88001e5d180 fffffa800523a040 fffff88001e67fc0 fffff88000c496a0 : nt!PspSystemThreadStartup+0x5a
fffff88001fd1d80 0000000000000000 : fffff88001fd2000 fffff88001fcc000 fffff88002790790 0000000000000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557321(v=vs.85).aspx
What to try
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
All I can recommend at this point is, to try removing the above listed drivers and run the usual recommended hardware stress tests if the situation does not improve.