The message on BSOD without the BSOD. Original 0x0000009f?

0 like 0 dislike
17 views
To my shame can't solve the problem yourself and write here, as Smoking of numerous manuals have not helped.

System: Win7 32x

Comp: Laptop Samsung r580


The problem (funny) — each time you restart message POPs up on the wrong end of a La Windows BSOD.

Common error 0x0000009f.


But the most important is ACTUALLY BSOD can'T SEE. Reboot normally, turn on and no pauses, flashes of the screen, etc. NO symptoms — only error message when you boot Windows and create the appropriate Minidump.

All possible actions were taken:

  • Clean Boot: disable all disable devices

    two new-to-me patch KB981848 and KB977186

    check memory on all modes, the error is not revealed

    when you repeatedly restart from Safe mode to normal and safe — the same thing

    sfc /scannow — likewise!


    All firewood presenile Unilowski driverscanner — all drivers current.


    The feeling that this is a glitch this BSOD does not occur at all, neither visually nor in fact, but the system thinks otherwise.

    I can't even eventvwr to see when going on this OFFICE is, at the time of shutdown or power-up.


    BlueScreenView gives this old — reason ntkrnlpa.exe and how to turn it off, it's unclear.:

    5e42e06c26720d2f5a8460253a086bd3.PNG


    That the most interesting another problem halmacpi.dll.


    Standard WinDbg and kdfe analysis dump do not.

    Symbols downloaded and installed — does not help.


    Can You help?

    Link to the dump (as many as 671 KB — a bit much for a core dump): drop.io/abchg1o


    Help, Komrad with me buns, simpy and laffki!

    UPD: kdfe woke up:

    Microsoft Windows [Version 6.1.7600]
    © The Microsoft (Microsoft Corp.), 2009. All rights reserved.

    Analyzing "c:\\Windows\\Minidump\\091810-15709-01.dmp", please wait... Done.

    Didn't find the answer. Try again with '-v' switch.
    To continue, press any key . . .

    C:\\Users\\Admin>kdfe.cmd c:\\windows\\minidump\\091810-15709-01.dmp -v

    Microsoft ® Windows Debugger Version 6.12.0002.633 X86
    Copyright © Microsoft Corporation. All rights reserved.

    Loading Dump File [c:\\Windows\\Minidump\\091810-15709-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff'8373ead4?
    Symbol search path is: srv*C:\\symbols*http://msdl.microsoft.com/download/symbols

    Executable search path is: srv*C:\\symbols*http://msdl.microsoft.com/download/sym
    bols
    Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x83618000 PsLoadedModuleList = 0x83760810
    Debug session time: Fri Sep 17 00:18:12.769 2010 (UTC + 3:00)
    System Uptime: 0 days 17:34:38.346
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................

    Loading User Symbols
    Loading unloaded module list
    ....
    0: kd> kd: Reading initial command '!analyze-v; q'
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 00000003, A device object has been blocking an Irp for too long a time
    Arg2: 8619aa70, Physical Device Object of the stack
    Arg3: 8373eae0, Functional Device Object of the stack
    Arg4: d46a5170, The blocked IRP

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

    DRVPOWERSTATE_SUBCODE: 3

    IMAGE_NAME: ntkrpamp

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAULTING_MODULE: 933b9000 ndiswan

    IRP_ADDRESS: d46a5170

    DEVICE_OBJECT: 8926e028

    Member of driver_object is: 8924bdc8

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x9F

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    STACK_TEXT:
    8373ea94 83654054 8619aa70 0000009f 00000003 nt!KeBugCheckEx+0x1e
    8373eb00 836538e8 8373eba0 8374b280 00000000 nt!PopCheckIrpWatchdog+0x1f5
    8373eb38 8368204d 83759a20 ab757741 00000000 nt!PopCheckForIdleness+0x73
    8373eb7c 83681ff1 83741d20 8373eca8 00000001 nt!KiProcessTimerDpcTable+0x50
    8373ec68 83681eae 83741d20 8373eca8 00000000 nt!KiProcessExpiredTimerList+0x101
    8373ecdc 8368020e 003de4d6 862cb030 8374b280 nt!KiTimerExpiration+0x25c
    8373ed20 83680038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
    8373ed24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38

    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: ntkrpamp

    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_ntkrpamp

    BUCKET_ID: 0x9F_3_IMAGE_ntkrpamp

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

    quit:
    To continue, press any key . . .

by | 17 views

7 Answers

0 like 0 dislike
now it's a girl!:)
\r
and the problem: most likely the bsod occurs at the time of shutdown of the laptop — because you can't see it. it is very likely that a great driver, I suspect that the network card or wifi. try to remove them or simply disable the Manager and rebootet laptop. if the problem goes away it makes sense to revert to the old wood.
\r
well googled something slightly similar happened in Vista social.answers.microsoft.com/Forums/en-US/vistaperformance/thread/0401bdc2-09a3-4c12-b829-db9333f36391
by
0 like 0 dislike
Try unplugging from the computer the entire periphery, i.e. leave just percent, memory, none, monitor, keyboard and mouse and everything else — network cards, printers, and other disconnect. The error will continue to appear? If not then continue connecting the devices one will be released on a specific device driver which is the problem.
\r
Make sure that the power supply is sufficient for your configuration, try to connect the system hard drive to another power cable.
by
0 like 0 dislike
The system is not deployed from an image? And that's the problem with hal looks like as if made a image on one piece of iron and launched another.
by
0 like 0 dislike
try to configure a complete memory dump and feeding it to windbg, minidump is usually nothing interesting in itself is not.
by
0 like 0 dislike
> I have the feeling that this is a bug this BSOD does not occur at all, neither visually nor in fact, but the system thinks otherwise.
And reboot when BSOD disabled?
\rimage
by
0 like 0 dislike
If a new laptop, try updating BIOS, manufacturers often in a hurry and produce crude BIOS.
To be sure, update your firewood.
If so, go to the service center.
by
0 like 0 dislike
</The error appeared only yesterday. Prior to that, worked like an Ox with no problems a few months. zaka September 18 at 15:49

Remember that set/deleted or memory or OS logs and rollback points. I would put Hamachi to start (he and the driver sticks to the system and service). By the way what version of Hamachi?
\r
Here is a list of the main drivers with versions as well as the status of the digital signature. Well pile up and the BIOS version.
Is there any antivirus or firewall? Also with versions get them.
by

Related questions

0 like 0 dislike
3 answers
asked Jun 4, 2019 by maverickcy
0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
asked May 3, 2019 by GooseTheDestroyer
110,608 questions
257,186 answers
0 comments
1,107 users