Vishwanath Pattanshetti
Member
- Joined
- Nov 23, 2015
- Messages
- 42
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80076caa10, fffff80000b9a3d8, fffffa800ae9dbd0}
Probably caused by : pci.sys
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80076dea10, fffff80000b9a3d8, fffffa80073a3010}
Probably caused by : pci.sys
Followup: MachineOwner
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_athrx_image_pci.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80076baa10, fffff800044803d8, fffffa800743b680}
Probably caused by : pci.sys
Followup: MachineOwner
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_athrx_image_pci.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80076e2a10, fffff80000b9a3d8, fffffa8009cdb620}
Probably caused by : pci.sys
Followup: MachineOwner
Ah ok leave it alone then. See how you go on with the hotfix..but that is how i got the machine..