Random BSOD's - USB_DRIVER_BUGCODE and SYSTEM_SERVICE_EXCEPTION

[Roy Renard]

Hello, so I've been getting several crashes and BSOD's for no particular reason for the last couple of weeks: while watching Youtube videos, browsing the web, listening to music or even just being in the desktop. In fact, it took me about 8, or so, attempts to write down this thread, getting the SF Diagnostic Tool file I needed and post this thread, because my computer repeatedly crashed during this process. Whenever I get a BSOD, the reason it normally lists is either: USB_DRIVER_BUGCODE or SYSTEM_SERVICE_EXCEPTION, but I just got one that said BAD_HEADER.
The BSODs, crashes and sudden restarts were a problem that I didn't have to deal with for about 8 or 9 months. I'll provide my background for any information that might be useful for finding a cause or solution: during June of 2013, I used to get repeated BSOD’s, crashes and sudden restarts only while playing games such as Age of Empires II HD, so I made a thread about it in this same forum. One of your members kindly helped me out of the problem throughout a process that lasted for about 4 months until my computer stopped crashing definitely, or so I thought.
It was about a month ago that I started getting these BSOD’s again, but just sparingly, so I didn’t take action until now, that I started getting at least one BSOD a day for no particular reason. Also, since that time 8 months ago that my computer ceased to crash (after performing a Repair Install suggested by the member that helped me), I started getting some other problems, such as my laptop not going into Sleep Mode while the lid is closed or getting a ton of “Validation” notifications and messages about getting Windows Original, which doesn’t make sense, because Windows 7 has been originally installed ever since I bought this laptop, about 3 years ago.
So, anyways, I’ll provide here the SF Diagnostic Tool .zip file that you ask for and thank you in advance for your help!

 

[Arc]

Hi Roy Renard.

Download and install Intel® Graphics Drivers for Intel® Core™, Pentium® and Celeron® Processors.

Upload the list of all the third party drivers Using NirSoft DriverView :

• Download and execute Driverview
• View > Hide Microsoft Drivers
• Edit > Select all
• File > Save Selected Items
• In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
• Zip the .txt file and upload it.

 

[Roy Renard]

Ok, so I installed the drivers required and here is the .zip file with the Driverview data. Thanks a lot!

 

[Arc]

Not finding any fair reason for a Bugcode USB Driver.

Uninstall Intel(R) Turbo Boost.

And disable bluetooth, it is is not very necessary.

Then observe the situation. Let us know how it is working after doing those. If it BSODs again, report us with the data.

 

[Roy Renard]

Alright, I can't really find Intel(R) Turbo Boost and uninstall it, but I'll be searching for it. I already disabled Bluetooth, as well. I'll make sure to report any new BSOD's asap.
Thanks a lot for your help!

 

[Roy Renard]

Well, BSOD's are still happening, so I'll leave the new dump files here. Thanks in advance.

 

[Arc]

[COLOR=Red]BugCheck 1000007E[/COLOR], {ffffffffc0000005, fffff8000336b078, fffff880031a19a8, fffff880031a1200}

Probably caused by : ntkrnlmp.exe ( nt!CmpRemoveKeyHash+4c )

Followup: MachineOwner
---------

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDhttp://carrona.org/bsodindx.html#top
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Let us test for the items other than the striked out ones.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Search for anu possible BIOS update from HP.

Remove any USB device that is attached with the computer.

Make it sure that windows is properly up-to-date.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest86+ does not show any error. enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Roy Renard]

Sorry for the extremely late response, but it's been somewhat difficult for me to successfully perform the different procedures. My computer has been crashing about 10-20 times daily now and my cooling base broke, so I've been unable to do the Memtest86+ step, since my computer overheats fairly easily without a cooling base. I saved up for a new one and am about to buy it as soon as possible, so I hope this thread doesn't get closed because of inactivity.
I'll try to post the info you required as soon as possible, as well.
Thanks for understanding!

Edit: I updated the BIOS from F.16 to F.32, which is, according to the HP site, the latest BIOS version available for my model.
I also tried out the Graphics Card stress test with Furmark, but the computer crashed/froze in the middle of the test.
Everything seems to provoke a crash right now and my computer looks like it's starting to have problems turning on after a crash occurs, since it repeatedly turns on and off (for about 5-10 times) until it finally starts up.

 

[Arc]

Change the cooler first, and then go for any stress test. Otherwise it may go fatal.

 

[Roy Renard]

Well, I finally got to run Memtest. During the first try, the computer shut down just as the Memtest screen showed up and during second try, it only took 2 minutes for it to stop because an error showed up. So it seems that there's some kind of problem there. What should I do next?

 

[Arc]

What should I do next?

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

For a bad RAM, you need to change it. For a bad slot, dont use it anymore.

 

[Roy Renard]

But that means I have to physically open my computer, right?

 

[Arc]

Yes.