Windows 7 Help needed! Computer constantly freezing! Please help.

[StingrayJG]

Hello everyone, total newbie when it comes to this stuff, but I desperately need to resolve why our computer keeps freezing frequently. I hope you can help.
This is a relatively new computer (just a few months in operation)
I have two separate profiles (besides "user" and "guest" which rarely get used) that my wife and I use serarately. The computer seems to freeze much more often when she is in her profile and going into her MS Outlook to use email. I would say that for every ten times it happens, it happens 9 for her and one for me (although it froze on me three times just this morning) I did transfer outlook data files from our old computer to this one for both of us, so I'm wondering if maybe my wifes transferred data file may have been corrupt or broken file and that may be contributing to this issue. Again I'm a newbie so these are very uneducated guesses on my part. But it does seem like outlook is always in the middle of the freezes coincidentally most of the time. Some other info that may be noteworthy: I run McAfee total protection, I have Secunia PSI running. I have carbonite on here but not running constantly in background, just once 4:30am daily then paused during the day.
Any help and/or guidance that anyone can provide here would be profusely appreciated.
Thanks for looking.
Jim.
P.S. I have not had outlook up since I began typing this and no freezes. Clue?
I will now attach some files I made for you, standby...

 

[StingrayJG]

Next file...

 

[StingrayJG]

Final file....

 

[StingrayJG]

Here is one of the BSOD info screens that my wife managed to capture for me last night....

[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7601.2.1.0.256.48[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: fe[/FONT]
[FONT=&quot] BCP1: 0000000000000008[/FONT]
[FONT=&quot] BCP2: 0000000000000006[/FONT]
[FONT=&quot] BCP3: 000000000000000A[/FONT]
[FONT=&quot] BCP4: FFFFFA8018E16B20[/FONT]
[FONT=&quot] OS Version: 6_1_7601[/FONT]
[FONT=&quot] Service Pack: 1_0[/FONT]
[FONT=&quot] Product: 256_1[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\Minidump\040413-47876-01.dmp[/FONT]

[FONT=&quot] C:\Users\Tracy\AppData\Local\Temp\WER-174923-0.sysdata.xml[/FONT]

[FONT=&quot] [/FONT]
[FONT=&quot]Read our privacy statement online:[/FONT]
[FONT=&quot] [/FONT][FONT=&quot]Windows 7 Privacy Statement - Microsoft Windows[/FONT][FONT=&quot][/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]If the online privacy statement is not available, please read our privacy statement offline:[/FONT]
[FONT=&quot] [/FONT][FONT=&quot]C:\Windows\system32\en-US\erofflps.txt[/FONT][FONT=&quot][/FONT]

 

[GeneralHiningII]

Pre-examination:
You say that you transferred data from your old computer to your new one:
A few question in my mind:
A) What type of files were they mainly (images. text files. excel spreadsheets etc.)
B) Which version of Outlook was on the old one, and which version do you have on your new one?
C) How much data did you transfer (around how much in size)?
From the information you've given me, it does look like Outlook is the problem here, but it's best to check your drivers and software as well.

To be quite honest with you, extra programs for virus scanning (Secunia PSI, Hotspot Shield and whatever) are just memory hogs that eat up all your RAM. A good antivirus that scans once a week is more than enough to keep your computer safe from viruses. Good internet browsing habit is also a good idea (Running Windows Firewall, Modem/Router Firewall (if able)).

------------------------------------------------------------
118 updates for windows - should be at 130 ish by now, give or take a few 10's.

------------------------------------------------------------
Program problems:

AllShare Framework DMS
From what I see you have the latest version of the program. Unless it's necessary you should remove it for now to see if it's a problem.

Rainmeter
Desktop Customization Tool - like the one above, remove it unless it's absolutely necessary to keep it.

Unlock
Same as the other two. Remove unless needed

You can reinstall them if the problem is fixed.

------------------------------------------------------------
Driver Problems:

wdcsam64.sys                Wed Apr 16 18:39:08 2008 (4805BB2C)
Western Digital SCSI Arcitecture Model (SAM) WDM driver 2008 driver version has known BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys

mvxxmm.sys                  Tue Aug  9 13:05:06 2011 (4E40A3E2)
Marvell Aux NV Bridge DLL - related to mv91xx SCSI HD Controller
http://www.carrona.org/drivers/driver.php?id=mvxxmm.sys
 
mvs91xx.sys                 Tue Aug  9 13:05:23 2011 (4E40A3F3)
Marvell 91xx SATA Controller Driver
http://www.carrona.org/drivers/driver.php?id=mvs91xx.sys

AppleCharger.sys            Wed Nov  2 13:46:00 2011 (4EB0AEE8)
GIGABYTE On/Off Charge driver. See here for details - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
http://www.carrona.org/drivers/driver.php?id=AppleCharger.sys

Drivers in red: Uninstall.
Drivers in blue: I've seen others with problems coming from the same driver version, update to make sure.

------------------------------------------------------------
Dumps:
Analysis:

Debug session time: Fri Apr  5 12:45:57.668 2013 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\040413-46753-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 3:06:27.495
BugCheck A, {4f70, 2, 1, fffff800030d3005}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+3274a )
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000004f70, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030d3005, address which referenced memory
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_athrx+3274a
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Apr  5 09:37:56.476 2013 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\040413-47954-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 0:46:05.193
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+3274a )
Bugcheck code 0000001E
Arguments: 
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_athrx+3274a
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Apr  5 08:50:22.453 2013 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\040413-47876-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 19:12:59.281
BugCheck FE, {8, 6, a, fffffa8018e16b20}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
Bugcheck code 000000fE
Arguments: 
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 000000000000000a, TimeoutCode
Arg4: fffffa8018e16b20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Apr  4 13:35:54.332 2013 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\040313-46691-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 20:48:24.048
BugCheck FE, {8, 6, a, fffffa8017b3ab20}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
Bugcheck code 000000fE
Arguments: 
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 000000000000000a, TimeoutCode
Arg4: fffffa8017b3ab20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Apr  3 11:26:59.242 2013 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\040213-49093-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 7:56:01.070
BugCheck FE, {8, 6, a, fffffa8017abdb20}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
Bugcheck code 000000fE
Arguments: 
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 000000000000000a, TimeoutCode
Arg4: fffffa8017abdb20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Apr  1 08:32:24.764 2013 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\033113-46223-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 2:10:45.481
BugCheck FE, {8, 6, a, fffffa8017c27b20}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
Bugcheck code 000000fE
Arguments: 
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 000000000000000a, TimeoutCode
Arg4: fffffa8017c27b20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Apr  1 04:35:31.610 2013 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\033113-47252-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 1:03:11.437
BugCheck A, {4f70, 2, 1, fffff800030cb005}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+3274a )
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000004f70, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030cb005, address which referenced memory
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_athrx+3274a
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Jan 29 15:10:26.728 2013 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\012813-58671-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 1 days 11:21:12.443
BugCheck 116, {fffffa8021241390, fffff88010207adc, ffffffffc000009a, 4}
*** 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+929adc )
Bugcheck code 00000116
Arguments: 
Arg1: fffffa8021241390, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010207adc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Three dumps pointing to athrx.sys:

athrx.sys                   Tue Feb  7 22:37:51 2012 (4F310D0F)
Atheros network adapter driver
http://www.carrona.org/drivers/driver.php?id=athrx.sys

Last updated in February last year - check the site for available updates to the device.
(note: The third dump references svchost.exe - shouldn't be a problem now, but I'll say it here for future reference if needed)

Four dumps pointing to your USB Driver Controller.
Check:
Software Download | Brother for your product
Otherwise check your motherboard manufacturer's site for any available updates.

One dump showing your NVIDIA driver:
geforce.com/drivers
for the latest drivers, be sure to check your device for the correct driver version.

That's all I got, hope to be hearing from you soon!

(Sorry for any inconvenience from the late answer)

 

[StingrayJG]

Pre-examination:
You say that you transferred data from your old computer to your new one:
A few question in my mind:
A) What type of files were they mainly (images. text files. excel spreadsheets etc.)
B) Which version of Outlook was on the old one, and which version do you have on your new one?
C) How much data did you transfer (around how much in size)?
From the information you've given me, it does look like Outlook is the problem here, but it's best to check your drivers and software as well.

To be quite honest with you, extra programs for virus scanning (Secunia PSI, Hotspot Shield and whatever) are just memory hogs that eat up all your RAM. A good antivirus that scans once a week is more than enough to keep your computer safe from viruses. Good internet browsing habit is also a good idea (Running Windows Firewall, Modem/Router Firewall (if able)).

------------------------------------------------------------
118 updates for windows - should be at 130 ish by now, give or take a few 10's.

------------------------------------------------------------

Thank you for your reply. Answers to some of your questions:

A) The F: drive you see in my data is a 3TB external hard drive that we used to export a lot of data from the old computer to the new one. The stuff we thought we would need on the new computer was transferred to the external and then when the old computer was "retired" and I got the new one running, I hooked up the external to the new computer, which is still there and what you now see as the F: drive. I didn't really actually transfer much of anything from F: to C:, but there is a wide array of files on F: (pics, vids, word docs, excel docs, etc, etc) but when we need them we just access them off of F:, we don't transfer them to the C: drive.
B) If I recall correctly, I think the old computer had Outlook 2007 on it, I'm about 99% sure. The new one has Outlook 2010 on it. I'm already smelling a compatibility problem here just after typing that. Your thoughts?
C) If you mean how much we transferred onto C:, hardly anything, if at all. We transferred about 174GB worth of stuff onto the external from the old computer and that is now sitting next to the computer connected to it as the F: drive, so we didn't put any of that stuff "into" the computer, per se. The only thing I can definitely say went from the old computer C: directly into the new computer C: drive, instead of residing on F: drive, is when we did the import/export of the Outlook data files for each of us. Those were brought over using the F: drive but are on the new C: drive now in whatever folder Outlook would ordinarily put them in, I'm sure.

To your remark about the windows updates being lacking possibly, I just ran windows updates now and no criticals came up and 3 windows optional updates came up (KB2574819, KB2592687, and KB2709981) 2 more optional software updates came up, "PXI - Other Hardware - HID Compliand Device" and "Fresco Logic - Other Hardware - Fresco Logic xHCI (USB3) Root Hub"
What are your recommendations on these? Necessary or disregard?

I agree with your suspicions on it having something to do with Outlook, more specifically, probably our old exported Outlook data files from the old computer. Possibly a compatibility conflict? The question is, what can be done to eliminate the problem.

I will now go take some of your other advice that you wrote RE: the drivers, etc while I await your response. Thanks so much for your help. It is very much appreciated.

Jim.

 

[StingrayJG]

Three dumps pointing to athrx.sys:

athrx.sys                   Tue Feb  7 22:37:51 2012 (4F310D0F)
Atheros network adapter driver
http://www.carrona.org/drivers/driver.php?id=athrx.sys

Last updated in February last year - check the site for available updates to the device.
(note: The third dump references svchost.exe - shouldn't be a problem now, but I'll say it here for future reference if needed)

Tried to update this, keep getting told:
"The best driver for your device is already installed"
"Windows has determined the driver software for your device is up to date"
"Atheros AR5BWB222 Wireless Network Adapter"

(The version I have is 10.0.0.34)
I'll move on to some of your other recommendations...

 

[StingrayJG]

Just deleted wdcsam64.sys as advised above.
At least I think I did. I followed remove from registry directions. Remember I'm kind of a newbie here.
Have to go now but I'll advise on developments good, bad, or otherwise....
Thanks again!

 

[GeneralHiningII]

For future reference it's better to compile all your answers/questions and such into one post (forenote).

A) That's alright then, just checking in case because, especially with large amounts of data transfer, it can get a bit messy and may/may not corrupt the files (in rare cases I've seen before).

B) Outlook 2010 brought new features and discarded features of 2007, and so there may have been compatibility issues with your files. This may sound tedious, but to be sure none of your own files are screwed up -
On Outlook, Go to: File > Info > Prepare for Sharing
In that category, Check for Issues, then Check Compatibility.
Do this with all your files (which may take a long time) and record any errors.

Windows Updates:
Install the Fresco Logic USB3 Root Hub, as a few of your dumps did reference USB issues.

For the Atheros Driver:
Looking at the messages you've recieved, seems like you've tried to check for updates from Windows Device Manager. Windows does a (and I mean no offence) horrible job at finding new drivers for your devices - it'd be better to go to the manufacturer's site for any updates.
Atheros AR5BWB222
Link Removed
Update Version 10.0.0.221
Released on the 27th November 2012, a version 10 months newer than your current one.

As for the last driver:
Link Removed
Try finding your product there, and downloading the latest driver for any devices related to Western Digital.
Can I ask,
How did you uninstall it?

 

[StingrayJG]

General,
Once again thanks for all your help here.
I updated the Atheros driver manually (despite Windows insistence that the one I had was fine) I saw the newer driver here but it looked like the version number of the one I had was a higher version number so I believed it. Bahh! That's what I get for believing windows instead of you.
My C: and F: drive are both WD. The C: drive showed as being updated to best driver available (on WD site, too, not just Windows) The F: drive ended up with a slight update showing so I did it.
I could not do the Outlook directions you outlined above because once I clicked on File and Info, I saw no option anywhere for Prepare for Sharing. But one thing i did do was: I went to outlook.exe file directly, right clicked on properties, and checked off to run in compatibility mode for Windows XP-SP3 (I believe that's where we were with the old computer), and run as administrator. Since doing this, I have gone in to my wife's profile and put Outlook through it's paces, and then switched back to mine, then back to hers and done the same Outlook things repeatedly, and so far no freezes or hang ups have occurred, where prior to this, her session would've almost surely froze in the first few moments.
So, even though I don't have much more than a small sample size to go on, so far things have started to improve. I wonder if between the driver updates and what I just did with the Outlook settings, the problem may, dare I say, be solved. For now we're just going to have to continue to use the computer as normal to get a larger real-world sample size and see the results we get. I will report back to you on our progress, hopefully only with good news.

Thanks again, General. I really can't thank you enough for all the advice and guidance you gave me here. I hope what we have done here has resolved my issues. You're the best!
Jim.

 

[GeneralHiningII]

Well it looks like the problem has been solved!

It's my pleasure to help you, and if you do get another BSOD just post it again on to this thread!

 

[StingrayJG]

Well it looks like the problem has been solved!

It's my pleasure to help you, and if you do get another BSOD just post it again on to this thread!

I hope you're right, General. But I'm not going to consider it solved until at least a week of normal everyday usage with no more BSOD's has passed. It seems so hard to believe that this nightmare might possibly be over that I guess I just want to really be sure before I get too happy over it.. I'll give you a progress report.

Thanks again.

 

[StingrayJG]

General,
Sorry for the thread bump but just wanted to give you my promised progress report.
It's been approximately one week now of regular everyday use of the computer and there hasn't been one single BSOD/freezing episode for either one of us since the changes I made. Just wanted to thank you again and let you know so if you encounter someone having the same issue I just did with Outlook and compatibility, have them run in compatibility mode and as administrator. Once I did this my problems stopped in their tracks. (Not sure if the run as administrator is really needed but I'm leaving it for now.) Plus in the process of troubleshooting I have more updated drivers now too, bonus. It's so much nicer using this new computer now without the anxiety of wondering if it's going to freeze at any moment multiple times a day. Thanks again, you're great!
Jim.

 

[GeneralHiningII]

My pleasure, glad I could help!

(moo)