Blue Screens

My computer has had problems blue screening a lot lately. I've had issues with blue screens before but it was never this consistent. My boyfriend said he thinks there's something wrong with my motherboard? He had me clean the dust and stuff off the inside of my computer, and after that my computer seemed to work perfectly fine for a few days or so. However, today I was skyping someone on my computer and I fell asleep. When I woke up, my computer was displaying the blue screen again. A blue screen mainly seems to happen when I skype people. When I turn my computer back on, there's always something different my computer tells me. It told me there's something wrong with my webcam and it needs to be updated, and just random things like that. Now it's told me "You received this message because your universal serial bus (USB) driver has caused a stop error, also called a blue screen error. This type of error means the computer has shut down abruptly to protect itself from potential data corruption or loss."


I can't run the dds scanner thing without my computer crashing to a blue screen. I don't know what to do.

First we need to see what is triggering these events, to see if there's a common cause, it may be something pretty straight forward, in which case we may be able to help you.

However, analysing blue screen faults is not always too straight forward, and can be very difficult. Really it is best dealt with by someone who specialises in those kind of problems, our speciality here is Malware removals, so I may have to direct you to a specialist at another forum if your problem is beyond my ability to resolve.

Your computer usually logs any Blue Screen events, and stores the logs, so first I need to see if you have any logs on your computer that might help us.

Please download MiniToolBox to your Desktop.

• Double click MiniToolBox.exe to launch the program.
• Checkmark the following checkboxes:
  
  • List last 10 Event Viewer Errors
  • List Minidump Files
• Click Go to start the scan.
• When finished a log Result.txt will open.
• Please post it in your next reply.

MiniToolBox by Farbar Version: 30-11-2014
Ran by [removed] (administrator) on 05-12-2014 at 06:56:50
Running from "C:\Users\Danielle\Desktop"
Microsoft® Windows Vista™ Home Basic Service Pack 2 (X86)
Boot Mode: Normal
***************************************************************************

========================= Event log errors: ===============================

Application errors:
==================
Error: (12/04/2014 08:38:48 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (12/04/2014 08:26:04 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (12/01/2014 04:51:02 PM) (Source: Application Hang) (User: )
Description: The program HPAdvisor.exe version 2.3.4292.2709 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Problem Reports and Solutions control panel.
Process ID: d0c
Start Time: 01d00daf04a18ac7
Termination Time: 25

Error: (12/01/2014 04:43:16 PM) (Source: HP AdvisorUpdate) (User: )
Description: GetContentBlock() missing ID ATTENTION

Error: (12/01/2014 04:43:16 PM) (Source: HP AdvisorUpdate) (User: )
Description: GetContentBlock() missing ID ATTENTION

Error: (12/01/2014 04:43:16 PM) (Source: HP AdvisorUpdate) (User: )
Description: GetContentBlock() missing ID NOT_INSTALLED

Error: (12/01/2014 04:42:58 PM) (Source: HP AdvisorUpdate) (User: )
Description: GetContentBlock() missing ID ATTENTION

Error: (12/01/2014 04:42:58 PM) (Source: HP AdvisorUpdate) (User: )
Description: GetContentBlock() missing ID ATTENTION

Error: (12/01/2014 04:38:46 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (11/30/2014 09:11:41 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003


System errors:
=============
Error: (12/04/2014 08:38:49 PM) (Source: Service Control Manager) (User: )
Description: IPsec Policy AgentBFE

Error: (12/04/2014 08:38:49 PM) (Source: Service Control Manager) (User: )
Description: IKE and AuthIP IPsec Keying ModulesBFE

Error: (12/04/2014 08:38:49 PM) (Source: Service Control Manager) (User: )
Description: Parallel port driver%%1058

Error: (12/04/2014 08:38:49 PM) (Source: Service Control Manager) (User: )
Description: Computer Browser%%1060

Error: (12/04/2014 08:37:16 PM) (Source: EventLog) (User: )
Description: The previous system shutdown at 8:34:19 PM on 12/4/2014 was unexpected.

Error: (12/04/2014 08:26:04 PM) (Source: Service Control Manager) (User: )
Description: IPsec Policy AgentBFE

Error: (12/04/2014 08:26:04 PM) (Source: Service Control Manager) (User: )
Description: IKE and AuthIP IPsec Keying ModulesBFE

Error: (12/04/2014 08:26:04 PM) (Source: Service Control Manager) (User: )
Description: Parallel port driver%%1058

Error: (12/04/2014 08:26:04 PM) (Source: Service Control Manager) (User: )
Description: Computer Browser%%1060

Error: (12/04/2014 08:24:32 PM) (Source: EventLog) (User: )
Description: The previous system shutdown at 5:56:15 PM on 12/4/2014 was unexpected.


Microsoft Office Sessions:
=========================
Error: (12/04/2014 08:38:48 PM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (12/04/2014 08:26:04 PM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (12/01/2014 04:51:02 PM) (Source: Application Hang)(User: )
Description: HPAdvisor.exe2.3.4292.2709d0c01d00daf04a18ac725

Error: (12/01/2014 04:43:16 PM) (Source: HP AdvisorUpdate)(User: )
Description: GetContentBlock() missing ID ATTENTION

Error: (12/01/2014 04:43:16 PM) (Source: HP AdvisorUpdate)(User: )
Description: GetContentBlock() missing ID ATTENTION

Error: (12/01/2014 04:43:16 PM) (Source: HP AdvisorUpdate)(User: )
Description: GetContentBlock() missing ID NOT_INSTALLED

Error: (12/01/2014 04:42:58 PM) (Source: HP AdvisorUpdate)(User: )
Description: GetContentBlock() missing ID ATTENTION

Error: (12/01/2014 04:42:58 PM) (Source: HP AdvisorUpdate)(User: )
Description: GetContentBlock() missing ID ATTENTION

Error: (12/01/2014 04:38:46 PM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (11/30/2014 09:11:41 PM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003


CodeIntegrity Errors:
===================================
Date: 2014-07-16 12:57:31.004
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

Date: 2014-07-16 12:57:30.879
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

Date: 2014-07-16 12:57:30.706
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

Date: 2014-07-16 12:57:30.524
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

Date: 2014-07-16 12:57:30.374
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

Date: 2014-07-16 12:57:30.244
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

Date: 2014-07-16 12:57:30.118
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

Date: 2014-07-16 12:57:29.998
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

Date: 2014-07-16 12:57:29.878
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

Date: 2014-07-16 12:57:29.757
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\mwac.sys because the set of per-page image hashes could not be found on the system.

========================= Minidump Files ==================================

C:\Windows\Minidump\Mini112914-01.dmp
C:\Windows\Minidump\Mini113014-01.dmp
C:\Windows\Minidump\Mini113014-02.dmp
C:\Windows\Minidump\Mini113014-03.dmp
C:\Windows\Minidump\Mini120114-01.dmp
C:\Windows\Minidump\Mini120414-01.dmp
C:\Windows\Minidump\Mini120414-02.dmp

**** End of log ****

OK, I need you to attach a couple of the minidump files to your next post, that your computer created when it blue screened.

C:\Windows\Minidump\Mini120414-01.dmp
C:\Windows\Minidump\Mini120414-02.dmp

You'll need to rename them to ....

C:\Windows\Minidump\Mini120414-01.txt
C:\Windows\Minidump\Mini120414-02.txt

... or the forum software will not allow you to attach them.

If you have problems attaching those files, please let me know and I'll post instructions.

How do I change it to a text file?

Just right click on the file, and select rename then type in the little box that pops up.

By default the file type is usually not highlighted in the box, so just click in the box and move the cursor across with the -> key until you can edit the file type.

When you do, you'll get a prompt from Windows telling you not to do it because it could make the file unusable, but you can ignore that.

I changed the files to .txt like you said. When I went to attach them a box popped up that said, "You don't have permission to open this file. Contact the file owner or an administrator to obtain permission."

OK, let's see if we can get the information we need another way, this is not quite as good as the first way, since we don't get as much information, but it should enable us to see if there is a common cause for your blue screen events.

Please download and install Blue Screen View

• Right click on BlueScreenView and select Run as administrator to launch the program.
• Scroll down the entries in the top pane of the interface to find .... Mini120414-01.dmp .... then click on it to select it.
  
  • Click Edit > Select all
  • Click File > Save selected items
  • Save as Minidump 1.txt to your Desktop.
• Repeat the steps above for .... Mini120414-02.dmp .... saving the file this time as Minidump 2.txt.
• Please post the contents of Minidump 1 and Minidump 2

I've already changed them to .txt files though. They're not showing up in the top pane on the interface because they're not .dmp anymore. Should I rename them back to .dmp? I'm sorry I'm making this so complicated.

Yes, rename them to .dmp files and Blue Screen View should find them proving they're still in the C:\Windows\Minidump folder.

Don't worry about the difficulties, I'm sure we'll be able to find a way through them.

Well when I went to rename them I pretty much just added .dmp to their name. They're still text files and Blue Screen View isn't recognizing them.

If you've renamed them properly, they should now be ....

C:\Windows\Minidump\Mini120414-01.dmp
C:\Windows\Minidump\Mini120414-02.dmp

.... is that how they are named, and are they in the Minidump folder ?

Did you shut down Blue Screen View while you re-named them, or did you leave it open ?

If you left it open, shut it down, then start it again and see if it now sees the files.

This is going to be hard to explain. So like, when I went to change them to .txt when you told me to do, the name of the file was highlighted and the .dmp part was highlighted. When I went back to change them back to .dmp again, when I hit rename the extension was no longer there, just the file name. So basically all I really did was just add .dmp to the end of the file and it didn't actually change the file back from a text file. Does that make sense? And yes I had Blue Screen View shut down while I did that.

Can you see the file extension name when you normally view the file ? (ie when you're not renaming it)

If you can't, then please do the following ...

• Click Start > Control Panel > Appearance and Personalization > Folder Options
• Click the View tab
• Ensure that Hide extensions for known file types is not checked (does not have a tick in the box next to it)
• Click OK

Now, check the file names again, and ensure that they say ...

Mini120414-01.dmp
Mini120414-02.dmp

... and nothing else.

Alright I got it. So about the blue screen view. After I highlight the minidump, and I go to the edit tab then click select all, it highlights all the rest of the minidumps. Is it supposed to do that?