Random restarts, advice PLEASE!

By Larryhud ยท 8 replies
Aug 17, 2006
  1. Bought a new pc, spec as follows:

    Athlon (Venice) XP 3800+
    2 GB RAM DDR 400Mhz
    nVidia GeForce 7600 GT 256MB (single card)
    SB Audigy
    PSU = 300W

    I installed the software myself, i.e. XP 2003 Pro, Office 2003 Pro and some virus software including a firewall. Everything is patched up to date, including all virus definitions.

    First two weeks were ok, no problem. I believe the problems started when I updated the graphic card drivers to 91.31 from ??

    I kept getting random restarts, not during a game, but when opening IE, or Windows explorer. Also, got one opening the DVD drive. Every half hour or so.

    I searched the web consistently. So much diverse advice! Could be the PSU, a faulty Graphics card (GC), bad drivers, corrupt RAM, overheating etc.

    Every case seems to have differrent symptons, so I am hoping if I post mine, someone may have had exactly the same thing happen to them!

    The error I got reads:

    BCCode : 1000007f BCP1 : 00000008 BCP2 : 80042000 BCP3 : 00000000
    BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

    When I sent the result to MS they said it was a faulty video driver.

    I have checked the RAM with memcheck and it seems fine. I ran Prim95 today for half hour, seemed fine. I did however start browsing the net whilst it was going, it rebooted with the same problem!

    I have also tried adjusting the latency of the RAM, no difference. When I changed the drivers to 84.21, it seems far more stable, but still will crash once/twice a night. Taking MS' advice, I have lowered the hardware accleration one notch and so far, so good.... but has only been an hour!

    However, I haven't bought a new pc, if I have turn the acceleration down and run on old drivers!

    I am seriously considering getting a much better power supply, 400W +. However, even though it is widely touted as a solution, I have never read anyone who said...'changed the supply and everything works now..', so I am dubious.

    I don't believe it is an overheating problem, as the pc is brand new. My inclination is either faulty RAM or faulty/underated PSU. Actually, I keep changing my mind!!?

    One thing is that it rebooted due to the DVD tray opengin which I believe suggests it IS the PSU. IS that a reasonable assumption?

    Also, do never graphic card drivers, draw more power? If so, that would support the theory I guess!?

    Please, please, any advice greatly appreciated!


  2. rki

    rki TS Rookie Posts: 18

    1) -Go to start -> control panel -> system > Advance
    -> startup and system recovery.

    Under 'sytem failure' unclick the 'Automatic restart'
    Under 'write debugging information' choose 'small memeory dump 64kb'

    Now what this does is that when there's a failure the system dosen't reboot itself immediately, you rather get a BSOD telling the full info on what might have caused the reboot. Allowing you to read if its a driver issue or hardware.
    Now, you will have your dumps created and dumped to the directory They are usually located in %systemroot%/minidump C:\WINDOWS\Minidump

    2) -You could also try debugging dumps by running the Microsoft Debugging Tools.
    Here's is how to debug your dumps http://forums.majorgeeks.com/showthread.php?t=35246

    I hope this does help.
  3. Larryhud

    Larryhud TS Rookie Topic Starter

    Actually I did uncheck that box, but it still rebooted anyway?!

    When I sent the error message (via system in the event viewer ) to MS, the response was...

    Product: Windows Operating System
    Event ID: 1003
    Source: System Error
    Version: 5.2
    Symbolic Name: ER_KRNLCRASH_LOG
    Message: Error code %1, parameter1 %2, parameter2 %3, parameter3 %4, parameter4 %5.

    ???? I hate this thing!!
  4. rki

    rki TS Rookie Posts: 18

    -And did you do check the other thing I said - Under 'write debugging information' choose 'small memeory dump 64kb'

    -And when it reboots, you checked - C:\WINDOWS\Minidump
  5. Zeratul

    Zeratul TS Rookie Posts: 70

    uninstall the graphic card driver then reinstall the old one. i believe that your pc won't run slow as you think, i guess.

    i don't think it's a PS problem, because you said that the problem BEGAN after updating to new drivers
  6. Larryhud

    Larryhud TS Rookie Topic Starter


    I rolled back the graphics card driver to the older version earlier this evening
    (84.21), as I believe this is more stable, i.e. NOT 91.xx.

    I did choose 'small memory dump' also, and I do have have some. As I was about to download the debugger, it restarted again but didn't blue screen!

    God I am going crazy! Will try to download now...
  7. rki

    rki TS Rookie Posts: 18

    Take it easy Larryhud.

    Just download the debugger and paste your logs here.

    We would see what we can do.
  8. Larryhud

    Larryhud TS Rookie Topic Starter

    Logs below:

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, 80042000, 0, 0}

    Unable to load image savrt.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for savrt.sys
    *** ERROR: Module load completed but symbols could not be loaded for savrt.sys
    Probably caused by : DVDAX.SYS ( DVDAX+9b5d )

    Followup: MachineOwner
  9. Larryhud

    Larryhud TS Rookie Topic Starter

    More detailed logs..

    kd> !analyze -v
    * *
    * Bugcheck Analysis *
    * *

    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    .trap on the appropriate frame will show where the trap was taken
    (on x86, this will be the ebp that goes with the procedure KiTrap)
    kb will then show the corrected stack.
    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 80042000
    Arg3: 00000000
    Arg4: 00000000

    Debugging Details:

    BUGCHECK_STR: 0x7f_8



    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from b53787ea to b5377b5d

    WARNING: Stack unwind information not available. Following frames may be wrong.
    b550e064 b53787ea 87575688 86fc9728 b550e1cc DVDAX+0x9b5d
    b550e074 804eddf9 87575688 86fc9728 86fc9990 DVDAX+0xa7ea
    b550e07c 86fc9728 86fc9990 b5378552 86fc9990 nt!IopfCallDriver+0x31
    b550e1cc b53787ea 87697f08 86fc9728 b550e334 0x86fc9728
    b550e1dc 804eddf9 87697f08 86fc9728 86fc99b4 DVDAX+0xa7ea
    b550e1e4 86fc9728 86fc99b4 b5378552 86fc99b4 nt!IopfCallDriver+0x31
    b550e334 b53787ea 876dcad0 86fc9728 b550e49c 0x86fc9728
    b550e344 804eddf9 876dcad0 86fc9728 86fc99d8 DVDAX+0xa7ea
    b550e34c 86fc9728 86fc99d8 b5378552 86fc99d8 nt!IopfCallDriver+0x31
    b550e49c b53787ea 876ee490 86fc9728 b550e604 0x86fc9728
    b550e4ac 804eddf9 876ee490 86fc9728 86fc99fc DVDAX+0xa7ea
    b550e4b4 86fc9728 86fc99fc b5378552 86fc99fc nt!IopfCallDriver+0x31
    b550e604 b53787ea 8744d770 86fc9728 b550e76c 0x86fc9728
    b550e614 804eddf9 8744d770 86fc9728 86fc9a20 DVDAX+0xa7ea
    b550e61c 86fc9728 86fc9a20 b5378552 86fc9a20 nt!IopfCallDriver+0x31
    b550e76c b53787ea 87038c28 86fc9728 b550e8d4 0x86fc9728
    b550e77c 804eddf9 87038c28 86fc9728 86fc9a44 DVDAX+0xa7ea
    b550e784 86fc9728 86fc9a44 b5378552 86fc9a44 nt!IopfCallDriver+0x31
    b550e8d4 b53787ea 88c66a50 86fc9728 b550ea3c 0x86fc9728
    b550e8e4 804eddf9 88c66a50 86fc9728 86fc9a68 DVDAX+0xa7ea
    b550e8ec 86fc9728 86fc9a68 b5378552 86fc9a68 nt!IopfCallDriver+0x31
    b550ea3c b53787ea 87480f08 86fc9728 b550eba4 0x86fc9728
    b550ea4c 804eddf9 87480f08 86fc9728 86fc9a8c DVDAX+0xa7ea
    b550ea54 86fc9728 86fc9a8c b5378552 86fc9a8c nt!IopfCallDriver+0x31
    b550eba4 b53787ea 885529d8 86fc9728 b550ed0c 0x86fc9728
    b550ebb4 804eddf9 885529d8 86fc9728 86fc9ab0 DVDAX+0xa7ea
    b550ebbc 86fc9728 86fc9ab0 b5378552 86fc9ab0 nt!IopfCallDriver+0x31
    b550ed0c b53787ea 87d4dcf0 86fc9728 b550ee74 0x86fc9728
    b550ed1c 804eddf9 87d4dcf0 86fc9728 86fc9ad4 DVDAX+0xa7ea
    b550ed24 86fc9728 86fc9ad4 b5378552 86fc9ad4 nt!IopfCallDriver+0x31
    b550ee74 b53787ea 8854f020 86fc9728 b550efdc 0x86fc9728
    b550ee84 804eddf9 8854f020 86fc9728 86fc9af8 DVDAX+0xa7ea
    b550ee8c 86fc9728 86fc9af8 b5378552 86fc9af8 nt!IopfCallDriver+0x31
    b550efdc b53787ea 8769ff08 86fc9728 b550f144 0x86fc9728
    b550efec 804eddf9 8769ff08 86fc9728 86fc9b1c DVDAX+0xa7ea
    b550eff4 86fc9728 86fc9b1c b5378552 86fc9b1c nt!IopfCallDriver+0x31
    b550f144 b53787ea 875bdf08 86fc9728 b550f2ac 0x86fc9728
    b550f154 804eddf9 875bdf08 86fc9728 86fc9b40 DVDAX+0xa7ea
    b550f15c 86fc9728 86fc9b40 b5378552 86fc9b40 nt!IopfCallDriver+0x31
    b550f2ac b53787ea 873d2a80 86fc9728 b550f414 0x86fc9728
    b550f2bc 804eddf9 873d2a80 86fc9728 86fc9b64 DVDAX+0xa7ea
    b550f2c4 86fc9728 86fc9b64 b5378552 86fc9b64 nt!IopfCallDriver+0x31
    b550f414 b53787ea 87774020 86fc9728 b550f57c 0x86fc9728
    b550f424 804eddf9 87774020 86fc9728 86fc9b88 DVDAX+0xa7ea
    b550f42c 86fc9728 86fc9b88 b5378552 86fc9b88 nt!IopfCallDriver+0x31
    b550f57c b53787ea 88af7020 86fc9728 b550f6e4 0x86fc9728
    b550f58c 804eddf9 88af7020 86fc9728 86fc9bac DVDAX+0xa7ea
    b550f630 ba70c997 00000170 88aa9dc8 00000006 nt!IopfCallDriver+0x31
    b550f6e4 b53787ea 88f33720 86fc9728 b550f84c atapi!AtapiSendCommand+0x267
    b550f6f4 804eddf9 88f33720 86fc9728 86fc9bd0 DVDAX+0xa7ea
    b550f738 804eee19 86fc9bac 804eee46 89de4e50 nt!IopfCallDriver+0x31
    b550f84c b53787ea 8778bbd0 86fc9728 b550f9b4 nt!IoStartPacket+0x7d
    b550f85c 804eddf9 8778bbd0 86fc9728 86fc9bf4 DVDAX+0xa7ea
    b550f8fc 8054482f 00000000 ffdff120 00000000 nt!IopfCallDriver+0x31
    b550f9b4 b53787ea 88733f08 86fc9728 b550fa08 nt!ExAllocatePoolWithTag+0x7af
    b550f9c4 804eddf9 88733f08 86fc9728 86fc9728 DVDAX+0xa7ea
    b550f9d4 80577ad6 88b4fd00 89e65040 00000001 nt!IopfCallDriver+0x31
    b550fa08 805b0beb 89e42830 88733f08 00000001 nt!IopCloseFile+0x27c
    b550fa38 805b053f 89e42830 88b4fd18 89e65040 nt!ObpDecrementHandleCount+0x119
    b550fa60 805b05dd e1001c48 88b4fd18 00000474 nt!ObpCloseHandleTableEntry+0x14d
    b550faa8 805b06ee 00000474 00000000 00000001 nt!ObpCloseHandle+0x87
    b550fabc 804edff1 80000474 00000000 88c789e0 nt!ObCloseHandle+0x12
    b550faf0 8056a282 88b4fd18 80000474 00000000 nt!IoCreateStreamFileObjectEx+0x109
    b550fb04 b7ab424d 88c789e0 00000000 e1dd2488 nt!IoCreateStreamFileObject+0x12
    b550fb10 e1dd2488 e17178c8 00000001 e1dd24dd savrt+0x1524d
    00000000 00000000 00000000 00000000 00000000 0xe1dd2488


    b5377b5d 56 push esi


    FOLLOWUP_NAME: MachineOwner





    FAILURE_BUCKET_ID: 0x7f_8_DVDAX+9b5d

    BUCKET_ID: 0x7f_8_DVDAX+9b5d

    Followup: MachineOwner
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...