| | |
Computer keeps crashing- error code help plz
![]() |
•
•
Join Date: Aug 2005
Posts: 8
Reputation:
Solved Threads: 0
About 5 weeks ago i decided the time was right to go out and build the pc ive been longing for, so i did....
The problem is now that it is all up and partly runnin im having major problems with system crashes and freeze ups.... ive tried every forum i can think of for help but to no avail.
The error message i get when i check in the event viewer is.....
Error code 0000009c, parameter1 00000004, parameter2 80545ffo, parameter3 b2000010, parameter4 00010c0f.
My system spec is......
AMD Athlon 64fx processor
Gigabyte K8 triton nForce 3 motherboard
Windows XP pro will use xp64 when all the software is ready for 64bit use
2gb Kingston ram
GeForce 6200 AGP8X 256mb graphics
1 x Maxtor diamond10 - 250gb HDD7200rpm
1 x Maxtor maxline 2 - 300gb storage drive
2 x Pioneer 109 dvd/cdrw
Soundblaster Audidgy ZS Platinum Pro - model SB0360
500w ATX Power supply
5 cooling fans
ive done all sorts of tests to see if it was a hardware conflict i was having as originally my computer crashed when i had the soundblaster audidgy installed, but since ive taken it out the crashes had stopped until yesterday. ive now taken 3 sticks of ram out of my machine tonight and it has run ok with just 512mb ram and no sound blaster but as soon as i reinstall the parts the problems will start back up.
due to how long ive been trying to sort this problem and had no joy im now starting right at the very bottom and any help in identifying the error code above would greatly apprieciated.
Thanks....
Benson - www.djbenson.com
The problem is now that it is all up and partly runnin im having major problems with system crashes and freeze ups.... ive tried every forum i can think of for help but to no avail.
The error message i get when i check in the event viewer is.....
Error code 0000009c, parameter1 00000004, parameter2 80545ffo, parameter3 b2000010, parameter4 00010c0f.
My system spec is......
AMD Athlon 64fx processor
Gigabyte K8 triton nForce 3 motherboard
Windows XP pro will use xp64 when all the software is ready for 64bit use
2gb Kingston ram
GeForce 6200 AGP8X 256mb graphics
1 x Maxtor diamond10 - 250gb HDD7200rpm
1 x Maxtor maxline 2 - 300gb storage drive
2 x Pioneer 109 dvd/cdrw
Soundblaster Audidgy ZS Platinum Pro - model SB0360
500w ATX Power supply
5 cooling fans
ive done all sorts of tests to see if it was a hardware conflict i was having as originally my computer crashed when i had the soundblaster audidgy installed, but since ive taken it out the crashes had stopped until yesterday. ive now taken 3 sticks of ram out of my machine tonight and it has run ok with just 512mb ram and no sound blaster but as soon as i reinstall the parts the problems will start back up.
due to how long ive been trying to sort this problem and had no joy im now starting right at the very bottom and any help in identifying the error code above would greatly apprieciated.
Thanks....
Benson - www.djbenson.com
umm i have no idea if this program works but you can try it, it claims that it will take an error code and give you a description of the error you are having. http://www.gregorybraun.com/MSWinErr.html
<--edit wrong type of error messages sorry.
<--edit wrong type of error messages sorry.
For now leave the sound card out - no need to complicate things more with something not necessary to run the system. Personally when I'm troubleshooting hardware I take everything off except a hard drive, RAM chip and video card...you might want to do this too and also don't drive yourself nuts trying to troubleshoot what could ultimately end up being a loose cable somewhere, save yourself some hassle and disconnect everything you don't need to run the system, put your power supply on a UPS and check all your connections twice before you do anything else! You can always go back to working on other issues like the sound card once the system is stable again. Based on that error and what you've said here the problem sounds like memory to me. You're on the right track - you're answering your own question here. If you take the memory out and it works with no error then you can make an educated guess that the conflict is something to do with the memory. I would start by detaching all memory chips except one and then start adding them back one-by-one until your error pops up. When the error shows up you know more about where it is coming from. If it's when you put the fourth RAM chip in, for instance, then it's probably either that dimm slot or the RAM chip itself so try the same ram chip in slot 3 and see if the error pops up...if not it's probably the slot...this is just an example but you get the idea. Memory is one of those things I find very hard to troubleshoot because the same ram chip that works fine 3 times in a row is hard to pick out as a point of failure when it doesn't work the 4th time - I've had this happen many times...you just have to be a smart, thorough detective. I've found I have to go one chip at a time and one slot at a time with numerous reboots sometimes to identify a failing ram chip or slot. A failing slot can be equally frustrating and hard to identify. Good luck!
•
•
Join Date: Aug 2005
Posts: 8
Reputation:
Solved Threads: 0
Been testing these sticks now for approximatly 24hrs now, and im even more confussed about the state of my system than when i started...
I have 1 stick that the pc wont boot up with, i have 3 that all test ok, but out of the 3 that test ok 1 of them was in the machine being tested while i was taking me mrs to work and when i got home there were no errors reported but the computer had crashed again in bios mode during the test....
ive just tried to get the machine to boot up again with a different stick inserted but all im getting is error beeps and no boot, so now im totally confused, could i have a fauly motherboard or dodgy bios.
when we first built the pc it wouldn't boot up at all until we downloaded the latest bios update for it and its run very unstable ever since...
I have 1 stick that the pc wont boot up with, i have 3 that all test ok, but out of the 3 that test ok 1 of them was in the machine being tested while i was taking me mrs to work and when i got home there were no errors reported but the computer had crashed again in bios mode during the test....
ive just tried to get the machine to boot up again with a different stick inserted but all im getting is error beeps and no boot, so now im totally confused, could i have a fauly motherboard or dodgy bios.
when we first built the pc it wouldn't boot up at all until we downloaded the latest bios update for it and its run very unstable ever since...
•
•
•
•
Originally Posted by Dj_Benson
I have 1 stick that the pc wont boot up with, i have 3 that all test ok, but out of the 3 that test ok 1 of them was in the machine being tested while i was taking me mrs to work and when i got home there were no errors reported but the computer had crashed again in bios mode during the test....
ive just tried to get the machine to boot up again with a different stick inserted but all im getting is error beeps and no boot, so now im totally confused, could i have a fauly motherboard or dodgy bios.
![]() |
Other Threads in the Windows NT / 2000 / XP Forum
- Previous Thread: Setup Outlook Signature for Domain Users
- Next Thread: Windows wont boot
| Thread Tools | Search this Thread |
.net 3.5 3daccelertion 2007 2010 a.exe alaris apache application appstore arm auto automatically black blue book cellphones collaboration computer computerfreezes crash cursor deployment desktop desktops dns domain dotnetnuke drive eartlink error errors features folder fontmanagers fonts format framework gadgets intel interoperability killprocess laptop latitude linux load login mac microsoft minimalizes mobile monitor motionle1600 netbooks novell nvidia open operatingsystems osx outlook palm partition patch printer product raid rds remotedesktop remotedesktopconnection repair replacingraiddrive retrieve screen server. simplifiedchinese sp1 unreadable update usb verizon videodrivers videogames virtual virus vista visual vulnerability wab webos weecam win win32/heur window windows windows7 windowsxp windowsxpnotstartingup. worm xp xpde






