IRQL bsod back again? >.<

[kyle2020]

Ok so this is the 4th time my pc has blue screened this morning - 3 times saying IRQL_NOT_LESS_OR_EQUAL with win32k.sys in it aswell, and one time it said something like PAGE FAULT IN NONE PAGED AREA or something.

Apparently its bad ram. Now if it is, i have a theory that i need validating.

My motherboard only allows me to set my rams voltage to a max of 1.95. I quickly checked on crucials site and it reckons that the ram should be run on 2.2V. Could it be that the ram isnt recieving enough juice because of my shitty motherboard? If so, could i buy something like some geil black dragon that says "1.8 - 2.1V" and run it fine?

This problem is giving me a bad headache - please help!

 

[kyle2020]

Anyone? And if it is voltage, ill have 2GB of tracers up for sale haha.

 

[JoshBrunelle]

try loosening up timings, what speed are you running them at?

 

[kyle2020]

try loosening up timings, what speed are you running them at?

just on defaults after fresh install of windows - 5-5-5-15 on 1.95V, running at a shade under 800Mhz.

 

[JoshBrunelle]

Run them through memtest, they should be able to run fine at those voltages, just not the fastest they could be.

 

[kyle2020]

Run them through memtest, they should be able to run fine at those voltages, just not the fastest they could be.

ill have to i think. Ill run it over night tonight. Do you know what else could be causing this?

 

[oli_ramsay]

Could be a driver issue, I kept getting BSODs saying IRQL not less or equal then I removed an app called DSLMON.exe and it went away

 

[kyle2020]

Could be a driver issue, I kept getting BSODs saying IRQL not less or equal then I removed an app called DSLMON.exe and it went away

cant find that oli, so it must be an issue elsewhere. Im getting rather annoyed at the prospect of having a previously reliable machine that after 2 weeks of downtime is now crashing upwards of 5 times a day under normal use :shadedshu

 

[oli_ramsay]

I still think it's a driver issue. Reinstall windows and and nothing else, if you're still getting BSODs then its a hardware issue.

 

[WhiteLotus]

i got this with my bad graphics drivers - have you changed yours recently?

 

[Ongaku]

I got this error when Windows XP was installing :/ The RAM wasn't seated properly...plus my PSU was dying.

 

[kyle2020]

i got this with my bad graphics drivers - have you changed yours recently?

i havent no. ill look to install some more recent ones once i come home from work. thanks for the suggestion.

 

[kyle2020]

i think its my processor. Im currently running it at stock clocks (2.6) and its going right up to 100% proc use playing CS:S for gods sake - and 60% on idle! She best not be dying on me, Ill cry ='[

 

[kyle2020]

If it is dying, slowly, ill run it till it dies then warrant the purchase of an intel quad setup. Everyones a winner!

 

[Ketxxx]

Geil Black Dragons won't help you. They state 2v, but in actuality its anywhere between 2-2.4v. I have to use 2.2v, sotck or OCd. Your options basically are to run 6-6-6-18 timings with your current memory to try and get it error-free, buy some cheap crappy generic stuff that will run on 1.8-1.9v, or buy a new mobo.

 

[kyle2020]

Geil Black Dragons won't help you. They state 2v, but in actuality its anywhere between 2-2.4v. I have to use 2.2v, sotck or OCd. Your options basically are to run 6-6-6-18 timings with your current memory to try and get it error-free, buy some cheap crappy generic stuff that will run on 1.8-1.9v, or buy a new mobo.

yeah im running it on those timings, and all seems good so far . . . now my processor is failing so a new motherboard + a Q6600 are soon to be had i think.