is there a setting somewhere that'll give me time to read the BSoD before a computer resets?

it's not giving me enough time to check the error codes

[Edited on September 17, 2006 at 3:43 PM. Reason : nm found it, this space to be used to post error codes next crash]

9/17/2006 3:35:47 PM

ok so i've gotten

DRIVER_IRQL_NOT_LESS_OR_EQUAL

BAD_POOL_CALLER

PAGE_FAULT_IN_NONPAGED_AREA

BSoD errors and a TRAP 06 EXCEPTION error, though that might possibly attributed to a crash occurring as i was virus scanning

i'm going to run memtest on it for my next step i think, anyone else have any ideas?

9/21/2006 1:08:00 PM

hardware/driver issue

9/21/2006 2:22:11 PM

that's what i was hoping initially until it kept referencing different drivers each crash

9/21/2006 2:28:55 PM

update your bios, check your ram, check for some sort of fuck up on your board

9/21/2006 3:12:09 PM

yeah i updated my bios and i haven't had a crash yet (for an hour)

but now i have a new problem, whenever i try to click on control panel or my computer, windows explorer crashes

i can get into my documents and go to my c drive and shit with the address bar though



[Edited on September 21, 2006 at 3:46 PM. Reason : heh the perception of time]

9/21/2006 3:45:09 PM

oh and microsoft media player

someone point me towards a windows repair app

9/21/2006 3:53:29 PM

Try memtest86, google it for an .iso, burn using nero or whatever you have, and then boot from CD with it. It does pretty exhaustive memory testing. It might not be whats wrong, but its worth checking out. Every single time XP has given me a BSoD, its been because of RAM. I RMAed 2 sticks a while back and haven't seen blue screen since.

[Edited on September 21, 2006 at 4:14 PM. Reason : nvm, I didn't read that you already fixed the first problem.]

9/21/2006 4:13:31 PM

i think i fixed the original problem by flashing the bios, we'll see in a few days

if not, i've been meaning to buy a thumb drive to fill with boot apps and this gives me a reason

and i think i've found the source of my second problem via the Event Viewer

Quote :

"Faulting application explorer.exe, version 6.0.2900.2180, faulting module urlmon.dll, version 6.0.2900.2870, fault address 0x00021b8d."

it's always the same address too

can i just overwrite it with a new copy?

9/21/2006 7:42:34 PM

oh fuck, BSoD is back

i need a windows xp cd and a spare thumb drive

9/22/2006 1:40:45 PM

iirc; in the IRQL NOT LESS OR EQUAL error message there are either four or five hex codes. One of those indicates whether it was a hardware or software fault (0000 or 0001.) If it's software it's probably a driver and one of them will indicate the memory address of the failing driver. You can look in the memory range of each driver under "resources" in the driver details to find out which driver it is.

Outside of those most likely causes it can get more complicated. There is a article somewhere on MS Technet about diagnosing it.

Also, keep in mind that memory errors can look like software errors from the OS point of view. If the memory flips a bit the OS can think it was just a software fault.

[Edited on September 22, 2006 at 3:42 PM. Reason : s]

9/22/2006 3:40:44 PM

well i went through 4 and half passes of memtest86+ with no errors, so i guess it's not the memory

fuck

9/22/2006 8:41:48 PM

how about the processor?

install something like motherboard monitor and run a CPU test while watching your power supply voltages... could be CPU or PSU, if you see your voltages dip significantly under sustained load (let it run for 2-4 hours at least) quite possibly is the PSU, if the results of the CPU test indicate a fault (or the system shits itself) while the voltages look fine you may be looking at a marginal CPU.

distributed.net's RC5-64 and OGR applets are good FPU and INT synthetic loads respectively, but I don't believe either can detect a corrupt value... Super-PI can detect a corrupt value and is probably a better FPU load... if the system is consistently shitting itself, though, you probably won't need to detect corruption to realize the load is causing the issue

[Edited on September 22, 2006 at 9:16 PM. Reason : *]

9/22/2006 9:07:19 PM

i'm going to wait until i get my hands on a winxp cd and can run "sfc /scannow" before i worry about the processor

if it comes down to something hardware, this laptop is still under warranty and i'll just send it in

9/22/2006 10:13:10 PM

w00t!

no recurrence of the BSoD and running 'sfc /scannow' and then 'regsvr32 urlmon.dll' got everything working again!

9/24/2006 3:05:06 PM