[SOLVED] Freeze and BSOD

Shortty

Active member
Joined
Jun 25, 2019
Posts
27
OS - window 10
x64
Original OS on system: Window 7 (full retail version)
Age of system: 11 year~
Age of (new) OS installation: Jul 2019

CPU: ?
Video card: NVIDIA GeForce GTX 550 Ti
Motherboard: ?
Power Supply: ?

System Manufacturer: ?
Exact model number: ?

Desktop

The freezes and BSOD happen long before the fixes (Jun 2019, on same forum) and update to window 10 (Jul 2019)

I will try to fill in the missing information as soon and as best as i can
 

Attachments

Update Windows 10 to version 1909 - https://support.microsoft.com/pl-pl/help/3159635/windows-10-update-assistant
1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 2 additional settings (Force pending i/o request and irp logging)
4. Select "Select driver names from a list"
5. Tick all 3rd party drivers and 7 Microsoft drivers (ntoskrnl.exe, hal.dll, hdaudbus.sys, npfs.sys, fltmgr.sys, storport.sys and storahci.sys)
6. Apply changes and reboot computer
 
i tried the step above, and "Window couldn't load correctly" screen appear and auto repair process was prompt afterward


Can't edit the first post so:
OS - window 10
x64
Original OS on system: Window 7 (full retail version)
Age of system: 11 year~
Age of (new) OS installation: since Jul 2019 (window 10)

CPU: Intel Core i5 Processor
Video card: NVIDIA GeForce GTX 550 Ti
Motherboard: Intel DP67BG Extreme Series
Power Supply: Ultra 750 Watt ATX

System Manufacturer: ? (Self-build by a friend)
Exact model number: ?

Desktop

Additional information:
PC was overclocked, i think
And running express script using a small SSD to make the regular HDD act like a SSD?
 
Last edited:
Hi Shortty,

Try to reboot. After 3 failed boot attempts you should be able to access the Recovery Environment automatically.

In the Recovery Environment.
  • click Troubleshoot
  • go to the advanced options
  • choose command prompt
  • enter the below command and press enter
    Code:
    verifier /reset
  • Reboot your system

If you get any error message or have issues along the way of doing the above, please let us know.
 
Before i do anything stupid =),
so i should try this
Update Windows 10 to version 1909 - https://support.microsoft.com/pl-pl/help/3159635/windows-10-update-assistant
1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 2 additional settings (Force pending i/o request and irp logging)
4. Select "Select driver names from a list"
5. Tick all 3rd party drivers and 7 Microsoft drivers (ntoskrnl.exe, hal.dll, hdaudbus.sys, npfs.sys, fltmgr.sys, storport.sys and storahci.sys)
6. Apply changes and reboot computer
again,

and then if it go in to the "Window couldn't load correctly" screen

then i will
Try to reboot. After 3 failed boot attempts you should be able to access the Recovery Environment automatically.

In the Recovery Environment.
  • click Troubleshoot
  • go to the advanced options
  • choose command prompt
  • enter the below command and press enter
    Code:
    verifier /reset
  • Reboot your system

If you get any error message or have issues along the way of doing the above, please let us know.


correct?
 
Yes, but there's a catch.

Driver verifier is quite an advanced tool for which preparations are required.

You already experienced one of the problems that may come with driver verifier, but one of the risks is that you ultimately could end up in a boot loop. This boot loop is due to drivers that are selected to be tested, which run at boot and make a mistake during the boot process. The tricky part of this is getting out of that.

Because of the tricky part, I can provide a couple of options for you to get out of them. A couple, because from time to time 1 or 2 of them don't work as expected. In the end it all comes down to the 'verifier /reset' command or using the GUI to do the same, how you get there is the difference really. For now, though, the recovery environment is sufficient, but please do prepare a bit more by configuring a system restore point and preparing a USB with installation media which can be used to repair computers as well.

To prepare a USB with installation media go to Download Windows 10. Expand "Using the tool to create installation media (USB flash drive, DVD, or ISO file) to install Windows 10 on a different PC (click to show more or less information) ". Please note that if you're going to use this option, when you see 'Install now' button click on 'Repair your computer'.


After preparing, please enable driver verifier again.
 
What is the indication that the Driver verifier was successfully completed?

There isn't; Driver Verifier will run as a background service running a number of tests on drivers. If a driver doesn't pass one of these tests, then you'll get a DV-generated BSOD.
 
i assume that, if the pc able to reboot successfully then maybe it a success?

Trying the step again, now,
Update Windows 10 to version 1909 - https://support.microsoft.com/pl-pl/help/3159635/windows-10-update-assistant ******(i thought i did before, but didn't)
1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 2 additional settings (Force pending i/o request and irp logging)
4. Select "Select driver names from a list"
5. Tick all 3rd party drivers and 7 Microsoft drivers (ntoskrnl.exe, hal.dll, hdaudbus.sys, npfs.sys, fltmgr.sys, storport.sys and storahci.sys) *****(didn't check all other drivers aside from microsoft one, the last time i done this)
6. Apply changes and reboot computer
 
i tried
Update Windows 10 to version 1909 - https://support.microsoft.com/pl-pl/help/3159635/windows-10-update-assistant
1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 2 additional settings (Force pending i/o request and irp logging)
4. Select "Select driver names from a list"
5. Tick all 3rd party drivers and 7 Microsoft drivers (ntoskrnl.exe, hal.dll, hdaudbus.sys, npfs.sys, fltmgr.sys, storport.sys and storahci.sys)
6. Apply changes and reboot computer

after 3 BSODs with stopcode: SYSTEM THREAD EXCEPTION NOT HANDLED
and have to go through these step,

Try to reboot. After 3 failed boot attempts you should be able to access the Recovery Environment automatically.

In the Recovery Environment.
  • click Troubleshoot
  • go to the advanced options
  • choose command prompt
  • enter the below command and press enter
    Code:
    verifier /reset
  • Reboot your system

If you get any error message or have issues along the way of doing the above, please let us know.

when i type in verifier /redet in cmd, it said no setting was change...

and then i have to restore with system restore after


what should i do next ?
 
Last edited:
Run the Sysnative BSOD app again and upload a new zip.
 
Was the update to 1909 before or after this bugcheck?
2020-02-26T10:12:11.462The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffff80000003, 0xfffff80004872380, 0xfffff00afaae5c58, 0xfffff00afaae54a0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 01de6af6-5074-4e94-a732-69a3597c2fed.

The 0x7E bugcheck is caused by a breakpoint (0xffffffff80000003 = breakpoint) which forced the system to crash. Funny enough the Windows Driver Framework driver wdf01000 forced this after detecting the HP mouse driver made an invalid operation.
Code:
Start memory scan  : 0xfffff00afaae4c38 ($csp)
End memory scan    : 0xfffff00afaae7000 (Kernel Stack Base)

               rsp : 0xfffff00afaae4c38 : 0xfffff80004883ee4 : nt!PspSystemThreadStartup$filt$0+0x44
               r14 : 0xfffff00afaae52e0 : 0xfffff800047d37b5 : nt!PspSystemThreadStartup+0x55
0xfffff00afaae4c38 : 0xfffff80004883ee4 : nt!PspSystemThreadStartup$filt$0+0x44
0xfffff00afaae4c50 : 0xfffff80004872380 : nt!DbgBreakPoint
0xfffff00afaae4c78 : 0xfffff8000484556c : nt!_C_specific_handler+0xac
0xfffff00afaae4ca8 : 0xfffff80005a5710c : Wdf01000!FxDriver::AddDevice+0x2c
0xfffff00afaae4cc0 : 0xfffff80004bc7f80 : "nt!Ports <PERF> (nt+0x51ef80)"
0xfffff00afaae4cd8 : 0xfffff800047d37b5 : nt!PspSystemThreadStartup+0x55
0xfffff00afaae4ce8 : 0xfffff80004873342 : nt!RtlpExecuteHandlerForException+0x12
0xfffff00afaae4d10 : 0xfffff00afaae52e0 : 0xfffff800047d37b5 : nt!PspSystemThreadStartup+0x55
0xfffff00afaae4d18 : 0xfffff8000476bf15 : nt!RtlDispatchException+0x4a5
0xfffff00afaae4d48 : 0xfffff8000471453d : nt!KeQueryCurrentStackInformationEx+0x6d
0xfffff00afaae4d68 : 0xfffff8000471453d : nt!KeQueryCurrentStackInformationEx+0x6d
0xfffff00afaae4d80 : 0xfffff80004bbcfac : "nt!Ports <PERF> (nt+0x513fac)"
0xfffff00afaae4d88 : 0xfffff80004bbcfac : "nt!Ports <PERF> (nt+0x513fac)"
0xfffff00afaae4da8 : 0xfffff80004be91f0 : "nt!Ports <PERF> (nt+0x5401f0)"
0xfffff00afaae4db0 : 0xfffff80004be91f0 : "nt!Ports <PERF> (nt+0x5401f0)"
0xfffff00afaae4db8 : 0xfffff800047144a8 : nt!RtlpGetStackLimits+0x28
0xfffff00afaae4e58 : 0xfffff80004871b5a : nt!KiStartSystemThread+0x2a
0xfffff00afaae4e88 : 0xfffff800046ba24a : nt!MiCommitPoolMemory+0x17a
0xfffff00afaae4f10 : 0xfffff80004b13400 : nt!MiSystemPartition
0xfffff00afaae4f20 : 0xfffff80004b13400 : nt!MiSystemPartition
0xfffff00afaae4f58 : 0xfffff800046c2b3a : nt!MiInsertPageInFreeOrZeroedList+0x60a
0xfffff00afaae5038 : 0xfffff800046be506 : nt!MiPfnShareCountIsZero+0x396
0xfffff00afaae5098 : 0xfffff800046bbd89 : nt!MiDeleteValidSystemPage+0x1f9
0xfffff00afaae50d8 : 0xfffff80004b13400 : nt!MiSystemPartition
0xfffff00afaae5108 : 0xfffff8000471def6 : nt!MiUnlockWorkingSetShared+0x66
0xfffff00afaae5138 : 0xfffff800046c4dc7 : nt!MiDeleteSystemPagableVm+0x387
0xfffff00afaae5198 : 0xfffff8000471453d : nt!KeQueryCurrentStackInformationEx+0x6d
0xfffff00afaae51a8 : 0xfffff80004b13400 : nt!MiSystemPartition
0xfffff00afaae51d8 : 0xfffff8000476fda4 : nt!RtlGetExtendedContextLength2+0x3c
0xfffff00afaae51e8 : 0xfffff800047c97b0 : nt!RtlpGetStackLimitsEx+0x14
0xfffff00afaae5218 : 0xfffff8000476bb6c : nt!RtlDispatchException+0xfc
0xfffff00afaae5270 : 0xfffff800046a9000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor <PERF> (nt+0x0)"
0xfffff00afaae5278 : 0xfffff800048454c0 : nt!_C_specific_handler
0xfffff00afaae52d0 : 0xfffff80004bc7f80 : "nt!Ports <PERF> (nt+0x51ef80)"
0xfffff00afaae52d8 : 0xfffff8000475c584 : nt!MiFlushTbList+0x2d4
0xfffff00afaae52e0 : 0xfffff800047d37b5 : nt!PspSystemThreadStartup+0x55
0xfffff00afaae52e8 : 0xfffff800046a9000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor <PERF> (nt+0x0)"
0xfffff00afaae52f0 : 0xfffff80004bc7f80 : "nt!Ports <PERF> (nt+0x51ef80)"
0xfffff00afaae5310 : 0xfffff800048454c0 : nt!_C_specific_handler
0xfffff00afaae5348 : 0xfffff80004872380 : nt!DbgBreakPoint
0xfffff00afaae5358 : 0xfffff800046a9000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor <PERF> (nt+0x0)"
0xfffff00afaae5360 : 0xfffff80004bd13e8 : "nt!Ports <PERF> (nt+0x5283e8)"
0xfffff00afaae5368 : 0xfffff80005a00000 : Wdf01000!_iob
0xfffff00afaae5370 : 0xfffff80005ab35ac : "Wdf01000!AuxpInitState <PERF> (Wdf01000+0xb35ac)"
0xfffff00afaae5378 : 0xfffff80005a00000 : Wdf01000!_iob
0xfffff00afaae5380 : 0xfffff80005ab47b8 : "Wdf01000!AuxpInitState <PERF> (Wdf01000+0xb47b8)"
0xfffff00afaae5388 : 0xfffff803078d0000 : HP8207_8307
0xfffff00afaae5398 : 0xfffff803078d0000 : HP8207_8307
0xfffff00afaae53a8 : 0xfffff803078d0000 : HP8207_8307
0xfffff00afaae53b8 : 0xfffff80005a00000 : Wdf01000!_iob
0xfffff00afaae53c0 : 0xfffff80005ab5604 : "Wdf01000!AuxpInitState <PERF> (Wdf01000+0xb5604)"
0xfffff00afaae53c8 : 0xfffff80005a00000 : Wdf01000!_iob
0xfffff00afaae53d0 : 0xfffff80005ab55f8 : "Wdf01000!AuxpInitState <PERF> (Wdf01000+0xb55f8)"
0xfffff00afaae53d8 : 0xfffff800046a9000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor <PERF> (nt+0x0)"
0xfffff00afaae53e0 : 0xfffff80004bda370 : "nt!Ports <PERF> (nt+0x531370)"
0xfffff00afaae53e8 : 0xfffff800046a9000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor <PERF> (nt+0x0)"
0xfffff00afaae53f0 : 0xfffff80004bf63d8 : "nt!Ports <PERF> (nt+0x54d3d8)"
0xfffff00afaae53f8 : 0xfffff800046a9000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor <PERF> (nt+0x0)"
0xfffff00afaae5400 : 0xfffff80004bf3990 : "nt!Ports <PERF> (nt+0x54a990)"
0xfffff00afaae5408 : 0xfffff800046a9000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor <PERF> (nt+0x0)"
0xfffff00afaae5410 : 0xfffff80004bf3954 : "nt!Ports <PERF> (nt+0x54a954)"
0xfffff00afaae5428 : 0xfffff80004770826 : nt!KdTrap+0x22
0xfffff00afaae5468 : 0xfffff800047704ae : nt!KiDispatchException+0x16e
0xfffff00afaae54f8 : 0xfffff80005a9f5c0 : Wdf01000!WPP_FxDeviceInitApi_cpp_Traceguids
0xfffff00afaae5508 : 0xfffff80005a3aee6 : Wdf01000!FxIsEqualGuid+0x16
0xfffff00afaae5520 : 0xfffff80005a9e430 :  !da ""WDF detected potentially invalid operation by %s.%s Dump the driver log (!wdflog...""
0xfffff00afaae5528 : 0xffff99892786efa0 :  !da "HP8207_8307"
0xfffff00afaae5538 : 0xfffff00afaae5e98 : 0xfffff80005a2f8c0 : Wdf01000!FxVerifierDbgBreakPoint+0x50
0xfffff00afaae5560 : 0xffff99892786efa0 :  !da "HP8207_8307"
0xfffff00afaae5568 : 0xfffff80004872380 : nt!DbgBreakPoint
0xfffff00afaae5598 : 0xfffff80004872380 : nt!DbgBreakPoint
0xfffff00afaae55c8 : 0xfffff800046ba24a : nt!MiCommitPoolMemory+0x17a
0xfffff00afaae5650 : 0x00440057003b003b :  !du ";;WD)(A;"
0xfffff00afaae5768 : 0xfffff800046b9b1d : nt!RtlpHpAllocVA+0x111
0xfffff00afaae5808 : 0xfffff800046b9b1d : nt!RtlpHpAllocVA+0x111
0xfffff00afaae5828 : 0xfffff800046b93c8 : nt!RtlpHpSegMgrCommit+0x108
0xfffff00afaae58f8 : 0xfffff8000476fda4 : nt!RtlGetExtendedContextLength2+0x3c
0xfffff00afaae5918 : 0xfffff80004790ce5 : nt!RtlpHpSegAlloc+0x3b5
0xfffff00afaae5938 : 0xfffff8000476fc9d : nt!RtlGetExtendedContextLength+0x2d
0xfffff00afaae5b10 : 0xfffff00afaae5d80 :  !du ";;WD)(A;"
0xfffff00afaae5b18 : 0xfffff8000487c51d : nt!KiExceptionDispatch+0x11d
0xfffff00afaae5c18 : 0xfffff800046db6c6 : nt!ExpAllocatePoolWithTagFromNode+0x56
0xfffff00afaae5c68 : 0xfffff80004872380 : nt!DbgBreakPoint
0xfffff00afaae5c80 : 0xfffff80004872380 : nt!DbgBreakPoint
0xfffff00afaae5ca8 : 0xfffff8000501bfbb : nt!VeAllocatePoolWithTagPriority+0x6b
0xfffff00afaae5cf8 : 0xfffff80004875ed8 : nt!KiBreakpointTrap+0x318
0xfffff00afaae5d00 : 0x0000000032385048 :  Trap @ fffff00afaae5d00
0xfffff00afaae5d18 : 0xfffff80005958b37 : VerifierExt!ExAllocatePoolWithTag_internal_wrapper+0x1b7
0xfffff00afaae5d38 : 0xfffff80005a9e430 :  !da ""WDF detected potentially invalid operation by %s.%s Dump the driver log (!wdflog..."" <-- message from Wdf01000!FxVerifierDbgBreakPoint 
0xfffff00afaae5d40 : 0xffff99892786efa0 :  !da "HP8207_8307" <-- driver WDF detected the invalid operation on
0xfffff00afaae5d50 : 0xffff99892786efa0 :  !da "HP8207_8307"
0xfffff00afaae5d58 : 0xfffff80004872380 : nt!DbgBreakPoint
0xfffff00afaae5d80 : 0x00440057003b003b :  !du ";;WD)(A;"
0xfffff00afaae5de8 : 0xfffff80005a9f5c0 : Wdf01000!WPP_FxDeviceInitApi_cpp_Traceguids
0xfffff00afaae5df8 : 0xfffff80005a3aee6 : Wdf01000!FxIsEqualGuid+0x16
0xfffff00afaae5e20 : 0xfffff800048462e0 : nt!strncmp
0xfffff00afaae5e38 : 0xfffff80005a0cd92 : Wdf01000!FxObject::FxObject+0x3e
0xfffff00afaae5e48 : 0xfffff80005a6457b : Wdf01000!FxDuplicateUnicodeString+0xe7
0xfffff00afaae5e68 : 0xfffff80004872381 : nt!DbgBreakPoint+0x1
0xfffff00afaae5e80 : 0xfffff00afaae5e98 : 0xfffff80005a2f8c0 : Wdf01000!FxVerifierDbgBreakPoint+0x50
0xfffff00afaae5e90 : 0xfffff80004872380 : nt!DbgBreakPoint
0xfffff00afaae5e98 : 0xfffff80005a2f8c0 : Wdf01000!FxVerifierDbgBreakPoint+0x50 <-- breakpoint starts here
0xfffff00afaae5ea8 : 0xffff99892786efa0 :  !da "HP8207_8307"
0xfffff00afaae5eb8 : 0xffff99892786efa0 :  !da "HP8207_8307"
0xfffff00afaae5ed8 : 0xfffff80005a47033 : Wdf01000!imp_WdfFdoInitSetFilter+0x63
0xfffff00afaae5f00 : 0xfffff80005a9f5c0 : Wdf01000!WPP_FxDeviceInitApi_cpp_Traceguids
0xfffff00afaae5f38 : 0xfffff80005a5d443 : Wdf01000!FxVerifierLock::Unlock+0x3ab
0xfffff00afaae5f98 : 0xffff99892786ab70 :  dt Wdf01000!FxDriver
0xfffff00afaae5fb0 : 0xffff998927e1b760 :  dt Wdf01000!FxPkgIo
0xfffff00afaae5fd8 : 0xffff998927e10090 :  dt Wdf01000!FxIoQueue
0xfffff00afaae5ff0 : 0xffff998927e10090 :  dt Wdf01000!FxIoQueue
0xfffff00afaae5ff8 : 0xfffff80005a772cf : Wdf01000!FxPkgIo::AddIoQueue+0xdf
0xfffff00afaae6008 : 0xffff99892786ab70 :  dt Wdf01000!FxDriver
0xfffff00afaae6010 : 0xffff998927e1b760 :  dt Wdf01000!FxPkgIo
0xfffff00afaae6028 : 0xfffff00afaae5f38 : 0xfffff80005a5d443 : Wdf01000!FxVerifierLock::Unlock+0x3ab
0xfffff00afaae6030 : 0xffff998927e10090 :  dt Wdf01000!FxIoQueue
0xfffff00afaae6038 : 0xfffff80005a3cd79 : Wdf01000!FxObject::MarkNoDeleteDDI+0x39
0xfffff00afaae6048 : 0xffff998927e10090 :  dt Wdf01000!FxIoQueue
0xfffff00afaae6058 : 0xfffff80005a83e00 : Wdf01000!FxPkgPnp::FinishInitialize+0x30
0xfffff00afaae6068 : 0xfffff80005a77c4b : Wdf01000!FxPkgIo::InitializeDefaultQueue+0x83
0xfffff00afaae6070 : 0xffff998927e10090 :  dt Wdf01000!FxIoQueue
0xfffff00afaae6088 : 0xfffff80005a54834 : Wdf01000!FxDevice::_Create+0x200
0xfffff00afaae6090 : 0xffff998927e1b760 :  dt Wdf01000!FxPkgIo
0xfffff00afaae60b8 : 0xfffff80005a76bdc : Wdf01000!imp_WdfIoQueueCreate+0x19c
0xfffff00afaae60c0 : 0xffff998927e1b760 :  dt Wdf01000!FxPkgIo
0xfffff00afaae6118 : 0xfffff80005a9fb68 : Wdf01000!WPP_FxDriverKm_cpp_Traceguids
0xfffff00afaae6130 : 0xfffff80005a9fb68 : Wdf01000!WPP_FxDriverKm_cpp_Traceguids
0xfffff00afaae62b0 : 0xffff99892786ab70 :  dt Wdf01000!FxDriver
0xfffff00afaae62b8 : 0xfffff80005a571f0 : Wdf01000!FxDriver::AddDevice+0xd0
0xfffff00afaae62e0 : 0xffff99891f456f80 : 0xfffff80004b13400 : nt!MiSystemPartition
0xfffff00afaae6308 : 0xffff99892786ab70 :  dt Wdf01000!FxDriver
0xfffff00afaae6310 : 0xffff998927338cc0 :  dt Wdf01000!FxDevice
0xfffff00afaae6690 : 0xfffff00afaae6700 : 0xfffff80005a570e0 : Wdf01000!FxDriver::AddDevice
0xfffff00afaae66a8 : 0xfffff800047d9379 : nt!IoGetDriverObjectExtension+0x39
0xfffff00afaae66c0 : 0xfffff80005a570e0 : Wdf01000!FxDriver::AddDevice
0xfffff00afaae66d8 : 0xfffff80005a5710c : Wdf01000!FxDriver::AddDevice+0x2c
0xfffff00afaae6700 : 0xfffff80005a570e0 : Wdf01000!FxDriver::AddDevice
0xfffff00afaae6710 : 0xfffff80005a570e0 : Wdf01000!FxDriver::AddDevice
0xfffff00afaae6718 : 0xfffff00afaae6860 : 0xffffe0041907ce00 :  !du "HidUsb"
0xfffff00afaae6738 : 0xfffff00afaae6900 :  !du "{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"
0xfffff00afaae6748 : 0xfffff80004dde7b2 : nt!PnpCallAddDevice+0x62
0xfffff00afaae6768 : 0xffffe0041907ce00 :  !du "HidUsb"
0xfffff00afaae6788 : 0xfffff80004a1806d : nt!ExAllocatePoolWithTag+0x5d
0xfffff00afaae67a8 : 0xfffff80004745de3 : nt!IoGetAttachedDeviceReferenceWithTag+0x43
0xfffff00afaae67d8 : 0xfffff80004da3f76 : nt!PipCallDriverAddDevice+0x816
0xfffff00afaae6800 : 0xfffff00afaae6900 :  !du "{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"
0xfffff00afaae6860 : 0xffffe0041907ce00 :  !du "HidUsb"
0xfffff00afaae6878 : 0xfffff80004b0c3a0 : nt!PiDependencyRelationsLock+0x60
0xfffff00afaae68a0 : 0xfffff00afaae6900 :  !du "{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"
0xfffff00afaae6900 : 0x003500340037007b :  !du "{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"
0xfffff00afaae6908 : 0x0061003700310061 :  !du "a17a0-74d3-11d0-b6fe-00a0c90f57da}"
0xfffff00afaae6910 : 0x00340037002d0030 :  !du "0-74d3-11d0-b6fe-00a0c90f57da}"
0xfffff00afaae6918 : 0x0031002d00330064 :  !du "d3-11d0-b6fe-00a0c90f57da}"
0xfffff00afaae6920 : 0x002d003000640031 :  !du "1d0-b6fe-00a0c90f57da}"
0xfffff00afaae6928 : 0x0065006600360062 :  !du "b6fe-00a0c90f57da}"
0xfffff00afaae6930 : 0x006100300030002d :  !du "-00a0c90f57da}"
0xfffff00afaae6938 : 0x0030003900630030 :  !du "0c90f57da}"
0xfffff00afaae6940 : 0x0064003700350066 :  !du "f57da}"
0xfffff00afaae6998 : 0xfffff80004da321d : nt!PipProcessDevNodeTree+0x1b9
0xfffff00afaae69c8 : 0xffff99891cceec01 :  !da "SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS..."
0xfffff00afaae69d8 : 0xfffff80004c38240 : nt!ExNode0
0xfffff00afaae6a10 : 0xfffff80004ddf6a0 : nt!PiMarkDeviceTreeForReenumerationWorker
0xfffff00afaae6a58 : 0xfffff80004dc5c0c : nt!PiProcessReenumeration+0x88
0xfffff00afaae6a68 : 0xfffff800046e2c01 : nt!ExAcquirePushLockExclusiveEx+0xd1
0xfffff00afaae6aa8 : 0xfffff800048049a7 : nt!PnpDeviceActionWorker+0x207
0xfffff00afaae6ad8 : 0xfffff800047664bc : nt!KeRemovePriQueue+0x25c
0xfffff00afaae6b40 : 0xfffff80004c38240 : nt!ExNode0
0xfffff00afaae6b60 : 0xfffff800048047a0 : nt!PnpDeviceActionWorker
0xfffff00afaae6b68 : 0xfffff80004766005 : nt!ExpWorkerThread+0x105
0xfffff00afaae6b80 : 0xfffff80004b0a220 : nt!PnpDeviceEnumerationWorkItem
0xfffff00afaae6ba8 : 0xffff99891fd88fe0 : 0xffff99891f456f80 : 0xfffff80004b13400 : nt!MiSystemPartition
0xfffff00afaae6bf0 : 0xfffff80004765f00 : nt!ExpWorkerThread
0xfffff00afaae6c08 : 0xfffff800047d37b5 : nt!PspSystemThreadStartup+0x55
0xfffff00afaae6c58 : 0xfffff80004871b5a : nt!KiStartSystemThread+0x2a
0xfffff00afaae6c70 : 0xfffff800047d3760 : nt!PspSystemThreadStartup

0: kd> lmvm HP8207_8307
Browse full module list
start             end                 module name
fffff803`078d0000 fffff803`078db000   HP8207_8307 T (no symbols)           
    Loaded symbol image file: HP8207_8307.sys
    Image path: \SystemRoot\System32\drivers\HP8207_8307.sys
    Image name: HP8207_8307.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Feb  4 09:20:24 2010 (4B6A8348)
    CheckSum:         00009C6E
    ImageSize:        0000B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

The HP mouse driver is very old. If there are no driver updates I would recommend replacing it.
 
the update was done before i think, until i did the restore (after the driver verifier) which reversed the update,

i'm not exactly using a HP mouse anymore, can it be remove ?
 
Go in device manager (right click windows logo > device manager), expand Mice and other pointing devices and delete the HP mouse. If offered, also delete the drivers of the HP mouse.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top