Author Topic: BSOD... (Read 356 times)

LC0g · « **on:** May 30, 2008, 02:48:03 pm »

Hey guys! I got multiple BSODs recently. I used the windows debugger to open the dump files and analyze them, and the result is:

Probably caused by : ntoskrnl.exe ( nt+43786 )
(the BSOD message is IRQL_NOT_LESS_OR_EQUAL)

What is this? Since I put this in Google, I found possible errors and one of them is the following: missing or invalid boot.ini file... that is true... I don't have a boot.ini file since every time I start up my PC I got a Missing or invalid boot.ini file; Booting from C:Windows message show up...
Do you guys know what is going on??

thx very much

LC0g

anomaly · « **Reply #1 on:** May 30, 2008, 03:19:48 pm »

try bumping up your voltages a tad. (RAM/CPU/FSB) it might help. BUT it could be something totally different. so i would await the help of others unless you have room to spare in the voltage area. or you could just down clock some too.

i have gotten this or a similar error before and i just though my ram was corrupting my data because of it not being configured properly. so thats what i did and it fixed the problem. but that was just my situation.

and i always try updating my drivers when stuff like this happens.

LC0g · « **Reply #2 on:** May 30, 2008, 03:48:59 pm »

Quote from: anomaly on May 30, 2008, 03:19:48 pm

try bumping up your voltages a tad. (RAM/CPU/FSB) it might help. BUT it could be something totally different. so i would await the help of others unless you have room to spare in the voltage area. or you could just down clock some too.

oh damn... I didn't overvolt my North bridge... is it ok?!?

the ohnly thing overvolted in my PC: RAM (tracer are rated at 2.2V when operating at 800MHz / 4-4-4-12) and CPU (3,2GHz and 1,424V Idle)

LC0g

Farmchild · « **Reply #3 on:** May 30, 2008, 05:55:55 pm »

I think I posted a link like this in the other thread. You should probably rebuild your boot.ini. You can do this using the recovery console. Take a look at this article:

http://www.computerhope.com/issues/ch000648.htm

LC0g · « **Reply #4 on:** May 30, 2008, 11:04:30 pm »

Quote from: Farmchild on May 30, 2008, 05:55:55 pm

I think I posted a link like this in the other thread. You should probably rebuild your boot.ini. You can do this using the recovery console. Take a look at this article:

http://www.computerhope.com/issues/ch000648.htm

oh nice. But what if my system is ''Microsoft Windows XP Media Center Edition''? I'll try getting the load identifier to ''Microsoft Windows XP Media Center Edition'' and see what happens.

thx,

LC0g

LC0g · « **Reply #5 on:** May 30, 2008, 11:19:55 pm »

GOD DAMN THAT FEELS GOOD

FINALLY... NO MORE BOOT.INI FU**...

My boot.ini:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Media Center" /fastdetect

thx so muuuuchh!!!
luv u!!

LC0g

Farmchild · « **Reply #6 on:** June 04, 2008, 06:45:03 am »

No Problem man, hope that fixes your BSOD's too.

LC0g · « **Reply #7 on:** June 05, 2008, 02:35:30 pm »

For now it has!! (been a week or so) THX!!

LC0g