Bsod irl_not_less_or_equal/whea_uncorrectable_error

[itzextinct]

- x86 (32-bit) or x64 ? : 64 bit
- the original installed OS on the system? : Windows 7 Premium 64 bit
- Full Retail
-Brand new build/month old OS install

PC Specs
Mobo: Gigabyte
GA_A55M_DS2
Ram:
Patriot 1333, 2 4GB sticks
CPU/GPU (An APU) : AMD LLano APU

Basically I just have built my first gaming comp and I've ran into some issues, because I've had TONS of issues fixed maybe one or 2 bluescreens out of like 5 and I just cant solve it and I think it has to do with drivers it happens common when I play like world of warcraft, listen to music, talk on skype, alt tab out of a game. Anyways if you guys could maybe solve this I'd love you forever <3

-I did run memtest it was mixed results

 

[zigzag3143]

18 of 28 crashes are memory exceptions, with a few hardware thrown in (perhaps ram)



These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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/Win7 Startup Repair feature).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

 

[itzextinct]

Results

These are my minidumps from the past 3 days, I may have been stressing windows drivers I forget what I put.

 

[zigzag3143]

These are my minidumps from the past 3 days, I may have been stressing windows drivers I forget what I put.

The most recent (from April 5) are still memory exceptions related to your USBPORT.SYS driver, and the most recent has converted into a generic hardware issue.

I would remove the USB devices (at least to test if you can) and run memtest and verifier.

 

[itzextinct]

Hello, it seems as if it wont crash if I dont have my logitech g35 plugged in, aswell as my phone charger been running it today with only my apple (normal audio jacks not usb) plugged in, is this a problem with the bluescreens?

 

[itzextinct]

EDIT*
It bluescreened.

 

[zigzag3143]

EDIT*
It bluescreened.

Still USBPORT.SYS, still memory exception caused by a driver.

http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html?ltr=U

 

[itzextinct]

Done, but i got this crash.

- I just installed a EVGA 2GB ddr3 GPU

I think the drivers on it are interfering with my APU's built in GPU

 

[zigzag3143]

Done, but i got this crash.

- I just installed a EVGA 2GB ddr3 GPU

I think the drivers on it are interfering with my APU's built in GPU

In post two both memtest and verifier were recommended. How many passes for memtest?

Please type verifier /query and tell us what drivers are being examined.

 

[itzextinct]

I think like 3 for memtest, it took about an hour for 3 passes, and everything but special pool, force pending, low resource simulation

 

[zigzag3143]

I think like 3 for memtest, it took about an hour for 3 passes, and everything but special pool, force pending, low resource simulation

Memtest needs 6-8 passes. Verifier is next. When you run it type verifier /query.

 

[itzextinct]

Hello, in regards to you I'm positive my ram is not faulty as i just had it in my last PC. I'm almost positive its my drivers could you help me fix this?

 

[itzextinct]

bump.

 

[writhziden]

Further reading for your RAM and whether you should do more thorough memory testing as suggested: Avoid Static Damage to Your PC | PCWorld