Solved Apparently Random BSODs

[Webbstre]

Hello!

I've been experiencing BSODs lately and I have no idea why. At first they showed an error message when they would appear, but lately it's just a generic message and a crash dump count, and they are getting more frequent.

I've done a full MemTest86 and it didn't return any errors, so I don't think it is my memory. I've updated my System info on the forum, and I'll attach the BSOD analysis to this post. For an additional, quick look, here is what WhoCrashed tells me lately:

On Wed 2015/04/08 1:06:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040815-29780-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80003DB3B15)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid 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. 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 2015/04/08 1:06:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xDA29)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80003DB3B15)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\win32k.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that the system attempted to access invalid 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. 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 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 Tue 2015/04/07 14:58:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040815-30841-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x18000000400, 0x2, 0x1, 0xFFFFF80003CF65A2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 2015/04/04 6:19:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040415-30217-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80003E09B15)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid 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. 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 2015/04/01 23:51:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040215-29593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80003DB2B15)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid 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. 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.

 

[Webbstre]

Bumping this, because I haven't gotten any responses yet.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {18000000400, 2, 1, fffff80003cf65a2}

*** WARNING: Unable to verify timestamp for[B][COLOR="Red"] networx.sys[/COLOR][/B]
*** ERROR: Module load completed but symbols could not be loaded for networx.sys
Probably caused by : tdx.sys ( tdx!TdxSendDatagramTransportAddress+2f5 )

Followup: MachineOwner
---------

0: kd> lmvm networx
start             end                 module name
fffff880`03fe9000 fffff880`03ffb000   networx  T (no symbols)           
    Loaded symbol image file: networx.sys
    Image path: \SystemRoot\system32\drivers\networx.sys
    Image name: networx.sys
    Timestamp:        Wed [B][COLOR="red"]Nov 20[/COLOR][/B] 03:36:31 [B][COLOR="red"]2013[/COLOR][/B] (528B9A97)
    CheckSum:         0000F60A
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I think the Networx application is interfering with the system. Update it if possible, or remove it, and see if the system stays stable.

https://www.softperfect.com/products/networx/

Can you also list all devices which are connected to the USB ports please?

 

[Webbstre]

I will start by trying to update Networx then. Is there an easy way to list all my USB devices?

 

[Golden]

Not that I know of, just type them out here - you can disregard the keyboard and mouse.

 

[Webbstre]

It's been a few weeks and I've had no Blue Screens since uninstalling Networx. I recommend BitMeter OS instead for anyone who comes across this with the same problem. Thanks for all the help!

 

[Golden]