[SOLVED] PNP_DETECTED_FATAL_ERROR

bascotie · Tuesday at 8:56 PM

Hi guys! Another learning experience has come up..

Sysnative collection zip attached.

Can boot into safe Mode
Windows 10
Tried disabling all startup non-microsoft services and programs
Tried updating to 20H2 from Safe mode but it fails
This computer has had a hinge repair a few months back

Any ideas of what to try next? Thanks!

x BlueRobot · Wednesday at 4:41 AM

It appears that your dptf_acpi.sys driver is causing issues, it appears to be provided by the OEM according to the DRT.

Rich (BB code):

1: kd> !drvobj ffff930a5b6b3e40
fffff805556252b0: Unable to get value of ObpRootDirectoryObject
fffff805556252b0: Unable to get value of ObpRootDirectoryObject
Driver object (ffff930a5b6b3e40) is for:
Unable to load image \SystemRoot\System32\drivers\dptf_acpi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dptf_acpi.sys
 \Driver\dptf_acpi

Driver Extension List: (id , addr)
(fffff80558ff4d50 ffff930a5644bea0)  
Device Object list:
ffff930a5b726de0

Rich (BB code):

1: kd> lmvm dptf_acpi
Browse full module list
start             end                 module name
fffff805`73120000 fffff805`7312e000   dptf_acpi T (no symbols)           
    Loaded symbol image file: dptf_acpi.sys
    Image path: \SystemRoot\System32\drivers\dptf_acpi.sys
    Image name: dptf_acpi.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jan  5 20:41:46 2015 (54AAF70A)
    CheckSum:         0001625D
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

The second dump file was the exact same bugcheck but different driver, it is likely to be part of the same package as the previously mentioned one.

Rich (BB code):

0: kd> !drvobj ffffdf83ca88d7b0
fffff80149c252b0: Unable to get value of ObpRootDirectoryObject
fffff80149c252b0: Unable to get value of ObpRootDirectoryObject
Driver object (ffffdf83ca88d7b0) is for:
Unable to load image \SystemRoot\System32\drivers\dptf_cpu.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dptf_cpu.sys
 \Driver\dptf_cpu

Driver Extension List: (id , addr)
(fffff8014c1f4d50 ffffdf83c997e4f0)  
Device Object list:
ffffdf83ca8b0980

x BlueRobot · Wednesday at 4:49 AM

Quick update, did you try and run a Windows Update for Intel by any chance? It appears you have the same or a very similar issue to this thread - Intel update via Windows update

bascotie · Wednesday at 7:28 PM

x BlueRobot said:
Quick update, did you try and run a Windows Update for Intel by any chance? It appears you have the same or a very similar issue to this thread - Intel update via Windows update

I'll have to check the update log, though I did try rolling back quality updates which didn't help.

So I ran tronscript for the heck of it, but no go.

I ended up doing a full HP F2 diagnostic run, and the long dst FAILED (S.M.A.R.T and short dst passed which is unusual for me but ok!)

I'll try replacing the drive thanks!

x BlueRobot · Thursday at 4:55 AM

Thanks for letting us know, hopefully the issue was with the drive in this instance. I find it rather peculiar to have two of the same bugcheck from different users within a day of each other.

bascotie · Thursday at 1:27 PM

So far so good with the new drive. Swapped it out yesterday for an ssd and finished all updates , data transfer , etc without issue.

Thanks!

x BlueRobot · 2021-04-11T05:12:06-0400

Glad your issue has been resolved, seems like quite few Stop 0xCA's are being caused by that driver.

Search

Search

[SOLVED] PNP_DETECTED_FATAL_ERROR

bascotie

BSOD Academy Student

Attachments

x BlueRobot

Moderator, BSOD Academy Instructor

x BlueRobot

Moderator, BSOD Academy Instructor

bascotie

BSOD Academy Student

x BlueRobot

Moderator, BSOD Academy Instructor

bascotie

BSOD Academy Student

x BlueRobot

Moderator, BSOD Academy Instructor