With apologies to JT.
I've been trying to chase down this BSOD and I can't figure out what's causing it. It's been very regular, happening several times a week. Here's my system specs:
Windows 7 Enterprise x64
i7-3770k
32GB RAM
Asus 1080 6GB
I let it run overnight with memtest86 but it didn't catch any errors. I ran driver verifier and it kept crashing in "PxHlpa64" so I ended up straight up deleting it, but that didn't seem to make a difference. Here's my 7 latest dumps, the 2 most recent being driver verifier crashes and the other 5 just being random. Please let me know if you need any more information, or what I should try next. Thanks!
On Thu 7/12/2018 6:14:42 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: diginet.sys (diginet+0x1525)
Bugcheck code: 0xC1 (0xFFFFF980227E8F90, 0xFFFFF980227E8FFC, 0xF34074, 0x24)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\drivers\diginet.sys
product: Pro Tools®
company: Avid Technology, Inc.
description: 64-bit Ethernet Packet Driver
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: diginet.sys (64-bit Ethernet Packet Driver, Avid Technology, Inc.).
Google query: Avid Technology, Inc. SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
On Thu 7/12/2018 6:11:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071218-53492-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0xC1 (0xFFFFF9800E2ACF90, 0xFFFFF9800E2ACFFC, 0xE34074, 0x24)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 7/11/2018 1:55:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071018-43477-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0x4E (0x99, 0x7FD523, 0x3, 0x526F2B)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 7/9/2018 4:25:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070818-43727-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0x4E (0x99, 0x26E9A3, 0x3, 0x5CB606)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 7/5/2018 1:10:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070418-44304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0x4E (0x99, 0x283DDA, 0x3, 0x455A)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 7/4/2018 3:45:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070318-39717-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x10168)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF8800F410168)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 7/4/2018 12:43:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070318-50762-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0x1A (0x8885, 0xFFFFFA800DB97140, 0xFFFFFA800DB96FC0, 0x302)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I've been trying to chase down this BSOD and I can't figure out what's causing it. It's been very regular, happening several times a week. Here's my system specs:
Windows 7 Enterprise x64
i7-3770k
32GB RAM
Asus 1080 6GB
I let it run overnight with memtest86 but it didn't catch any errors. I ran driver verifier and it kept crashing in "PxHlpa64" so I ended up straight up deleting it, but that didn't seem to make a difference. Here's my 7 latest dumps, the 2 most recent being driver verifier crashes and the other 5 just being random. Please let me know if you need any more information, or what I should try next. Thanks!
On Thu 7/12/2018 6:14:42 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: diginet.sys (diginet+0x1525)
Bugcheck code: 0xC1 (0xFFFFF980227E8F90, 0xFFFFF980227E8FFC, 0xF34074, 0x24)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\drivers\diginet.sys
product: Pro Tools®
company: Avid Technology, Inc.
description: 64-bit Ethernet Packet Driver
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: diginet.sys (64-bit Ethernet Packet Driver, Avid Technology, Inc.).
Google query: Avid Technology, Inc. SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
On Thu 7/12/2018 6:11:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071218-53492-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0xC1 (0xFFFFF9800E2ACF90, 0xFFFFF9800E2ACFFC, 0xE34074, 0x24)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 7/11/2018 1:55:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071018-43477-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0x4E (0x99, 0x7FD523, 0x3, 0x526F2B)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 7/9/2018 4:25:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070818-43727-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0x4E (0x99, 0x26E9A3, 0x3, 0x5CB606)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 7/5/2018 1:10:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070418-44304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0x4E (0x99, 0x283DDA, 0x3, 0x455A)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 7/4/2018 3:45:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070318-39717-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x10168)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF8800F410168)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 7/4/2018 12:43:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070318-50762-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA62A0)
Bugcheck code: 0x1A (0x8885, 0xFFFFFA800DB97140, 0xFFFFFA800DB96FC0, 0x302)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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