| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 53947 | 2005-01-31 21:23:00 | IRQL not less or equal blue screen error | virus67 (7068) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 319945 | 2005-02-01 10:24:00 | Extract from [ulr=http://www.michna.com/kb/WxSP2.htm#Boot_or_shutdown_problems_after_Service_ Pack_2_installation]WinXP Problem Solver[/url]: IRQ_NOT_LESS_OR_EQUAL STOP: 0x0000000A can be caused by Nero InCD 4300. A side effect is that, very strangely, you cannot boot in safe mode, but you can boot in normal mode. You can try to update InCD to the latest version. There are conflicting reports about version 4303. If you keep having the problem, uninstall the program altogether. Scroll down to "General Blue Screen of Death information" and see if there is anything helpful in there. Just in case it happens again. |
Murray P (44) | ||
| 319946 | 2005-02-20 16:31:00 | Im getting the same thing, but it's when i try to install windows. I had to reformat :blush: | Dr_Badlove (7069) | ||
| 319947 | 2005-05-19 15:44:00 | Hi guys. I need some new ideas. I have recently started getting this BSOD error when i try to load Windows XP. I run fully updated in terms of windows updates. I have tried the latest driver updates for all components on my PC. I have tried remastering which solved the problem for a few days before it returned. I cud get into safe mode but thats not loading either now since i told it to run a chkdsk on next restart. I have tried reseating and swap testing all components and have run a memtest that came back fine. Like i say i have recently remastered so there is pretty much no SW on the comp that cud be causing the problem. Im stuck on what to try next :dogeye: Any ideas? |
Tomatoes (7070) | ||
| 319948 | 2005-05-19 23:08:00 | How the heck has this thread garnered 4,802 views? :dogeye: :dogeye: | Metla (12) | ||
| 319949 | 2005-05-19 23:10:00 | How the heck has this thread garnered 4,802 views? :dogeye: :dogeye: search engines. |
tweak'e (69) | ||
| 319950 | 2005-05-20 01:39:00 | How the heck has this thread garnered 4,802 views? :dogeye: :dogeye: Because that error message appears to be highly popular and everyone wants a slice of the cake. Thank Google for that. ;) |
FoxyMX (5) | ||
| 319951 | 2005-08-17 01:15:00 | if u'r using amd processor then it must be really hot ;) try to cool it down and no blue screens again... | murdock (7071) | ||
| 319952 | 2006-02-05 21:13:00 | Im getting the same thing, but it's when i try to install windows. I had to reformat :blush: I'm currently having the exact same problem. I recently installed a new motherboard, and it's been acting funny ever since. I cant reinstall windows because I get this error halfway through the setup process. Anyone know why? |
kyle2371 (7072) | ||
| 319953 | 2006-07-22 21:35:00 | :lol: I agree...try arranging the cards into different configurations and try testing them into another system too. Take (a) known good ram(s) from other system and use them into your computer that's giving that error and you'll find the culprit. :thumbs: Even if you reinstall windows or reformat it will not allow you to continue with the process even if your access safe mode or last known good config it will be no good. Extremely advisable to try another known good ram or system... |
IvyJones (7073) | ||
| 319954 | 2006-07-22 22:43:00 | This error is always a driver error . Its not hot CPUs . A friend had this recently with a new build . She'd get right through the Windows install and get it, it did it after she added the updates so she started again, it did it this tme after SP2 was added . She started again and added nothing and got it again . Eventually after much stress and headaches she found it would occur if she plugged the mouse into 3 of the 4 onboard USB ports . Tried a printer in them, no problem, so she tried another mouse . End of problem . But weirdly the suspect mouse was OK in one of the USB ports but not the others . This was not specific to its own mouse driver, did it with just the WIndows one too . So it can be tricky to find which device is causing the problem . Remove every add on and try it, try another mouse and keyboard (one at a time), try PS2 versus USB too . Add cards back one at a time . Try updated chipset drivers too . |
pctek (84) | ||
| 1 2 3 4 5 | |||||