Random BSOD: Interrupt Exception Not Handled

BlairD · 18 Jun 2012

So I built this computer recently and it blue screens at what appears to be random times. Sometimes it happens when I'm using the internet or it happens right as my computer starts up. The blue screen says INTERRUPT_EXCEPTION_NOT_HANDLED at the top and at the bottom it says STOP: 0x0000003D. I also have my OS installed on my SSD. I attached a .rar with the dump files and the Perfmon report. My specs are:

OS: Windows 7 Professional 64 bit
CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Motherboard: ASUSTeK Computer INC. P8Z68-V PRO GEN3
Ram: 8 GB
GPU: AMD Radeon HD 7950
HDD: Hitachi HDS721010DLE630 ATA Device
SSD: INTEL SS DSC2CW120A3 SCSI Disk Device

Thanks.

usasma · 19 Jun 2012

You've got 25 memory dumps from 15 - 18 June 2012 (4 days!)
Wow!
I'm only going to run the last 10 and will see what I get......

Actually I haven't seen a whole lot of problems with Intel SSD's, but here's my spiel on SSD's anyway:

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.

SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
NOTE: For Vista, read these notes:

Read these notes for installing Vista SP1: Learn how to install Windows Vista Service Pack 1 (SP1)
Read these notes for installing Vista SP2: Learn how to install Windows Vista Service Pack 2 (SP2)

5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?
Also, check out this troubleshooting link from Microsoft: Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2

I have had limited success in installing updates/Service Packs when using a "clean boot". I suspect that I'm just bypassing the problem - and that it can come back to bite me in the butt later on.

3 memory dumps in the WER section of MSINFO32 show issues with your Marvell controller (on your motherboard). Older Marvell controllers may have issues with SSD's. Please do the following:
- switch the SSD to a non-Marvell controller
- update the Marvell controller drivers (even if the SSD isn't connected to it) from the manufacturer's website

All memory dumps are STOP 0x3D and all blame the Marvell controller also (mv91xx.sys)
Please follow the advice in the previous paragraphs.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


AtihdW76.sys    Thu Feb 23 07:30:12 2012 (4F463154)
HECIx64.sys     Tue Oct 19 19:33:43 2010 (4CBE2AD7)
RTKVHD64.sys    Tue Nov 23 05:14:08 2010 (4CEB93F0)
amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
asmthub3.sys    Wed Sep 14 03:36:19 2011 (4E705973)
asmtxhci.sys    Wed Sep 14 03:36:09 2011 (4E705969)
aswFsBlk.SYS    Tue Mar 06 19:01:31 2012 (4F56A55B)
aswMonFlt.sys   Tue Mar 06 19:01:51 2012 (4F56A56F)
aswSP.SYS       Tue Mar 06 19:04:03 2012 (4F56A5F3)
aswSnx.SYS      Tue Mar 06 19:04:05 2012 (4F56A5F5)
aswTdi.SYS      Tue Mar 06 19:01:56 2012 (4F56A574)
aswrdr2.sys     Tue Mar 06 19:02:19 2012 (4F56A58B)
atikmdag.sys    Thu Apr 05 21:48:25 2012 (4F7E4B69)
atikmpag.sys    Thu Apr 05 21:10:44 2012 (4F7E4294)
btath_a2dp.sys  Mon Feb 14 20:47:47 2011 (4D59DB43)
btath_bus.sys   Thu Jun 24 02:17:43 2010 (4C22F887)
btath_flt.sys   Thu Jun 24 02:17:38 2010 (4C22F882)
btath_hcrp.sys  Tue Jun 29 05:30:43 2010 (4C29BD43)
btath_lwflt.sys Mon Sep 13 04:26:54 2010 (4C8DE04E)
btath_rcp.sys   Thu Jun 24 02:17:21 2010 (4C22F871)
btfilter.sys    Tue Mar 08 01:15:22 2011 (4D75C97A)
dump_mv91xx.sys Fri Aug 27 05:49:22 2010 (4C778A22)
dump_mvxxmm.sys Fri Aug 27 05:49:03 2010 (4C778A0F)
e1c62x64.sys    Tue Sep 21 17:34:15 2010 (4C9924D7)
jraid.sys       Tue Aug 10 05:28:44 2010 (4C611BCC)
mv91xx.sys      Fri Aug 27 05:49:22 2010 (4C778A22)
mvxxmm.sys      Fri Aug 27 05:49:03 2010 (4C778A0F)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061712-15600-01.dmp]
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Debug session time: Sun Jun 17 09:31:13.998 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:15.293
BugCheck 3D, {fffff80000b9c070, 0, 0, fffff880010fe78e}
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff800`00b9c070 00000000`00000000 00000000`00000000 fffff880`010fe78e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061712-9874-01.dmp]
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Debug session time: Sun Jun 17 09:28:26.812 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:06.107
BugCheck 3D, {fffff80000b9c070, 0, 0, fffff8800108e78e}
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff800`00b9c070 00000000`00000000 00000000`00000000 fffff880`0108e78e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061712-9984-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jun 17 09:08:33.600 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:15.896
BugCheck 3D, {fffff88002ffd060, 0, 0, fffff880010bc78e}
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff880`02ffd060 00000000`00000000 00000000`00000000 fffff880`010bc78e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061812-23556-01.dmp]
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Debug session time: Mon Jun 18 11:06:48.186 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:15.108
BugCheck 3D, {fffff880080ddc90, 0, 0, fffff880010f578e}
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff880`080ddc90 00000000`00000000 00000000`00000000 fffff880`010f578e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061812-24211-01.dmp]
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Debug session time: Mon Jun 18 11:11:09.958 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:51.253
BugCheck 3D, {fffff8800aa800a0, 0, 0, fffff8800114a78e}
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  CCC.exe
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff880`0aa800a0 00000000`00000000 00000000`00000000 fffff880`0114a78e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061812-6739-01.dmp]
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Debug session time: Mon Jun 18 11:22:23.108 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:29.403
BugCheck 3D, {fffff80000b9c070, 0, 0, fffff880010cf78e}
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff800`00b9c070 00000000`00000000 00000000`00000000 fffff880`010cf78e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061812-6910-01.dmp]
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Debug session time: Mon Jun 18 11:37:41.831 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:21.752
BugCheck 3D, {fffff8800b745fa0, 0, 0, fffff880010e478e}
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  where.exe
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff880`0b745fa0 00000000`00000000 00000000`00000000 fffff880`010e478e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061812-7394-01.dmp]
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Debug session time: Mon Jun 18 11:09:46.320 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:15.615
BugCheck 3D, {fffff80000b9c070, 0, 0, fffff8800107f78e}
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff800`00b9c070 00000000`00000000 00000000`00000000 fffff880`0107f78e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061812-8626-01.dmp]
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Debug session time: Mon Jun 18 11:19:31.344 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:05.265
BugCheck 3D, {fffff80000b9c070, 0, 0, fffff880010ce78e}
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff800`00b9c070 00000000`00000000 00000000`00000000 fffff880`010ce78e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061812-9438-01.dmp]
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Debug session time: Mon Jun 18 11:20:21.833 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:16.755
BugCheck 3D, {fffff8000421a070, 0, 0, fffff8800115978e}
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff800`0421a070 00000000`00000000 00000000`00000000 fffff880`0115978e
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

BlairD · 20 Jun 2012

I think after updating a lot of drivers, the problem may be fixed now. This is my first computer I've built so I really appreciate all the help.

But I have one quick concern. Even after installing Windows 7 SP1, a few automatic updates still give me Error 800B0100. I tried to run the System Update Readiness Tool, but the updates still don't work. What do you suggest I do?

Once again, thanks for all the help!

usasma · 20 Jun 2012

Please zip up and upload the SURTool logfile. It's located at C:\Windows\Logs\CBS\CheckSUR.log
Found it in this article: Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2

It describes the error that you're having as being a file without the appropriate signature. I'm not sure how to fix that, but once we identify it there's several things that we can try.

First, try this troubleshooter/fixit tool: Fix the problem with Microsoft Windows Update that is not working

BlairD · 26 Jun 2012

Thanks for the help and sorry for not responding in a while. Things appear to be working a lot better now, so I'm going to set the thread to solved. Thanks again.