you need more rams

>>34399629
I have no sacrificial altar to put the rams on, though.

Are you overclocking? Is the RAM running at the support clock speed?

Do you by any chance have the Etron 168A USB3.0 chip?
I got that same BSOD a few weeks ago.

Dude, are you retarded? Fixing this could not be any more simple...

ffs, the BSoD is telling you the problem: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Let's break it down
-IRQL = IRQ Level
-and that IRQL is NOT less or equal

Just go into the control panel, click 'IRQ Levels', and make sure 'Is Less or Equal' is selected. Apply and restart.

>driver problem
open source drivers are more stable. that's what you get for being nonfree

Download Memtest86 and run it to see if it is a RAM problem.

>>34399682
Answer this, OP.
XHCI stands for eXtensible Host Controller Interface. It's an issue common with Etron's 168A chips, which are utter shit.

>>34399682
Nope.

>>34399613 (OP)
>Windows

>>34399812
Okay. If you have USB3.0 at all, just disable it and reconnect your header to a 2.0 port on your mobo.
Don't use the 3.0 ports on the back of your mobo either.
Reinstall your driver, even if it is up-to-date.

install gentoo

OP check your ram timings and voltage are correct

YOu have bad ram replace them.

>Windows
Not even once.

Not OP but he's a buddy of mine. His computer appears to have crashed again (he just dropped out of IM) so he won't be back for a few minutes while he reboots.

He was telling me that he couldn't find the IRQ options in his control panel. We have the same OS (W7) and I couldn't either. Neither of us are particularly tech savvy, so could you maybe elaborate a bit on what he should do?

>>34399941
lol

>>34399827
>>34399907
Right, because BSODs almost never happen means that we should go on Linux.

>>34399941
They were fucking with you.
The issue lies in his USB controller. He needs to reinstall his drivers.

File: 1370649384516.png-(5 KB, 250x250, 1283558371633.png)

5 KB PNG

>>34399613 (OP)
>can't troubleshoot the goddamn thing because it crashes so fucking often.

>>34400017
>>34399969

Okay I'm sorry for making him sound retarded. He's better with tech than I am, I was just trying to give him a hand while he dealt with a shitty tech situation.

Ignore me and pretend I never made that post.

>>34399941
This error is usually caused by bad RAM there are two options

1. the ram is fucked
2. the timings and voltage are set incorrectly

Solution to fix is to open computer case, read voltage and timings off of the side of the ram go into the bios find the memory options and set the timings and voltage correctly.

>>34400031
This. It's Windows after all.

>>34400046
What does this have to do with BSODs?

>>34400041
>EtronXHCI.sys
It's not a RAM problem. It's a problem with his Etron Host Controller. All he needs to do is reinstall or downgrade his drivers to the last stable release.

>>34400112
It's not a picture of my bluescreen, because I don't own a camera.
It's just the first thing Google pulled up.

>>34400134
The entire point of the BSOD is to tell you what exactly is going wrong.
It's probably the RAM then.

>>34400134
And how is this supposed to help us, stupid?

Check what your bluescreens were with
http://www.resplendence.com/whocrashed
and then google the causes.

Alright. After checking, it would appear that I wasn't supplying enough power to my RAM. Timing was fine, though.