Problema con reinicios con Windows 7. Pantalla azul. Dumping physical memory to

Hola, llevo unas semanas que de manera aleatoria me sale una pantalla azul con un mensaje, en el que termina algo asi como "Dumping physical memory to disk". Se reinicia el Pc dandome la opcion de inicial en modo a prueba de errores. una vez iniciado me sale una ventana y en los detalles me remite a una direccion de una carpeta dentro de C:/Windows/minidump/ a un fichero con extension .dmp.

he indagado y he podido acceder a ese fichero mediante el kit de herramientas de windows (windbgx64).

En este fichero me hace referencia a falta de driver o problema con driver.

Y hace referencia a un modulo .sys, que es fwpkclnt.sys, pero a partir de aqui, no sé como solucionar esto.

No sé si se ha corrompido esta libreria y hay que sustituirla y en este caso como hacerlo o que hacer al respecto.
He hecho el SFC /scanow, y está correcto, he hecho un test de la memoria fisica y tambien correcto, y por supuesto he pasado mi antivirus Bitdefender total 2016, y todo correcto.

En cualquier caso, a ver si me pueden ayudar para solucionar éste problema, si lo creen conveniente les podría subir el archivo .dmp. Espero su ayuda.

Muchas gracias. Un saludo.
Dumping physical memory to disk

Archivo minidump.

[color=#000080]Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\042216-12043-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19160.amd64fre.win7sp1_gdr.160211-0600
Machine Name:
Kernel base = 0xfffff800`0345d000 PsLoadedModuleList = 0xfffff800`036a4730
Debug session time: Fri Apr 22 18:13:31.353 2016 (UTC + 2:00)
System Uptime: 0 days 0:03:48.180
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......

*
Bugcheck Analysis *
*



Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa800afb4c50, fffffa800afb4c70, 4020019}

WARNING: Unable to verify timestamp for mwac.sys
ERROR: Module load completed but symbols could not be loaded for mwac.sys


Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a )

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

1: kd> !analyze -v

*
Bugcheck Analysis *
*



BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800afb4c50, The pool entry we were looking for within the page.
Arg3: fffffa800afb4c70, The next pool entry.
Arg4: 0000000004020019, (reserved)

Debugging Details:
------------------

DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.19160.amd64fre.win7sp1_gdr.160211-0600
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: B85M-HD3
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: F5
BIOS_DATE: 08/03/2013
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: B85M-HD3
BASEBOARD_VERSION: x.x
DUMP_TYPE: 2
BUGCHECK_P1: 20
BUGCHECK_P2: fffffa800afb4c50
BUGCHECK_P3: fffffa800afb4c70
BUGCHECK_P4: 4020019
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370e100
Unable to get MmSystemRangeStart
fffffa800afb4c50
CPU_COUNT: 4
CPU_MHZ: bb1
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 12'00000000 (cache) 12'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: mbamservice.ex
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: ENRIQUE-PC
ANALYSIS_SESSION_TIME: 04-24-2016 13:14:36.0072
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff80003607cae to fffff800034d1080
STACK_TEXT:
fffff880`09887168 fffff800`03607cae : 00000000`00000019 00000000`00000020 fffffa80`0afb4c50 fffffa80`0afb4c70 : nt!KeBugCheckEx
fffff880`09887170 fffff880`01d27d2d : 00000000`00000008 00000000`00000008 00000000`676e7049 fffffa80`0b9be1f6 : nt!ExDeferredFreePool+0x12da
fffff880`09887220 fffff880`00da0066 : 00000000`00000000 fffff880`00d9c0c3 00000000`00000000 fffffa80`0711f9b0 : tcpip!IppInspectBuildHeaders+0x65d
fffff880`09887500 fffff880`0783c12d : 00000000`00000000 00000000`00000014 00000000`00000000 fffffa80`07023a00 : fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+0x20a
fffff880`098875a0 00000000`00000000 : 00000000`00000014 00000000`00000000 fffffa80`07023a00 fffffa80`07023a14 : mwac+0x612d

STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 2647a8884c8b09f064ff759df6d75b2848c3da21

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8fcf995ee0f14a68f835dd0cf90d0f79e4bd9785

THREAD_SHA1_HASH_MOD: d22f46aff69f74919852fff5c04c9e17fb5861c0

FOLLOWUP_IP:
fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a
fffff880`00da0066 85c0 test eax,eax

FAULT_INSTR_CODE: 2c74c085
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fwpkclnt
IMAGE_NAME: fwpkclnt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 533f5b09
IMAGE_VERSION: 6.1.7601.18438
FAILURE_BUCKET_ID: X64_0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a

BUCKET_ID: X64_0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a

PRIMARY_PROBLEM_CLASS: X64_0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a

TARGET_TIME: 2016-04-22T16:13:31.000Z

OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-02-11 18:40:22[color=#0000BF]
BUILDDATESTAMP_STR: 160211-0600
BUILDLAB_STR: win7sp1_gdr
BUILDOSVER_STR: 6.1.7601.19160.amd64fre.win7sp1_gdr.160211-0600
ANALYSIS_SESSION_ELAPSED_TIME: 750
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x19_20_fwpkclnt!fwpsconstructipheaderfortransportpacket0+20a

FAILURE_ID_HASH: {863e217f-0693-d7a3-6d21-a4c5a3f57698}

Followup: MachineOwner
---------[/color][/color]

Has hecho un chequeo de la memoria RAM?

Enviado desde mi SM-N910F mediante Tapatalk

Hola amigo @davdi, si he hecho un chequeo de la Ram, también hice un sfc /scannow, y todo estaba correcto. De momento estoy desinstalando alguna cosa del PC, para ir probando, por que al ser un problema aleatorio.....no sé donde está el problema.
Gracias de nuevo, un saludo.

Has instalado algo de hardware cuando ha empezado a pasarte? (Impresora, tarjeta WiFi, hdd, cualquier dispositivo interno o externo)
Has actualizado drivers últimamente?

Enviado desde mi SM-N910F mediante Tapatalk