- Mar 6, 2017
- 1
- 0
- 510
Hello
I stupidly downloaded and used a driver cleaner and now have blue screen of death.
I get this message: The driver is mismanaging system PTES - could this be graphics driver related?
the blue screen disappears before I can note down the 0x0000 numbers.
I have logged in to safe mode and tried downloading new graphics drivers for my nvidia thinking this may cure the problem as it may be graphics related and then tried reverting drivers and rolling them back but that has not worked either.
I tried using windows recovery but that has not worked either. every time I get past the login screen BSOD happens.
Please see attatched crash dump data:
Thank you
Additional information about the problem:
BCCode: da
BCP1: 0000000000000504
BCP2: FFFFF6FC40078D98
BCP3: 0000000000000030
BCP4: 000000000000F1B3
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
crash dump file: C:\Windows\Minidump\030717-33602-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0xDA (0x504, 0xFFFFF6FC40078D98, 0x30, 0xF1B3)
Error: SYSTEM_PTE_MISUSE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xDA (0x504, 0xFFFFF6FC40078D98, 0x30, 0xF1B3)
Error: SYSTEM_PTE_MISUSE
Bug check description: This indicates that a page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I stupidly downloaded and used a driver cleaner and now have blue screen of death.
I get this message: The driver is mismanaging system PTES - could this be graphics driver related?
the blue screen disappears before I can note down the 0x0000 numbers.
I have logged in to safe mode and tried downloading new graphics drivers for my nvidia thinking this may cure the problem as it may be graphics related and then tried reverting drivers and rolling them back but that has not worked either.
I tried using windows recovery but that has not worked either. every time I get past the login screen BSOD happens.
Please see attatched crash dump data:
Thank you
Additional information about the problem:
BCCode: da
BCP1: 0000000000000504
BCP2: FFFFF6FC40078D98
BCP3: 0000000000000030
BCP4: 000000000000F1B3
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
crash dump file: C:\Windows\Minidump\030717-33602-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0xDA (0x504, 0xFFFFF6FC40078D98, 0x30, 0xF1B3)
Error: SYSTEM_PTE_MISUSE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xDA (0x504, 0xFFFFF6FC40078D98, 0x30, 0xF1B3)
Error: SYSTEM_PTE_MISUSE
Bug check description: This indicates that a page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Facebook
Twitter
Instagram