BSOD BCCode 1a

[iandxb]

Hi Guys,
I recently installed windows 7 on a new computer build but have found it crashes a couple of times a day with the Bluescreen error. Any help would be greatly appreciated.
The OS is Windows 7 Professional and the hardware bar the hardrive and case is new. The hardware spec is as follows:
Radeon HD6870 2GB DDR5 Graphics card
Intel i7-2600k processor
Patriot 2x4gb DDRIII 1600MHZ
XFX 750W PSU
ASUS P8Z68-V Motherboard.

Attached is the system health report and BSOD Dump & System File Collection report. I noticed it says 'unknown' device drivers are missing in the system health report.

The initial problem contained the following information:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041284
BCP2: 000007FEFA0E5001
BCP3: 0000000000000000
BCP4: FFFFF70001080000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\010412-22542-01.dmp
C:\Users\user\AppData\Local\Temp\WER-25599-0.sysdata.xml


However, the last problem involved
Appcrash
explorer.exe
6.1.7601.17567
4d672ee4
SHLWAPI.dll
6.1.7601.17514
4ce7c9ab
c0000005

Thanks in advance for any help.

 

[usasma]

App crashes are different from BSOD's. I'd suggest using the free Shell Extension Viewer ( ShellExView - Shell Extension Manager For Windows ) to selective disable 3rd party extensions to see if there's an issue with any of them.

As for the BSOD's, here's what I found:

perfmon reports an unknown device does not have it's drivers installed
MSINFO32 shows this device as this:

Not Available USB\VID_0CF3&PID_3000\6&DF2EE03&0&7 The drivers for this device are not installed.

My research indicates that this is an Atheros AR3011 Bluetooth device. Please visit the Manufacturer's website and download/install drivers for it.

Only 55 updates installed since SP1. Most systems have 60-70 or more. Please visit Windows Update to ensure that you have all available updates

The WER section of MSINFO32 reports 2 BSOD's
- a STOP 0x1A blaming the kernel (core file of the OS)
- a STOP 0x3B blaming your ATI video driver

Without any other info, I'd suggest:
- updating your video drivers from the ATI website
- updating your chipset drivers from the PC/mobo Manufacturer's website

If that doesn't fix things, then I'd suggest running the free diagnostics/stress tests on this page: Hardware Diags
Please post back with the results of the tests.
Good luck!
BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010412-22542-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan  3 22:03:46.650 2012 (UTC - 5:00)
System Uptime: 0 days 10:16:31.665
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
Bugcheck code 0000001A
Arguments 00000000`00041284 000007fe`fa0e5001 00000000`00000000 fffff700`01080000
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010312-17862-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan  3 11:46:04.477 2012 (UTC - 5:00)
System Uptime: 0 days 2:22:30.492
Probably caused by : atikmdag.sys ( atikmdag+90817 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+90817
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`056b4817 fffff880`07ada7b0 00000000`00000000
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[iandxb]

Thanks a lot for the help! Will follow the instructions and see how it runs over the next 24 hours. If it crashes again over this time I will run the test mentioned and post the results tomorrow.
thanks again!
PS I don't have an atheros bluetooth device so not sure what else it could be.

 

[usasma]

BlueTooth is built into your ASUS mobo.
Update the drivers from the Asus support website

 

[iandxb]

thanks again for the reply.
i disabled all non microsoft shell extensions as i don't need them and would rather just eliminate the chance any of them did cause a crash.
windows has updated further and i updated the chipset driver and installed the bluetoothdriver from the asus website which has got rid of the 'unknown driver missing' in system report so that was the missing driver.
i have then left the computer running to see how the changes worked.
so far this seems to have worked; i have had no crashes for almost 24 hours and have still yet to have a crash.
just now though i had an application failure;

Problem signature:
Problem Event Name: APPCRASH
Application Name: Skype.exe
Application Version: 5.6.59.110
Application Timestamp: 4e96c2e0
Fault Module Name: Skype.exe
Fault Module Version: 5.6.59.110
Fault Module Timestamp: 4e96c2e0
Exception Code: c0000005
Exception Offset: 00ad5b64
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


i'm not sure if this is an application specific issue to Skype or whether its connected to the rest? it just forced the application to close and didn't actually crash the computer.

 

[usasma]

Sorry, but I don't use Skype.
My only suggestion for that is to:
- download a fresh copy of Skype
- uninstall the current copy of Skype
- install the freshly downloaded copy of Skype
- monitor for further problems.

 

[iandxb]

no crashes since the original fix with the bluetooth driver.
thank you very much!!!