alguien puede descifrar este minidump?

ronny255

Nuevo
Registrado
6 Jul 2015
Mensajes
4
Puntos
0
Hola. Tengo windows 8.1 pro y cuando conecto el usb wifi me sale una pantalla azul y al final dice "bugcode_ndis_error.
Os subo el minidump a ver si alguien descifra qué puede estar causando el error. Gracias y un saludo

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* 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+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff801`ea00c000 PsLoadedModuleList = 0xfffff801`ea2d0990
Debug session time: Sat Jul 4 01:21:25.218 2015 (UTC + 2:00)
System Uptime: 0 days 0:01:29.906
*********************************************************************
* 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+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\system32\drivers\ndis.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7C, {1d, ffffe000059eb1a0, ffffe0000771bda0, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** 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 ***
*** ***
*************************************************************************
Probably caused by : ndis.sys ( ndis+4d2fd )

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

5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_NDIS_DRIVER (7c)
This is the NDIS Driver Bugcheck for Windows Server 2003 and later.
For Windows 2000 and Windows XP, see 0xD2, BUGCODE_ID_DRIVER.
Arguments:
Arg1: 000000000000001d, NDIS BugCheck Code
Arg2: ffffe000059eb1a0
Arg3: ffffe0000771bda0
Arg4: 0000000000000000

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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: ndis

FAULTING_MODULE: fffff801ea00c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 523d51e2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7C

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80000ecf2fd to fffff801ea159ca0

STACK_TEXT:
ffffd000`38bc57c8 fffff800`00ecf2fd : 00000000`0000007c 00000000`0000001d ffffe000`059eb1a0 ffffe000`0771bda0 : nt+0x14dca0
ffffd000`38bc57d0 00000000`0000007c : 00000000`0000001d ffffe000`059eb1a0 ffffe000`0771bda0 00000000`00000000 : ndis+0x4d2fd
ffffd000`38bc57d8 00000000`0000001d : ffffe000`059eb1a0 ffffe000`0771bda0 00000000`00000000 00000000`0d01035c : 0x7c
ffffd000`38bc57e0 ffffe000`059eb1a0 : ffffe000`0771bda0 00000000`00000000 00000000`0d01035c ffffe000`06400000 : 0x1d
ffffd000`38bc57e8 ffffe000`0771bda0 : 00000000`00000000 00000000`0d01035c ffffe000`06400000 fffff800`00ec4cbf : 0xffffe000`059eb1a0
ffffd000`38bc57f0 00000000`00000000 : 00000000`0d01035c ffffe000`06400000 fffff800`00ec4cbf ffffe000`0771bda0 : 0xffffe000`0771bda0


STACK_COMMAND: kb

FOLLOWUP_IP:
ndis+4d2fd
fffff800`00ecf2fd ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ndis+4d2fd

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ndis.sys

BUCKET_ID: WRONG_SYMBOLS

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

5: kd> lmvm ndis
start end module name
fffff800`00e82000 fffff800`00f9a000 ndis T (no symbols)
Loaded symbol image file: ndis.sys
Image path: \SystemRoot\system32\drivers\ndis.sys
Image name: ndis.sys
Timestamp: Sat Sep 21 09:59:30 2013 (523D51E2)
CheckSum: 00116389
ImageSize: 00118000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 

Wendiga

Master Chapuzas
Registrado
21 Oct 2014
Mensajes
4.166
Puntos
113
Suele ser por un hardware o un controlador tocando las narices.
Has instalado algo hace poco?

En algunos casos puede ser el HD o la RAM.
 

Borja Rodríguez

Amo y señor de los Chapuzas
Miembro del equipo
Registrado
4 Jul 2012
Mensajes
81.403
Puntos
113
Edad
34

ronny255

Nuevo
Registrado
6 Jul 2015
Mensajes
4
Puntos
0
Compré un pc hace unos meses. un core i7 con placa asus rock, hd principal: disco sólido de 120 gb, hd secundario: sata 1 tb, 8 gb de ram. lo compré sin s.o- en casa he instalado el windows 8.1 pro. Cuando arranco el pc carga perfecto pero al final me sale una ventana diciendo "You may not distribute the invisible exe with the free version of this compiler" y me da a elegir yes o no. ni idea
tengo instalado una tarjeta de sonido roland ua 55 quad capture, un controlador midi, un sintetizador de guitarra roland vg 99 y nada más.
conectado en los puertos usb tengo el teclado, el ratón, la tarjeta de sonido roland, el sintetizador roland vg 99 y nada más.
 

ronny255

Nuevo
Registrado
6 Jul 2015
Mensajes
4
Puntos
0
lo que me tiene mosqueao es lo de you may not distribute.....
 

Borja Rodríguez

Amo y señor de los Chapuzas
Miembro del equipo
Registrado
4 Jul 2012
Mensajes
81.403
Puntos
113
Edad
34
Pues no será original, no?
 

ronny255

Nuevo
Registrado
6 Jul 2015
Mensajes
4
Puntos
0
Sigo sin saber que puede estar ocasionando el conflicto. gracias
 
Arriba