Solved Various BSODs are back, not consistent, seems random

[lian9]

I made a thread a few months ago back in late June I think, and was able to get help with BSODs I was having, and while I think the frequency of them has decreased, the system is still not fully stable. I have been busy lately and just dealing with them, but it's time I take care of this nonsense once and for all.

I can't really say what causes them, and they seem to be happening almost completely randomly; sometimes when playing a game, other times when I open the internet browser, once shortly after booting the computer, etc. The BSODs have been things from irql not less or equal, page fault in non paged area, etc. The attached file should hopefully have all the information you need.

I'll link the old thread (sevenforums.com/crashes-debugging/236320-numerous-bsod-playing-games-recently-error-0xd1-6.html), but it's quite long, so to sum up the important parts, I did memtest89+ which passed and ultimately ended up replacing the motherboard. I then basically reinstalled everything from scratch after getting the new motherboard. My system specs are up to date.

 

[koolkat77]

Checked your latest dump which is caused by usbport.sys

Follow steps mentioned in this tutorial for a possible fix:
http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html

Post back results

 

[lian9]

I followed the steps shortly after you posted, but just recently I got a BSOD, this time saying BAD POOL CALLER. I attached the zip. I had opened a game called minecraft and it crashed after about 2 minutes, there weren't any issues as the game was running, it just crashed.

 

[koolkat77]

usbport.sys

This is also hardware and sometimes caused by a faulty BIOS but lets check to see what you have set for Power Settings first. Follow steps in this tutorial:
:ar: http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html

 

[lian9]

I'm using high performance power settings, usb selective speed setting is enabled. Should it be disabled?

 

[koolkat77]

Yes

 

[lian9]

Ok thanks. I'll let you know how things go.

 

[koolkat77]

You're welcome.
Take your time.

 

[lian9]

Had another one just now, uploaded the zip. Assuming it's motherboard related, here's the website for it: ASUS - Motherboards- ASUS P8Z77-V LX

 

[koolkat77]

Still shows USBPORT.sys as the problem
Do what the quote below asks you to.

Possible fix| Go to Device Manager > Expand the USB list > Uninstall every driver (not device) and Reboot Windows.
Let Windows detect them and reinstall them.

• What kind of USB Devices to you have attached to your hub?

 

[lian9]

I put a picture of my usb list in the attachment. To make sure I don't screw something up, do I just right click on each one and go to properties, the driver tab, and then click uninstall? Thanks.

The only usb device attached is a usb extender with a wireless usb for the wireless keyboard and mouse.

 

[koolkat77]

Yup, just uninstall the driver not device.
View attachment 233083

 

[lian9]

Ok thanks, I have done that and I'll let you know how it goes.

 

[koolkat77]

Thanks
Take your time

 

[lian9]

Had another one just now zip attached.

 

[koolkat77]

Shows problems with DirectX.
Run the DirectX Diagnosis tool
:ar: Run DirectX Diagnostic Tool

 

[lian9]

I ran it and it says no problems found for each tab in the notes box at the bottom. I'll screenshot certain/all pages for you if you'd like.

 

[koolkat77]

Hmm. That may or may not be the true cause for your BSoDs.
We'll have to enable driver verifier now.

Its used to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

 

[lian9]

Ok, I'm running it now, no crashes yet. Is it OK if I shut the computer down for the night and, or should I just leave it running over night?

 

[koolkat77]

Leave it running