Always a BSOD on shutdown

Hi Folks,
I'm new to Win7 and not as familiar with it's tools but believe I have what info I seen is needed for help here. Thanks in advance for the help!

Machine/Model: Toshiba Satellite / A215-S4757
Processor: AMD Turion-64
BIOS: Toshiba V2.30 1/15/2010 (Updated prior to the Win7 installation)
SMBIOS: 2.4
OS: 64Bit Win7 Ultimate SP-1
Drivers: Current
Anti virus/malware software: Microsoft Security Essentials
Malwarebytes
CCleaner (latest versions)
ESET

Symptoms: Won't shut down (BSOD always reported on next startup)

What I've done so far: 1. recently updated all video, (etc) drivers because of these problems
2. Run CHKDSK: 1st time 3 files fixed. Clean after that
3. Ran all of the above anti virus/malware/trojan software Results were clean
4. Ran BlueScreenView (reports shown below)
Out of 13 BSOD's there were...
- ntoskrnl.exe 6
- hal.dll 5
- athrx.sys 1
- atikmag.sys 1
5. MEMTEST+ shows no memory errors
6. Ran MiniToolBox.exe (system error section report below)

Notes:
- This is a dual-boot LINUX machine on a smaller partition, but it always has been so with no problems.

- This all started (according to the WIN7 Reliability Monitor software) on March 23rd, but that doesn't coincide with any application or driver installs. I don't know about MS updates.

BlueScreenView Reports on the four drivers listed above:

ntoskrnl.exe
==================================================
Dump File : 053012-17487-01.dmp
Crash Time : 5/30/2012 7:10:33 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x1000009f
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000258
Parameter 3 : fffffa80`0175e660
Parameter 4 : fffff800`00b9c510
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+8208a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\053012-17487-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 455,272
==================================================

hal.dll
==================================================

Dump File : 053112-16645-01.dmp
Crash Time : 5/31/2012 11:51:17 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0263c8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+f768
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+4b09bc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\053112-16645-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================
athrx.sys
==================================================
Dump File : 053112-16723-01.dmp
Crash Time : 5/31/2012 8:27:42 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`025cda10
Parameter 3 : fffff800`04a48518
Parameter 4 : fffffa80`01d60190
Caused By Driver : athrx.sys
Caused By Address : athrx.sys+55057
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\053112-16723-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 803,728
==================================================

atikmdag.sys
==================================================
Dump File : 052812-17487-01.dmp
Crash Time : 5/28/2012 7:38:35 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`025cf060
Parameter 3 : fffff800`00b9c518
Parameter 4 : fffffa80`02bdfe10
Caused By Driver : atikmdag.sys
Caused By Address : atikmdag.sys+4bde00
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052812-17487-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 803,728
==================================================
OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

MiniToolBox.exe reports both application and hardware errors but I don't know how reliable this is or if it points to another problem.

System errors:
=============
Error: (05/31/2012 11:51:32 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: LOCAL SERVICE)
Description: A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: 3
Error Type: 256
Processor ID: 1

The details view of this entry contains further information.

Error: (05/31/2012 11:51:32 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: LOCAL SERVICE)
Description: A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: 3
Error Type: 10
Processor ID: 1

The details view of this entry contains further information.

Error: (05/31/2012 11:51:32 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: LOCAL SERVICE)
Description: A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: 3
Error Type: 9
Processor ID: 1

The details view of this entry contains further information.

Error: (05/31/2012 11:51:29 AM) (Source: Service Control Manager) (User: )
Description: The following boot-start or system-start driver(s) failed to load:
Lbd
SBRE

Error: (05/31/2012 11:51:24 AM) (Source: Microsoft-Windows-WLAN-AutoConfig) (User: SYSTEM)
Description: WLAN Extensibility Module has failed to start.

Module Path: C:\Windows\system32\athExt.dll
Error Code: 126

Error: (05/31/2012 11:51:22 AM) (Source: BugCheck) (User: )
Description: 0x00000124 (0x0000000000000000, 0xfffffa800263c8f8, 0x0000000000000000, 0x0000000000000000)C:\Windows\Minidump\053112-16645-01.dmp053112-16645-01

Error: (05/31/2012 08:27:52 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: LOCAL SERVICE)
Description: A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: 3
Error Type: 10
Processor ID: 1

The details view of this entry contains further information.

Error: (05/31/2012 08:27:52 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: LOCAL SERVICE)
Description: A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: 3
Error Type: 10
Processor ID: 1

The details view of this entry contains further information.

Error: (05/31/2012 08:27:52 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: LOCAL SERVICE)
Description: A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: 3
Error Type: 9
Processor ID: 1

The details view of this entry contains further information.

Error: (05/31/2012 08:27:50 AM) (Source: Service Control Manager) (User: )
Description: The following boot-start or system-start driver(s) failed to load:
Lbd
SBRE
OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

We need to know more about your BSODs...

Download BlueScreenView (in Zip file)

No installation required.

Unzip downloaded file and double click on BlueScreenView.exe file to run the program and When scanning is done, go to Edit > Select All.

Then go to File > Save Selected Items, and save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Compliments of Broni

Thanks for the reply but perhaps this is an automated response?
I thought I had all of the information in my initial post.

Glad to provide more info if needed.

Have had any more recent BSOD's I only see three, and if so can you run Blue screenview.

Have you installed any new software or drivers for any hardware in your machine?

Has this lap top been cleaned out with a can of air, because Heat can cause BSOD's even when shutting down.

Thanks for the time!

Question #1:
These four drivers listed above are the only ones ever listed and these reports are dated within the last three days. If I reboot the machine thirty times it would create thirty crashes but these are the only drivers ever listed, and most are even listed at the same offset each time, although that sometimes varies. Today?

Todays BlueScreenView reports have ntoskrnl.exe and athrx.sys.

ntoskrnl.exe
==================================================
Dump File : 060112-18361-01.dmp
Crash Time : 6/1/2012 3:41:16 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`025be060
Parameter 3 : fffff800`04a48518
Parameter 4 : fffffa80`05e01690
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060112-18361-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 798,920
==================================================

athrx.sys
==================================================
Dump File : 060112-17877-01.dmp
Crash Time : 6/1/2012 7:16:19 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`025d4060
Parameter 3 : fffff800`00b9c518
Parameter 4 : fffffa80`0308b570
Caused By Driver : athrx.sys
Caused By Address : athrx.sys+55057
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060112-17877-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 801,680
==================================================

Question #2:
As stated I only installed new drivers after this started happening because I thought outdated ones might be causing it. The new drivers did not solve the problem.

Question #3:
I have not had the machine apart since last (2011) summer when I installed a new HD, and although I picked out dust from the fans and cooling-tubes, I did not use air to do it but plastic tweezers. It's run fine since then until very recently. I don't know which utilities to use to check the temperature of the CPU, etc unless there is one built into Ultimate.

Recommend one?
Thanks and Regards

Please perform the following, so that we can get the exact specs of your computer. This will better assist us in helping you more.

Publish a Snapshot using Speccy

The below is for those who cannot get online

Please take caution when attaching a text file to your post if you cannot copy/paste the link to your post, you will need to edit it to make sure that your Windows Key is not present.

The file mentioned pertains to your wireless network card driver

The cause of your problem is likely to be that there are 3 (at least) antivirus applications running on the system:

• MSE
• AdAware
  

  Error: (05/31/2012 11:51:29 AM) (Source: Service Control Manager) (User: )
  Description: The following boot-start or system-start driver(s) failed to load:
  Lbd
  SBRE

• ESET

There should not ever be more than one active antivirus application running on the system ... or you risk diminished security and all sorts of problems such as the one you are experiencing.

Uninstall AdAware (this could be a nightmare to get rid of ... ) and ESET, leaving only MSE. Restart the system after uninstalling each application. Let us know how the system behaves after doing that. We may have to take further steps to completely remove the remaining remnants of the applications.

I uninstalled Lavasoft a long time ago for the reasons you specified and you're right. That last driver in the MiniToolbox scan is still there so I'll dig it out. That should stop the SBRE problem in the report.

I uninstalled ESET at your request and rebooted. No change. But ESET was an application I installed and ran after these troubles started.

In the BlueScreenView (BSV) the drivers listed are from the Atheros wireless driver (athrx)and (I think) the ATI graphics adapter. Both of those are fairly new (since the trouble started) and since I didn't know to do a BSV before they were installed, I don't know if they were misbehaving. There aren't enough dumps to see what was happening in mid-march, when this all started.

I'm gonna look into the Speccy publication but have a natural issue with too much personal information out in the ether. I'll have to noodle over that for a bit and learn how it works.

Thanks for the support folks.

There will not be any personal information in the speccy report, and as a courtsy, I will post mine so you can see the output.

http://speccy.piriform.com/results/00hs5YB2nYs84PObttEYnJs

Ah, as I save it as a txt there was, of course, the serial number. So I thought it would be in the Speccy output as well until I looked at a locally saved one.

http://speccy.piriform.com/results/4dCJ62EOKbLziV7J1DmIIfw

Is your wireless mouse connected when you shut down the lap top? If so remove the USB Mouse prior to shutdown, and see if the bsod's stop.

External mouse results:

1. I've shutdown the machine 9 times by first removing the external mouse dongle.

2. Until the 10th shutdown it had no BSOD's and then it returned.

3. Then I simply left the external mouse out of the picture and used the touchpad only for three more shutdowns.

BSOD's are back and happen every time.

BlueScreenView reports
- Two hal.dll crashes and
- One ntoskrnl.exe crash

So it's back to crashing every time on shutdown even without the external mouse.

I suspected a potential problem with the CPU except that the the Ubuntu 12.x linux image has no problems whatsoever.

Thanks for the continuing support.

What else do you have plugged in during computer use?

Only the power supply is attached. Occasionally I'll attach it to a printer via USB but not often.

try leaving the printer attached, and see if it BSOD's.