Help Random Reboot Windows XP Pro

By maxsterling
Apr 20, 2006
Topic Status:
Not open for further replies.
  1. I have a major issue that I desperately want to solve. I have about 18 BRAND NEW PCs with EXACT same configuration (e.g. same Motherboard, graphics card, CPU, HD, RAM, PSU etc) and out of the 18 four are giving me random reboots. All the PCs were custom built. The Specs are:
    Intel Pentium IV 2.4 GHZ
    Intel Motherboard D865PCDL (i thought i would get intel MB and CPU thinking i would minimize incompatibilities but to my surprise i still have headaches)
    Windows XP PRO
    PowerColor ATI Radeon 9250 128mb/64bit
    512 RAM generic unknown name/brand
    PSU 300WATTS unknown name/brand
    No FDD, No CD/DVD rom drive. Its a bare bones PC in terms of pheriperals.

    Now the PC reboots completely random, that is without playing games or music files or anything, basically the desktop screen, it will just reboot on its own. I strongly feel it cannot be a bios issue because the other 14 PCs are ok and have the same BIOS and the drivers as well are all the same. To illustrate how random it can be, i had the PC on for 10 days straight and no reboot/crash/minidump. Then suddenly today it had 5 crashes. Again, no hardware changes at all. I thought, maybe overheat but then how come the 14 other PCs do not crash at all even when they are on 24/7.

    If anyone could even give a slight hint as to the problem much would be appreciated. Again, my basis for comparison is that 14 other PCs with exact same configuration are very STABLE. This leads me to think it cannot be a driver/bios issue. Besides, i am already running the latest bios as I mentioned these are brand new PCs. Many thanks for any info as I've read through various tips (memory test and cleaning were done) and attached are the most recent minidumps.


    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini042006-05.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Thu Apr 20 03:51:47.103 2006 (GMT-4)
    System Uptime: 0 days 3:22:40.796
    Loading Kernel Symbols
    ...............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ....................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {80000004, 804db9ff, bab2ebd0, 0}

    Probably caused by : ntoskrnl.exe ( nt!SwapContext+dc )

    Followup: MachineOwner
    ---------


    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini042006-04.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Thu Apr 20 00:28:34.362 2006 (GMT-4)
    System Uptime: 0 days 0:02:46.203
    Loading Kernel Symbols
    ..........................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {7fcdf05c, ff, 0, 7fcdf05c}

    Probably caused by : ntoskrnl.exe ( nt!KiDoubleFaultStack+2d50 )

    Followup: MachineOwner
    ---------



    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini042006-03.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Thu Apr 20 00:25:07.406 2006 (GMT-4)
    System Uptime: 0 days 0:02:57.984
    Loading Kernel Symbols
    ..........................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {0, 2, 0, 0}

    Probably caused by : tcpip.sys ( tcpip!TCBTimeoutdpc+f )

    Followup: MachineOwner
    ---------



    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini042006-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Thu Apr 20 00:21:24.469 2006 (GMT-4)
    System Uptime: 0 days 0:03:20.265
    Loading Kernel Symbols
    ..........................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {7fcdf05c, ff, 0, 7fcdf05c}

    Probably caused by : ntoskrnl.exe ( nt!KiDoubleFaultStack+2d50 )

    Followup: MachineOwner
    ---------


    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini042006-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Thu Apr 20 00:17:13.084 2006 (GMT-4)
    System Uptime: 0 days 2:44:17.312
    Loading Kernel Symbols
    ...........................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {7fcdf05c, ff, 0, 7fcdf05c}

    Probably caused by : ntoskrnl.exe ( nt!KiDoubleFaultStack+2d50 )

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


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.