He pasado el WinDbg y me sale lo siguiente:
Bugcheck Analysis *
* *
************************************************** *****************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81ca9897, The address that the exception occurred at
Arg3: a2971910, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************

MODULE_NAME: nt

FAULTING_MODULE: 81c36000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

FAULTING_IP:
nt!ExAcquireRundownProtectionEx+39
81ca9897 8b487c mov ecx,dword ptr [eax+7Ch]

TRAP_FRAME: a2971910 -- (.trap 0xffffffffa2971910)
ErrCode = 00000000
eax=0190f104 ebx=8490e0d8 ecx=83dfdb58 edx=00000000 esi=83fb9bc0 edi=83fb9cc0
eip=81ca9897 esp=a2971984 ebp=a2971984 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!ExAcquireRundownProtectionEx+0x39:
81ca9897 8b487c mov ecx,dword ptr [eax+7Ch] ds:0023:0190f180=????????
Resetting default scope

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 81c67f9e to 81cf16d9

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a29714d0 81c67f9e 0000008e c0000005 81ca9897 nt!KeBugCheckEx+0x1e
a29718a0 81c8e56a a29718bc 00000000 a2971910 nt!RtlFindNextForwardRunClear+0x2a3
a2971920 8649304f 24d4e13c 00000000 848cc3e0 nt!Kei386EoiHelper+0x1d2
a2971984 81ca9af4 00000000 a297199c 8604dc70 Ntfs+0x9104f
a2971990 8604dc70 0190f104 a29719f8 86046067 nt!IoGetTransactionParameterBlock+0x11
a297199c 86046067 848ba2c0 0190f104 00000000 fltmgr!FltObjectDereference+0x392
a29719f8 86049090 00fb9bc0 00000000 83fb9bc0 fltmgr!FltRequestOperationStatusCallback+0x5a9
a2971a0c 860495c6 83fb9bc0 8548acb0 a2971a4c fltmgr!FltGetIrpName+0x80c
a2971a1c 86049c37 848ae960 8548acb0 83fb9bc0 fltmgr!FltGetIrpName+0xd42
a2971a4c 8605c643 a2971a6c 00000000 00000000 fltmgr!FltGetIrpName+0x13b3
a2971a98 81c7c1ad 848ae960 848ba2c0 83dfdbb4 fltmgr!FltDeletePushLock+0x1db7
a2971ab0 81e2f9dc 824d0028 844dd0ac 84806170 nt!IofCallDriver+0x64
a2971b80 81e295cc 84806188 00000000 844dd008 nt!SeExamineSacl+0x127e
a2971c10 81e29b5c 00000000 a2971c68 00000040 nt!CcUnpinData+0x89f
a2971c70 81e30927 01328b78 00000000 00000001 nt!ObOpenObjectByName+0x13c
a2971ce4 81e49fac 01328bdc 00100081 01328b78 nt!SeSetAccessStateGenericMapping+0x674
a2971d30 81c8d9aa 01328bdc 00100081 01328b78 nt!NtCreateFile+0x34
a2971d64 778c9a94 badb0d00 01328b40 00000000 nt!ZwQueryLicenseValue+0xbd2
a2971d68 badb0d00 01328b40 00000000 00000000 0x778c9a94
a2971d6c 01328b40 00000000 00000000 00000000 0xbadb0d00
a2971d70 00000000 00000000 00000000 00000000 0x1328b40


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExAcquireRundownProtectionEx+39
81ca9897 8b487c mov ecx,dword ptr [eax+7Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExAcquireRundownProtectionEx+39

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID: WRONG_SYMBOLS

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