Click to See Complete Forum and Search --> : BSOD
bad55lad
03-19-2005, 06:04 AM
recently overclocked my pc which worked out to be a very bad idea,
i have a :
amd 2400+ xp ahtlon
512 ram
120 gb hard drive
radeon 9000
soundblaster live
windows xp
asus a7v8x-x motherboard
i managed to fry the mobo which took some time to work out after swapping between alot of different hardware,right well the problem is after i found out the mobo was fried i ordered the new one listed above (asus).after connecting everything up again i was surprised it all turned on and seemed to work perfectly.after a few hours it decides to turn off and randomly restart and some times locks up with the blue screen of death .does anybody have any idea what this can be as im stumped and is slowly making me lose the will to live.
bad55lad
03-19-2005, 08:04 AM
A problem has been detected and windows has been shut down to prevebt hardware damage to your computer.
Driver_IRQL_Not_less_OR_Equal
*** Stop: 0x000000D1(0x0096f050,0x00000002,0x00000000,0xf79A 5FD3)
*** USBPORT.SYS - Address F79A5FD3 Base at F798B000,DATESTAMP 41107 D62.
But these errors change nearly everytime it happens.
Sterling_Aug
03-19-2005, 08:06 AM
If you are overclocking this one, STOP.
If you didn;t use thermal grease on the CPU, get some on there for better heat transfer to the heatsink.
Check the heatsink and fan for dust and dirt. Clean them well.
Check the FSB Vcore voltages. Reset them to factory default which will reduce the heat.
Check the system board for buldged caps. The tops may be pushing out and oozing goo.
bad55lad
03-19-2005, 08:10 AM
i have just brought the new mobo so everything is intact!!
I have also brought a new heatsink and fan for processor so dont think it is a heat problem!
all voltages look fine!
rmanet
03-19-2005, 11:44 AM
Found this from what microsoft says about it. Or maybe even just switch your bios back and forth between plug and play OS and non plug and play if you think you done everything below in terms of your drivers - and what kind of ram you using?
Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
The Stop 0xD1 message say the system attempted to access memory using a kernel process IRQL that was too high. Drivers typically cause this error and you keep getting different ones so it doesn't appear to be just one device - did you load the mobo drivers? I'm asking because you listed the USB error. Are you sure all your drivers are installed correctly?
This Stop message has four parameters:
Memory referenced.
IRQL at the time the system crashed
Type of access (0x00000000 = read 0x00000001 = write
Stop 0xD1 messages can occur because of faulty or incompatible drivers?
Stop 0xD1 messages can be researched at the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources.
Search using keywords from the various error messages you're getting- maybe that'll help...
sleek
03-22-2005, 07:58 PM
random BSOD's with different errors often means faulty RAM.
fishybawb
03-23-2005, 04:05 AM
Is your new motherboard the same model/chipset as the old one? If it's not, it's advisable to do a fresh install of Windows - having the wrong chipset drivers installed is going to cause problems.
causticVapor
03-28-2005, 01:06 AM
Yeah, changing chipsets without uninstalling the old chipset drivers (most notably IDE drivers) will cause this error.
If your old motherboard doesn't work and you don't have another motherboard lying around with the same chipset as it, your only real option is to reinstall.
bad55lad
04-13-2005, 07:34 AM
I have re-installed everything again andd problem still persists!!
It has been going on for a while now and i have narrowed it down to when i play mmog's such as world of warcraft and starwars galaxies and also when i play movies files.
does anyone have any ideas???
RockNRoll
04-13-2005, 03:13 PM
Try new RAM like sleek said?
causticVapor
04-14-2005, 10:38 PM
I have an idea - swap CPUs. The CPU may seem to "work perfectly," but who knows what could have happened. Very likely the mobo wasn't the only thing taken out by your overclocking misadventure. Doing memtest86 runs wouldn't be bad either.
SysOpt.com
Copyright Internet.com Inc. All Rights Reserved.