TechSpot

Computer Reseting

By GazUK
Jul 27, 2006
  1. Dear Team,

    Many thanks for the useful information you provide. I have been reading some of the threads regarding 'Computer Resets' and decided to join the community to be of help and hopefuly to be helped as can be seen from below.

    I have a newly refurbished industrial PC type Kontron/ICS. The only original items from 1997 are the floppy disk, chassis and main cooling fans. Please find attached the spec files and system config files. The OS is Win 2000 PRO SP4. The new PSU is ATX12V-AC400-CE: 400WATX PSU (PFC & P4 COMPATIBLE). The NIC is Intel Dual Server configured as teaming.

    I have refurbished 7 other of these PCs using the same components, all of which are working without fault 24/7 since Mar-2006. However this particular one resets/re-boots itself approximately once every 2-3 weeks. Attached are two of the Minidump files copied as text.

    My problem is that I am not fluent in Minidump analysis, and while the problem may be staring at me I can't make head or tails of the 0x0000000a stop code and which process/driver may be causing it. Then I would be grateful for any assistance you can provide in its interpreatation.

    The later of the two minidum file was taken while running Eurosoft's QA+Win32diagnostic software which then reset during the Clock/Calander test. Not sure if this is relevant but the 'Local' shown in the System Information shows it to be United States while in the Control Panel both Regional and Date/time are set to U.K. Also during the second failure, there was no network connection present. I have changed over the RAM for another module. The system only uses a single RAM module of size 512M. The HD is Maxtor 40G located in a removable STORCASE drive. I have brushed over the main components using a heatgun in an attempt to stimulate any heat associated problem but no luck. All fans are working properly as confirmed by the chassis' own heat and fan monitoring system.

    In one of the related threads you suggest in Startup & Recovery, unchecking the 'Automatic Re-boot' and setting the 'Write Debug Info' to none. I have now dine this and await the error message. Any help you can provide from the Minidump files would be much appreciated. Thanks.
     
  2. altheman

    altheman TS Rookie Posts: 425

    Post the original dump files, under C:\Windows\Minidump.
    Unfortuanally I can't debug Win2k dumps, bacause I don't use it. But hopefully someone else'll have a look at 'em.
     
  3. GazUK

    GazUK TS Rookie Topic Starter

    Please also find attached the original dump files...thanks altheman
     
  4. GazUK

    GazUK TS Rookie Topic Starter

    Please find attached the original .dmp files ... thanks altheman
     
  5. Per Hansson

    Per Hansson TS Server Guru Posts: 1,929   +186

    As you can see it is referencing the same memory area, either you have a single bad memory block in your RAM or it is driver related.

    Since you said you tried different sticks of RAM I would test newer or older drivers for the system...

    Mini042106-01.dmp;
    Code:
    Microsoft (R) Windows Debugger  Version 6.3.0017.0
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Documents and Settings\Administratör\Skrivbord\Mini042106-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: C:\Program\Debugging Tools for Windows\2000Symbols
    Executable search path is: 
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: symbols timestamp is wrong 0x3ee650b3 0x427b58bb for ntoskrnl.exe
    Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
    Kernel base = 0x80400000 PsLoadedModuleList = 0x80484520
    Debug session time: Fri Apr 21 19:56:02 2006
    System Uptime: not available
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: symbols timestamp is wrong 0x3ee650b3 0x427b58bb for ntoskrnl.exe
    Loading Kernel Symbols
    ............................................................................................
    Loading unloaded module list
    ..................................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffffc, 1c, 0, 8043242f}
    
    Probably caused by : ntoskrnl.exe ( nt!KiInitializeContextThread+63 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffffc, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8043242f, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: unable to read from 80481518
    unable to read from 804811c8
    unable to read from 804810a8
    unable to read from 80472de0
    unable to read from 804810c0
    unable to read from 804811c4
    unable to read from 80472de4
    unable to read from 80481284
    unable to read from 804814b8
     fffffffc 
    
    CURRENT_IRQL:  1c
    
    FAULTING_IP: 
    nt!KiInitializeContextThread+63
    8043242f ??               ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    LAST_CONTROL_TRANSFER:  from 00000000 to 8046987c
    
    STACK_TEXT:  
    ae776c7c 00000000 fffffffc 0000001c 00000000 nt!ExecuteHandler+0x10
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nt!KiInitializeContextThread+63
    8043242f ??               ???
    
    FOLLOWUP_NAME:  MachineOwner
    
    SYMBOL_NAME:  nt!KiInitializeContextThread+63
    
    MODULE_NAME:  nt
    
    IMAGE_NAME:  ntoskrnl.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  3ee650b3
    
    BUCKET_ID:  0xA_nt!KiInitializeContextThread+63
    
    Followup: MachineOwner
    ---------
    
    Mini072606-01.dmp;
    Code:
    Microsoft (R) Windows Debugger  Version 6.3.0017.0
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Documents and Settings\Administratör\Skrivbord\Mini072606-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: C:\Program\Debugging Tools for Windows\2000Symbols
    Executable search path is: 
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: symbols timestamp is wrong 0x3ee650b3 0x427b58bb for ntoskrnl.exe
    Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
    Kernel base = 0x80400000 PsLoadedModuleList = 0x80484520
    Debug session time: Wed Jul 26 13:31:21 2006
    System Uptime: not available
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: symbols timestamp is wrong 0x3ee650b3 0x427b58bb for ntoskrnl.exe
    Loading Kernel Symbols
    .................................................................................................
    Loading unloaded module list
    .................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {16c6e34, ff, 1, 16b4063}
    
    Probably caused by : ntoskrnl.exe ( nt!ExecuteHandler+10 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 016c6e34, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 016b4063, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: unable to read from 80481518
    unable to read from 804811c8
    unable to read from 804810a8
    unable to read from 80472de0
    unable to read from 804810c0
    unable to read from 804811c4
    unable to read from 80472de4
    unable to read from 80481284
    unable to read from 804814b8
     016c6e34 
    
    CURRENT_IRQL:  ff
    
    FAULTING_IP: 
    +16b4063
    016b4063 ??               ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    LAST_CONTROL_TRANSFER:  from 00000000 to 8046987c
    
    STACK_TEXT:  
    af473afc 00000000 016c6e34 000000ff 00000001 nt!ExecuteHandler+0x10
    
    
    FOLLOWUP_IP: 
    nt!ExecuteHandler+10
    8046987c ??               ???
    
    SYMBOL_STACK_INDEX:  0
    
    FOLLOWUP_NAME:  MachineOwner
    
    SYMBOL_NAME:  nt!ExecuteHandler+10
    
    MODULE_NAME:  nt
    
    IMAGE_NAME:  ntoskrnl.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  3ee650b3
    
    STACK_COMMAND:  kb
    
    BUCKET_ID:  0xD1_W_nt!ExecuteHandler+10
    
    Followup: MachineOwner
    ---------
    
    
    
     
  6. GazUK

    GazUK TS Rookie Topic Starter

    ...thanks for that Per. The systems RAM address range only stretches to 0x020000000, so this particular block looks like its on the PCI bus. I'll take a closer look around there. The bus has fitted an Intel Dual port Server adapter, a Single Port RS232 card and also a 8 Channel Muliport RS232 card.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

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