big problem!!help!!

Mr.Suave

Mr.Suave

New Member
im not sure if this is the right place but i have problem with my comp
i get this error message and i dont kno y

a problem has been detected and windows has been shut down to prevent damage to your computer.

DRIVER_IRQL_NOT_LESS_OR_EQUAL

if this is your first time you've seen this stop error screen, restart you computer. if this screen apears again, follow these steps:

Check to make sure any new hardware or software is properly installed. if this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

if problems continue, disable or remove any newly installed hardware or software. disable BIOS memoery options such as caching or shadowing. if you need to use safe mode to remove or disable components, restart your computer, press F8 to select advanced startup options, and then select safe mode.

Technical information:
*** STOP: 0x000000d1 (0x00000000, 0x00000002, 0x00000008, 0x00000000)

beginning dump of physical memory
physical memory dump complete
contact your system administrator or technical support group for futher assistance.
Click to expand...

looks like this
attach_photo

(can you see the pic? its kinda fussy b/c its taken by my sk2 camera)

i havent installed anything new, hardware or software, and this hapened when i was just talking to someone over aim..its happened twice now..wat could be the problem and how do i fix it?
 
QUESTIONS 101 Could be any number of things, usually it's a faulty windows install or a HDD going bad or something with the controller or something else OR some other random thing, like said, more info needed.
 
more info like wat exactly?
my system specs are in my sig. and i doubt its a faulty windows install becuase it just happened just today and ive had my comp w/o the problem for about 2-3 weeks now. and its a new comp, just built it.
im thinking it is b/c of AIM some how. i had aim going when it did it twice. but now that i dont have aim on it hasnt happened. but even b4 today ive been using aim everyday and had no problems. the version of aim is 5.2.3292, its an older version b/c im using AIM mutation with it.
 
more info like wat exactly?
my system specs are in my sig. and i doubt its a faulty windows install becuase it just happened just today and ive had my comp w/o the problem for about 2-3 weeks now. and its a new comp, just built it.
im thinking it is b/c of AIM some how. i had aim going when it did it twice. but now that i dont have aim on it hasnt happened. but even b4 today ive been using aim everyday and had no problems. the version of aim is 5.2.3292, its an older version b/c im using AIM mutation with it.
Click to expand...
Have you done a burn in test after getting/building the box? Regardless, id do a few laps in Memtest86+ :)
 
Praetor said:
Have you done a burn in test after getting/building the box? Regardless, id do a few laps in Memtest86+ :)
Click to expand...
nope not yet but will do...i planed to do that and the prime 95 thing but havent had the free time where i could keep the comp on w/o the need to use it. i plan to do it when i get to vegas as im in california right now and going back in a few days.

btw do you really need to burn in the comp? and wats the purpose of it? also when you get a prebuilt comp do they burn it in for you so there is no problems?
 
btw do you really need to burn in the comp? and wats the purpose of it? also when you get a prebuilt comp do they burn it in for you so there is no problems?
Click to expand...
You trust Dell or whoever to burn it in? :rolleyes: C'mon now :P (and if they did, ... to do a good job?)
 
ok well ive done burning in the comp and i did some benchmarks and i still have this problem but its worse. its either i get the BSOD msg like i said b4 or it will just freeze. Also one time when the msg did pop it it beeped twice if that has to do with anything. then a few times it was all staticky and it sounded like it was beeping. sometimes when it did freeze or i get the msg, it would do a very high and long pitch beep and wouldnt stop till i press restart. its happening randomly but it seems i have a higher risk of getting it when playing a game.
also would pressing the restart button harm the comp? b/c its not properly shutting down then restarting. im just afriad each time i do it harms it, in some way...

after i get the BSOD msg and restart. a window would pop up telling me somthing is wrong with windows and asks if i want to inform microsoft or somthing like that. should i say send? or just cancel. so far ive been saying cancel. would clicking send and letting microsoft know help? like they contact me back explainging the problem and telling me how to fix it somehow?

btw when i did the prime95 torture test overnight the next morning i got the BSOD...but i kno it had completed it b/c i checked back at prime95's result folder and said it was successfully completed. also i didnt exactly use memtest86(i cant figure out how to do that image burning and ran out of cd's) but i used somthing called memtest(just memtest) and it checks the memory without having to use a cd or floppy and i did the test twice and got no errors.
 
Get more CD's/floppies and put Memtest86 on one of them (it's real easy to burn, use Nero or something and select burn a previous image), run it once and see if you get any errors.
 
well i was exploring through my bois and guess what i found!!
i found an option that said "Run Memtest86" and for its description is said Run Memtest86 without any boot device.
should i do that? or would it be better to do it by image burning memtest86 on a CD?
 
well i was exploring through my bois and guess what i found!!
i found an option that said "Run Memtest86" and for its description is said Run Memtest86 without any boot device.
should i do that? or would it be better to do it by image burning memtest86 on a CD?
Click to expand...
I use the BIOS one for convenience heh

Also, what are your voltages for everything? :) and clocks too
 
well i did the memtest86 and it was running for about 11hrs and my dad decides to just turn the power off for the whole house...and he doesnt even tell me....
would that cuase any problems??

Also, what are your voltages for everything? and clocks too
Click to expand...
according to PCwizard
CPU Core : 1.28 V (CPU-z its 1.312V)
Aux. : 1.17 V
+3.3V Voltage : 3.26 V
+5V Voltage : 5.05 V
+12V Voltage : 11.37 V
and for the memory
Voltage : SSTL 2.5v (but the BOIS has the DRAM at 2.6V:confused: )
Supported Frequencies : 200 MHz
CAS Latency (tCL) : 2.5 clocks @200 MHz (but the specs said that it shoudl be 2 :confused: when i bought the RAM) should i go into BOIS and set it to 2? cuz its at Auto right now, well it exactly says "CAS Lantency Control (Tel) Auto"<- is that even it?
RAS to CAS (tRCD) : 3 clocks @200 MHz
RAS Precharge (tRP) : 2 clocks @200 MHz
Cycle Time (tRAS) : 5 clocks @200 MHz
 
according to PCwizard
Click to expand...
Where in PCWizard are you reading this? I assume under the section labeled Voltage, Temperatures and Fans rather than the individual component sections :)
 
Praetor said:
Where in PCWizard are you reading this? I assume under the section labeled Voltage, Temperatures and Fans rather than the individual component sections :)
Click to expand...
yes y? where should i be looking?
 
since i did the memtest(w/ it showing no errors), the BSOD didnt popped up again so i thought it was over with. but when i played Ghost Recon for a little bit it comes up again. and so far its only happening when i play GR.:confused: i can play AOE3 and Fear w/o it comming up even at very long gamming sessions, but i cant even play GR for more than 10mins.:confused: :confused: help!
 
hate to sound like a newb but I noticed that in your error that you origninally posted that it could be an IRQ address problem?? if you have already checked it then guess not but that stood out when I saw it..
 
You must log in or register to reply here.
Back
Top