I’ve been having some problems today with my computer crashing all of a sudden, giving this blue screen of death errornotice:
“IRQL not less or equal
stop: 0x0000007E ( 0XC0000007E , 0X00000000 , 0XF789E384 , 0XF789E080 )”
Did some googling and browsed through a bunch of tech messageboards, but the hints & tips are so diverse… I think I need some expert help to pinpoint the precise cause of this error Some people say its bad memory, some blame it on the network drivers, some say it’s a virus etc etcetera.
Basically the motherboard bios could use an update, but I’m afraid to mess up the firmware and f**** up the whole system. According to ‘si soft sandra’ I have a Gigabyte motherboard ( 8I915P duo ), when I search the net for drivers there seem to be tons of variations on the 8I915P duo, some with the word pro behind it or another letter and some number combo. Why can’t these manufacturers just pick a totally different string of characters to define a newer motherboard?
Is there a place on the net where I can paste in the given bsod and the site tells me what’s the problem?
The bad memory and virus explanation are silly (“blah blah blah reinstall”), as bad memory and viruses can cause just about anything. But just so you know that it’s not the cause: http://www.memtest.org/
If it happened just once, forget about it (IIRC that’s what it says on the BSOD itself ). I sometimes get that when I plugged in something (USB) and then reboot… maybe Windows then reassigns IRQs or something, because I never get that error twice in a row. Okay, I guess that wasn’t very helpful either sorry…
Microsoft has some kind of knowledgebase, but as said, just forget it if the crash was just once. It can be caused by anything, only way for you to find out the cause if problem persists is test all components one by one. If nothing seems to be wrong, it’s your PSU or mobo. Processor not likely, but would maybe show in memtest too.
The “report error” feature in WinXP works pretty well sometimes. All of a sudden I started having some total freak crashes repeatedly, and after a restart that same dialog came up for the n-th time, so I decided to see what it does. It found out that it was the audio driver for the nForce that was buggin’ out, and gave me a direct link to the latest driver.
Quite handy, if you want to sell your soul . It’s unlikely to work that well in every case, though.
Yep, always in these kind of situations it’s necessary to think what has been updated lately and what can be updated and have this enormous driver/Windows update hassle. I personally never used error reporting, I have completely disabled it from my system. And it would never have helped me either.
BSODs are that much spiritual concept that really no-one can help on the forums like this unless problem is examined pretty tight. Microsoft has internet-based database as far as I remember where you can search by the fault code of the BSOD. It may or may not help.
I was having problems with BSODs, restarts and freezes for years and no matter what I did I couldn’t find a solution. It wasn’t until a couple of months ago that I, when playing around with BIOS settings, tried to up the voltages a bit. A mere 0.1V increase to the CPU and to the memory has made my system stable as a rock.
If reinstalls, driver updates, BIOS updates and prayer fails, you might want to check if the behavior is caused by fluctuating voltages from the PSU or a power hungry CPU. Higher voltages in general means a more stable system, just make sure you have the know-how and the means to get rid of the extra heat that is generated… small increments in voltage shouldn’t make much difference in heat though.
Some people say its bad memory, some blame it on the network drivers, some say it’s a virus etc etcetera.
). I sometimes get that when I plugged in something (USB) and then reboot… maybe Windows then reassigns IRQs or something, because I never get that error twice in a row. Okay, I guess that wasn’t very helpful either sorry…
. It’s unlikely to work that well in every case, though.