Windows Restart Error

Discussion in 'Windows - General discussion' started by darkbamy, Jul 20, 2009.

  1. darkbamy

    darkbamy Guest

    since a short while my pc is randomly restarting with the Bcc code 1000000d1,so i thought it would be a windows problem (or the heat of the weather lately) so i reinstalled windows yesterday but now today the problem is back again.the computer runs fine all day only in the night its restarting so i searched google for it but couldt find any clear answer..i looked in my event log and saw it had somthing to do with faultrep.dll,so my question is : is there any solution to this problem or is it some hardware problem or is it indeed the heat?


    here is the whole error

    BCCode : 100000d1 BCP1 : 1EC082AB BCP2 : 00000002 BCP3 :00000000

    BCP4 : A354DB54 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

    also i would like to add the restart is also random its when im doing a game or when im doing nothing at all
     
  2. Vicious88

    Vicious88 Regular member

    Joined:
    Jan 25, 2007
    Messages:
    274
    Likes Received:
    0
    Trophy Points:
    26
    While you're researching an answer, you could try seeing if putting "Shutdown -A" into your run window won't help. In most cases, this will abort active shutdown commands and prevent future ones from being initiated untill the computer is manually shutdown (holding power for 10 seconds).

    If you use the Shutdown -A command and find that your computer hasn't restart itself during the night, than you now know that something is initiating a shutdown command, and odds are it's a virus that you had prior to your windows re-install and re-contracted afterwards by either failing to scan backup files, downloading it again via the internet, or visiting shaky websites and downloading content from them.

    If the shutdown -a command DOESN'T help, than I'd go ahead and say that the problem lies elsewhere...

    I'll try and re-search your problem to come up with a better answer, but for a temporary fix, this is the best I can suggest right now.
     
  3. darkbamy

    darkbamy Guest

    shutdown-a? i never heard of it.
    but im just worried that it is an hardware problem a while ago my motherboard had a little ''shock'' so it was back to default now my theory is...if the motherboard was indeed broken it would have died by now if im correct

    and the weirdest part is...even microsoft dosnt know what it is...atleast the error code or the ID (1003) of it..when it showed up i tried to send it with the pop up error (with the option sned or not send) so i did send it and nothing...i did it with eventlog...also nothing
     
    Last edited by a moderator: Jul 21, 2009
  4. Vicious88

    Vicious88 Regular member

    Joined:
    Jan 25, 2007
    Messages:
    274
    Likes Received:
    0
    Trophy Points:
    26
    Yeah, I'm having a bit of a tough time researching it myself...

    I hate to say it, but the problem may in fact lay with the hardware.

    If your computer surged, it could have easily caused a problem to a piece of hardware that only triggers on your end periodicly. An intermittent problem, if you're familiar with the term.

    Intermittent problems can be things like Capacitors that blank out under certain loads, resitors that blank out under certain loads, or even completed ICs that simply fail out with the right stimulation.

    So while it's begining to look like a hardware problem, I don't know that I'd just to blaming the motherboard just yet. I don't know what you have available in terms of spare computer parts, but you may want to begin a hardware diagnostic on your computer.

    And here I begin giving away business secrets (online no less)...

    A Basic Hardware Diagnostic:

    Warning: Before working on the inside of a computer, make sure it is completely unplugged from power, and be sure to ground any static out of your body by touching the exposed metal of the casing BEFORE handling any componants. Failure to ground static can result in damage to hardware, and in some cases, damage to yourself.

    When I do a hardware diagnostic on a customer's computer, I start by completely unhooking the power supply from the board and all devices, and then hooking it up to a power supply tester. If you don't have a power supply tester, try swapping it out temporarily with one that you know is good.

    A power supply can be bad and still provide power to the board. If the power supply tests bad, or your system runs fine on a different power supply, then you've found and solved the bulk of the problem. Note: It is possible, and even somewhat likely, that a bad power supply can lead to a bad motherboard or device.

    If you've gotten this far, but the problem remains, there is still a chance that the problem lies somewhere OTHER than the motherboard. So continue on with the diagnostic untill you can identify the problem...

    The next step of a hardware diag is to remove all unnecessary componants from the board -- this means the removal of all secondary harddrives, PCI devices, as well as sound and video devices (if the motherboard supports onboard video, if it does not, you obviously can't remove the video card without loosing the ability to see what's going on).

    Once the computer has been stripped to it's bare running essentials (motherboard, RAM, CPU, HARDDRIVE), load it up and see if it works without problem in this much more basic form. If your computer is STILL not working as it should, you may try replacing RAM just for good measure if you have some extra laying around, but odds are the problem now lies with your motherboard and/or harddrive. If it works without any hardware-related failures or shutdowns then you've ruled out all the active componants as possible culprits.

    To narrow your suspect list further shut down the computer, add a previously removed device, such as a PCI card, and restart the computer. Continue this untill you break it again. The device that triggers the break is the source of your problem.

    I honestly couldn't tell you the number of "dead" motherboards that have been brought back to life simply by unplugging a PCI device. If you've got an old 56k modem card in the computer collecting dust, and the problem falls down to a PCI device, I'd bet you money that it's your culprit. From what I've seen it's almost always either an old dialup card or (if the computer was surged with a somewhat serious ammount of power) one of the older nvidia cards or Creative Soundblaster cards... I work on a lot of older computers, and have lined the bottom of the trashcan in my shop with old burned out nvidia geforce 4 MX 440's before. They don't like surges.

    Well I've given away the secrets to a hardware diagnostic that more thorough than what most any of my competitors will perform - so make good use of it and save your computer.

    Hope I've been of some help.
     
  5. darkbamy

    darkbamy Guest

    woow thats allot of things...maybe its just better for me to just buy a new pc...i mean the thing works fine just i cant upgrade the AGP anymore...so im thinking of just buying new parts and be happy with those hehe.

    thanks allot for the help but when i was done reading i was already tired in my head of doing all those stuff.anyways thanks again
     

Share This Page