reboot instead shut down

By gab2006
Oct 9, 2006
  1. after reading the *.dmp file i've got this

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

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

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Thu Oct 5 15:36:07.281 2006 (GMT+3)
    System Uptime: 0 days 1:08:34.895
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {1c, 2, 1, 8053b885}

    Unable to load image win32k.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for win32k.sys
    Probably caused by : win32k.sys ( win32k!vFill_IFIMETRICS+c10 )

    Followup: MachineOwner

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

    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.
    Arg1: 0000001c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 8053b885, address which referenced memory

    Debugging Details:

    WRITE_ADDRESS: 0000001c


    8053b885 ff4b1c dec dword ptr [ebx+1Ch]





    LAST_CONTROL_TRANSFER: from a84bdda4 to 8053b885

    a84bdd68 a84bdda4 80524bc1 00000000 e1000000 nt!MiPurgeTransitionList+0x5d
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a84bdd6c 80524bc1 00000000 e1000000 81f09da0 0xa84bdda4
    a84bdda4 804eb58e c0001da8 0076a000 00000000 nt!MiEnsureAvailablePageOrWait+0x47
    a84bde68 804f3500 e1d50728 008affff 00000000 nt!CcWorkerThread+0x1b8
    a84bdf14 80572e26 81f09da0 81f10ae0 82101ce8 nt!MiInsertVad+0x185
    a84bdf58 80575b45 81f10b10 81f10b60 00000000 nt!NtQueryInformationFile+0x1de
    a84bdf6c bf8c0f45 81f09da0 005b0000 82101ce8 nt!CmpSetValueKeyExisting+0x146
    a84bdfa0 bf8c102e 81f09da0 00000000 82101cd0 win32k!vFill_IFIMETRICS+0xc10
    a84bdfbc 80580605 a84be000 82101cd0 823c6ad0 win32k!vFill_IFIMETRICS+0xcf9
    a84bdfe8 80582a03 bf8c0fec a84be000 00000000 nt!NtCompleteConnectPort+0xc0
    a84be014 80566901 81f09da0 82101ce8 000f01ff nt!NtNotifyChangeKey+0x26
    a84be044 80566aab 81f09da0 82101ce8 823c6ad0 nt!RtlUpcaseUnicodeString+0xcd
    a84be06c 80566b1c e10d2690 82101ce8 0000002c nt!RtlpAtomMapAtomToHandleEntry+0x2f
    a84be0b4 80566b66 0000002c 00000000 00000000 nt!NtRemoveIoCompletion+0x60
    a84be0c8 804de7ec 0000002c a84be160 804dc8c1 nt!NtRemoveIoCompletion+0xbc
    a84be0d4 804dc8c1 badb0d00 a84be14c fffffea8 nt!KiUnexpectedInterrupt65+0x2
    a84be160 bf820e5e e1095008 e1095008 81f04da8 nt!KiTimerExpiration+0x44
    a84be188 bf820f06 e1095008 00000000 81f04da8 win32k!zzzBltValidBits+0x42
    a84be1a4 80582e08 81f09da0 00000000 81d70e88 win32k!zzzBltValidBits+0x117
    a84be250 80583150 40010004 a84be2ac 804e60e9 nt!NtNotifyChangeDirectoryFile+0x221
    a84be25c 804e60e9 81d70e88 a84be2a8 a84be29c nt!FsRtlNotifyUpdateBuffer+0x4
    a84be2ac 804de855 00000001 00000000 a84be2c4 nt!KiSaveProcessorControlState+0x58
    a84be2c4 7c90eb94 badb0d00 0007f988 00000000 nt!KiUnexpectedInterrupt75+0x7
    a84be2c8 badb0d00 0007f988 00000000 7ffdf6f4 0x7c90eb94
    a84be2cc 0007f988 00000000 7ffdf6f4 0000001d 0xbadb0d00
    a84be2d0 00000000 7ffdf6f4 0000001d 0000000c 0x7f988


    bf8c0f45 ?? ???


    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys


    SYMBOL_NAME: win32k!vFill_IFIMETRICS+c10

    FAILURE_BUCKET_ID: 0xA_W_win32k!vFill_IFIMETRICS+c10

    BUCKET_ID: 0xA_W_win32k!vFill_IFIMETRICS+c10

    Followup: MachineOwner

    I believe 450, it's new, because me old 1g athlon died(usb core died, and i have adsl modem) then i bought this 2.53 MHz celeron, with AMI BIOS I believe, this is ASRock 775Dual -880Pro mainboard; someone told me maybe i do not have the core parameters in the netwaork always and this new videocard needs quality parameters, i dont know
  2. Rik

    Rik Banned Posts: 3,814

    Have you made any recent additions or upgrades to your pc?
  3. gab2006

    gab2006 TS Rookie Topic Starter

    there are some changes, the most important, 1 DDR2 memory (now i have 2x256Mb) bought from different vendors, and not at last the video card ATI RADEON X550 (on PCI expres)
  4. Rik

    Rik Banned Posts: 3,814

    You need to make sure ALL your drivers are up to date!!!
    Also, what make and wattage psu are you using???
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...