5 BSOD within 20mins. USBPORT.SYS, CLFS.SYS, ACPI.SYS

[brianlt]

Hello everyone,

Two hours ago a got a BSOD during a League of Legends game. I restarted my computer then continued to play LoL. Within the few minutes of being on LoL, I got my second BSOD. As I tried to restart my computer again and opened LoL, I immediately got a BSOD. I restarted, and during bootup, I got a BSOD. Restart, another BSOD during bootup.

During some of the blue screens, I noticed that the minidump files weren't being collected. I did not see the info for each BSOD screen because I forgot to check. I know the last two BSOD were CLFS.SYS and ACPI.SYS.

Can I get some help diagnosing the problem? Thanks in advance!

 

[richc46]

Welcome
Sounds like hardware issue. Lets rule out drivers first, to be sure
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" (without the quotes) 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

 

[brianlt]

Thanks for the reply Richard,

I am backing up my data now. Once I find out what causes the crash and repeatedly crash it, what do I do next?

 

[richc46]

Use the computer for the next 36 hours. Boot it, play your games, do whatever you do with your computer. It should BSOD and this is a good thing. After about 36 hours, send me all the reports.

 

[brianlt]

Hi Richard,

I attached the zip file. During these last few BSOD, the minidump collection on the BSOD screen would take a while so I just shut down the computer. I'm not sure if the information was collected for those particular BSOD. Thanks for looking at my stuff.

 

[richc46]

Your dumps name a MS Kernal driver as the cause. NO way, its just the scapegoat. This may very well mean hardware. Start with a memory test.
Guide to using Memtest86+ - Geeks to Go Forums
Run fo 8 passes
Then take each stick and test for 6 passes in a good slot.

 

[brianlt]

Are you saying that I need run the test while both sticks of RAM are in, then run the test with individual sticks?

 

[richc46]

For 8 passes run with all the sticks, just like the computer is now
Then run each stick separately in a good slot for 6 passes.

 

[brianlt]

Thanks for the quick reply. If there is an error, would I need to write everything down or is the information recorded?

 

[richc46]

You will either get pass, or fail with a number (amount of failures) Even one failure you either need new ram or a new MB.

 

[brianlt]

Soon after I build my desktop, which was about a month ago, I started getting BSOD. Since I could still return my components, I returned the MOBO and video card and swapped them for the same products so I think it might not be the MOBO unless its a coincidence that both mobos are faulty.

 

[brianlt]

Ive been getting more BSOD and thought I would update the attachment. Also, I can't get this part of the memtest instructions to work "First and foremost verify that your disk has burned correctly.
Go to My Computer or Finder on a Mac and go to your CD/DVD drive. Make sure the Disk is called Boot. If not then the burn has been unsuccessful. However if it is called Boot your CD is ready to go." The CDs I burned stay as "mt420" and do not boot on startup. hmmm

 

[brianlt]

Nvm, I got it to work

 

[brianlt]

Hey Richard, I ran memtest on both sticks together for 7 passes and there was no error. Should I still run memtest on individual sticks?

 

[richc46]

Yes, run it for 6 passes each.

 

[brianlt]

I ran a stick for 9 passes and the other for 11 passes. No errors ):

 

[richc46]

OK,
Check out CPU. Read warnings before you try.
http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

 

[brianlt]

I ran the CPU test, however, I had to stop it as the temperature of one of my cores was at 66'C and my CPU's Tcase is 67.4'C. Man, they BSODs are stacking up. Getting a lot more of IRQL_NOT_LESS_OR_EQUAL errors on startup recently :/

 

[brianlt]

Hi Richard,

Okay, I ran the test 1 time and it was successful at standard level. Does this narrow it down to HDD/PSU?

Thanks for all the help so far. I really appreciate it!

 

[richc46]

Go to the website of of your HD manufacturer and test hard drive.
Test temps
http://www.cpuid.com/softwares/hwmonitor.html