Maybe anyone can tell me how to get more information on my latest Blue screen.

Windbg resulted in : A driver is causing an inconsistent power state.

But I can't figure out which driver

We got this on 4 machines with this issue when shutting down or restarting windows. Disabling "power safe" function for the network cards seems to fix this blue screen on 3 of those. But one still pop up with the blue screens when shutting down.

The OS is Windows 2000 Server btw.

Analysis:

 !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000100, SubCode
Arg2: 884682e0
Arg3: 884682e0
Arg4: 88501990

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  100

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  WINLOGON.EXE

LAST_CONTROL_TRANSFER:  from 804907b3 to 80489980

STACK_TEXT:  
eb1bfae4 804907b3 883f9c0c 00000001 00000000 nt!IoBuildPoDeviceNotifyList+0x276
eb1bfb04 8049033f 00000000 eb1bfbf4 eb1bfc78 nt!PopSetDevicesSystemState+0x85
eb1bfbe0 80468309 00000005 00000004 c0000004 nt!NtSetSystemPowerState+0x329
eb1bfbe0 80432193 00000005 00000004 c0000004 nt!KiSystemService+0xc9
eb1bfc64 80490086 00000005 00000004 c0000004 nt!ZwSetSystemPowerState+0xb
eb1bfd48 80494cf8 00000005 00000004 c0000004 nt!NtSetSystemPowerState+0x70
eb1bfd58 80468309 00000001 00000000 00000000 nt!NtShutdownSystem+0x2e
eb1bfd58 77888e07 00000001 00000000 00000000 nt!KiSystemService+0xc9
0006fe90 01014c3d 00000001 00000001 00076460 ntdll!NtShutdownSystem+0xb
0006fea8 01014f6c 00000050 0000000b 0000000b winlogon!ShutdownMachine+0x165
0006ff04 0100e20f 00076460 0000000b 5ff90000 winlogon!Logoff+0x216
0006ff20 01007e8c 00076460 00000005 000739bc winlogon!MainLoop+0x1fb
0006ff58 0100af70 00071fc8 00000000 000739bc winlogon!WinMain+0x37a
0006fff4 00000000 7ffdf000 000000c8 00000100 winlogon!WinMainCRTStartup+0x156


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!IoBuildPoDeviceNotifyList+276
80489980 8b55ec          mov     edx,dword ptr [ebp-14h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!IoBuildPoDeviceNotifyList+276

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  427b58bb

FAILURE_BUCKET_ID:  0x9F_nt!IoBuildPoDeviceNotifyList+276

BUCKET_ID:  0x9F_nt!IoBuildPoDeviceNotifyList+276

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

0: kd> lmvm nt
start    end        module name
80400000 805a3100   nt         (pdb symbols)          downstream_store\ntkrnlmp.pdb\427B58BB1\ntkrnlmp.pdb
    Loaded symbol image file: downstream_store\ntkrnlmp.dbg\427B58BB1a3100\ntkrnlmp.dbg
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Fri May 06 13:44:59 2005 (427B58BB)
    CheckSum:         001A4BC8
    ImageSize:        001A3100
    File version:     5.0.2195.7045
    Product version:  5.0.2195.7045
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0407.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Betriebssystem Microsoft(R) Windows (R) 2000
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   5.00.2195.7045
    FileVersion:      5.00.2195.7045
    FileDescription:  NT-Kernel und -System
    LegalCopyright:   Copyright (C) Microsoft Corp. 1981-1999

I use a utility called BlueScreenView, retrieve the minidump file(s) and it can give some insight on the cause of the BSOD, drivers involved in each instance, a screenshot of the BSOD message, etc... Support for Windows 2000 stopped in 2010 if memory serves me correctly. if it's driver-related, I'd say it'll be hard to get any updated drivers, you'd probably have to revert to an earlier driver, maybe introducing other problems.

I would advise a new server with Hyper-V and move our old servers to virtual machines

the BSOD data presented suggest a possible bad stick of memory, given the vintage of your servers it probably high time you modernized

Some more information: There are 4 PC's. All 4 have same setup.

Only one of them brings up this message. The drivers and the hardware is windows 2000 certified.

Moving to a "modern" system is out of discussion, we had troubles to find hardware that provides old 5V PCI.

Moving to a newer Windows is not of any possibility. There is no replacement for the measurement card yet, maybe planed for 2019, if I can trust the manufacturer.

You are all invited to write a Virtual driver for visualization.

The PC's don't have and will never have internet.