View Full Version : cant install windows - driver irql not less or equal


baluga
7th March 2008, 03:25
Need help here. I cant install my windows, it crashes in the middle of installation. It displays a blue screen stating "driver_irql_not_less_or_equal" physical dump memory. What will I do? Please help me. I already removed all the components/hardware installed in my pc. All that is left is my video card and memory. Thanks a lot!

squire77
17th March 2008, 10:05
Disable the SATAenable in the bios i think it will work, i had encountered that problem before in my Notebook

leianleian
17th March 2008, 10:39
install WinXP with SP2

weboneando
29th March 2008, 02:11
Most probably you have a faulty ram module get memtest (google it) and run it to check your ram, if you got several modules then you´ll have to remove them and test them one by one, if you find a faulty one then try cleaning the pins with a eraser and test it again.

Myk!
29th March 2008, 02:18
Yes I agree with webo.

This problem mostly due to RAM. But try also to get another installation disk to be sure of.

Ling738
28th April 2008, 11:39
HELP!! :confused:
Anyone knows how to solve the following BSOD errors ?

1) STOP : 0x0000000A (0x00000000,0x0000001C,0x00000001,0x80502000)
2) STOP : 0x0000000A (0x00000016,0x0000001C,0x00000001,0x805021DE)

my system configurations:
Microsoft Windows XP Pro Ver2002 SP2
Intel Core 2 Duo E4600 @ 2.4GHz
2GB RAM NVIDIA GeForce 8400 GS

Could not watch any videos, mpgs files at all.

weboneando
28th April 2008, 17:58
At the bottom of the message there must be info making reference to a file, this info indicates where is the error, if the messages is too fast to read it do this: go to "System properties" windows key + pause key, then go to advanced tab and in the "startup and recovery" section click on the settings button, at the next window uncheck "Automatically restart", that way the next time the error occurs the system won´t restart by it´s own and you´ll get the chance to read the whole message, take note of everything not just the memory address and then post that again, my guess is that the video driver could be the cause but you have to make sure before starting to mess around with the system.