BSOD reporting without BSOD. Unbanal 0x0000009f?

Question

Windows

To my shame, I cannot solve the problem on my own and am writing here, since smoking numerous manuals did not help.
System: Win7 32x
Comp: Notebook Samsung r580
Problem (ridiculous) - every time you reboot, a message pops up about an incorrect shutdown of Windows a la BSOD.
Common error 0x0000009f .
But the most important - ACTUALLY I DO NOT SEE BSOD! I reboot normally, turn on and no pauses, screen flashes, etc. there are NO symptoms - only an error message when loading Windows and the creation of the corresponding Minidump.
Every conceivable action has been taken:

• Clean Boot shutdown of all disconnected devices
  two patches KB981848 and KB977186, new for me,
  the memory check in all modes did not reveal an error
  when restarting from Safe mode to normal and safe multiple times - the same
  sfc / scannow - the same!
  All firewood was scanned by the Uniblu driver scanner - all drivers are up to date.
  It feels like this is a glitch of such a plan - BSOD does not occur AT ALL - neither visually nor in fact, but the system thinks otherwise.
  I can't even see eventvwr when this BSOD occurs, at the moment of turning it off or on.
  BlueScreenView gives such information - the reason for ntkrnlpa.exe and how to disable it is unclear.:
  
  What is most interesting is also a problem withhalmacpi.dll .
  Standard WinDbg and kdfe can't cope with dump analysis.
  Symbols downloaded and installed - does not help.
  Can you help?
  Link to the dump (already 671 kb - too much for a dump ) : drop.io/abchg1o UPD: kdfe woke up:
  
  

  Microsoft Windows [Version 6.1.7600]<br/>
  © Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.<br/>
  <br/>
  Analyzing &quot;c:\Windows\Minidump\091810-15709-01.dmp&quot;, please wait... Done.<br/>
  <br/>
  Didn't find the answer. Try again with '-v' switch.<br/>
  Для продолжения нажмите любую клавишу . . .<br/>
  <br/>
  C:\Users\Admin&gt;kdfe.cmd c:\windows\minidump\091810-15709-01.dmp -v<br/>
  <br/>
  Microsoft ® Windows Debugger Version 6.12.0002.633 X86<br/>
  Copyright © Microsoft Corporation. All rights reserved.<br/>
  <br/>
  Loading Dump File [c:\Windows\Minidump\091810-15709-01.dmp]<br/>
  Mini Kernel Dump File: Only registers and stack trace are available<br/>
  <br/>
  DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`8373ead4?<br/>
  Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols<br/>
  <br/>
  Executable search path is: srv*C:\symbols*http://msdl.microsoft.com/download/sym<br/>
  bols<br/>
  Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible<br/>
  Product: WinNt, suite: TerminalServer SingleUserTS Personal<br/>
  Built by: 7600.16617.x86fre.win7_gdr.100618-1621<br/>
  Machine Name:<br/>
  Kernel base = 0x83618000 PsLoadedModuleList = 0x83760810<br/>
  Debug session time: Fri Sep 17 00:18:12.769 2010 (UTC + 3:00)<br/>
  System Uptime: 0 days 17:34:38.346<br/>
  Loading Kernel Symbols<br/>
  ...............................................................<br/>
  ................................................................<br/>
  ................................................................<br/>
  <br/>
  Loading User Symbols<br/>
  Loading unloaded module list<br/>
  ....<br/>
  0: kd&gt; kd: Reading initial command '!analyze -v; q'<br/>
  *******************************************************************************<br/>
  * *<br/>
  * Bugcheck Analysis *<br/>
  * *<br/>
  *******************************************************************************<br/>
  <br/>
  DRIVER_POWER_STATE_FAILURE (9f)<br/>
  A driver is causing an inconsistent power state.<br/>
  Arguments:<br/>
  Arg1: 00000003, A device object has been blocking an Irp for too long a time<br/>
  Arg2: 8619aa70, Physical Device Object of the stack<br/>
  Arg3: 8373eae0, Functional Device Object of the stack<br/>
  Arg4: d46a5170, The blocked IRP<br/>
  <br/>
  Debugging Details:<br/>
  ------------------<br/>
  <br/>
  DRVPOWERSTATE_SUBCODE: 3<br/>
  <br/>
  IMAGE_NAME: ntkrpamp<br/>
  <br/>
  DEBUG_FLR_IMAGE_TIMESTAMP: 0<br/>
  <br/>
  FAULTING_MODULE: 933b9000 ndiswan<br/>
  <br/>
  IRP_ADDRESS: d46a5170<br/>
  <br/>
  DEVICE_OBJECT: 8926e028<br/>
  <br/>
  DRIVER_OBJECT: 8924bdc8<br/>
  <br/>
  CUSTOMER_CRASH_COUNT: 1<br/>
  <br/>
  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT<br/>
  <br/>
  BUGCHECK_STR: 0x9F<br/>
  <br/>
  PROCESS_NAME: System<br/>
  <br/>
  CURRENT_IRQL: 2<br/>
  <br/>
  STACK_TEXT:<br/>
  8373ea94 83654054 0000009f 00000003 8619aa70 nt!KeBugCheckEx+0x1e<br/>
  8373eb00 836538e8 8373eba0 00000000 8374b280 nt!PopCheckIrpWatchdog+0x1f5<br/>
  8373eb38 8368204d 83759a20 00000000 ab757741 nt!PopCheckForIdleness+0x73<br/>
  8373eb7c 83681ff1 83741d20 8373eca8 00000001 nt!KiProcessTimerDpcTable+0x50<br/>
  8373ec68 83681eae 83741d20 8373eca8 00000000 nt!KiProcessExpiredTimerList+0x101<br/>
  8373ecdc 8368020e 003de4d6 862cb030 8374b280 nt!KiTimerExpiration+0x25c<br/>
  8373ed20 83680038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb<br/>
  8373ed24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38<br/>
  <br/>
  STACK_COMMAND: kb<br/>
  <br/>
  FOLLOWUP_NAME: MachineOwner<br/>
  <br/>
  MODULE_NAME: ntkrpamp<br/>
  <br/>
  FAILURE_BUCKET_ID: 0x9F_3_IMAGE_ntkrpamp<br/>
  <br/>
  BUCKET_ID: 0x9F_3_IMAGE_ntkrpamp<br/>
  <br/>
  Followup: MachineOwner<br/>
  ---------<br/>
  <br/>
  quit:<br/>
  Для продолжения нажмите любую клавишу . . .

  
  

Answer 1

here's a girl! :)
but on the problem: most likely bsod occurs at the moment the laptop is turned off - that's why you don't see it. very similar to the fact that the driver is messing up, I suspect that it is from a network card or Wi-Fi. try deleting them or just disable them in the manager and reboot the laptop. if the problem disappears, then it makes sense to roll back to the old firewood.
Well, I googled something slightly similar in Vista social.answers.microsoft.com/Forums/en-US/vistaperformance/thread/0401bdc2-09a3-4c12-b829-db9333f36391

Answer 2

Try disconnecting all peripherals from the computer, i.e. leave literally only the percentage, memory, vidyuhu, monitor, keyboard and mouse, and turn off the rest - network cards, printers, and so on. Will the error continue to appear? If not, then by connecting the devices one at a time, you will go to a specific device with the driver of which the problem is.
Also make sure that the power supply is sufficient for your configuration, also try connecting the system hard drive to a different power cable.

Answer 3

Is the system not deployed from the image? And then the problem with hal looks like as if they made an image on one piece of iron and deployed it on another.

Answer 4

try setting up a full memory dump and feeding it to windbg, a minidump usually isn't anything interesting.

Answer 5

> It feels like this is a glitch of such a plan - BSOD does not occur AT ALL - neither visually nor in fact, but the system thinks otherwise.
Have you disabled reboot on BSOD?

Answer 6

If the laptop is new, try updating the BIOS, often manufacturers are in a hurry and release it with a raw BIOS.
To be sure, update the firewood.
If everything is the same, go to the service center.

Answer 7

</The error appeared only yesterday. Prior to that, he plowed like an Ox without problems for several months. zaka September 18 at 3:49 pm

Remember what you put / deleted either from memory or from OS logs and rollback points. I would take out Hamachi for a start (he puts the driver into the system and the service). By the way, what version of Hamachi?
Give a list of the main drivers with versions and also the status of the digital signature. Well, to the heap and the BIOS version.
Is there an antivirus or firewall? Also bring them with versions.

Answer 8

There was a similar saga here: www.techsupportforum.com/microsoft-support/windows-vista-windows-7-support/478548-bsod-windows-7-0x0000009f.html
The Realtek driver turned out to be the culprit.
Hints: www.techsupportforum.com/microsoft-support/windows-vista-windows-7-support/473665-driver-verifier-windows-7-vista.html#post2670109
and http://msdn.microsoft.com/en- us/library/ff559329(d=lightweight,v=VS.85).aspx