pantallazo azul

Tengo pantallazo azul en windows 7 .He encontrado un tutorial para averiguar los fallos usando el dump y eso es lo que me deparo.

¿alguna solución?


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


Loading Dump File [C:\Windows\Minidump\020912-16894-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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82c0c000 PsLoadedModuleList = 0x82d554d0
Debug session time: Thu Feb 9 00:30:31.779 2012 (UTC + 0:00)
System Uptime: 0 days 6:23:36.996
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 8d739750, 0, 0}

*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*** WARNING: Unable to verify timestamp for RTL8187.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8187.sys
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.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 : RTL8187.sys ( RTL8187+13581 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 8d739750
Arg3: 00000000
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 ***
*** ***
*************************************************************************

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: RTL8187

FAULTING_MODULE: 82c0c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b1f6add

BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82c8fae2 to 82d2c19f

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8d75004c 82c8fae2 00000000 00000010 73556f49 nt+0x12019f
8d750064 83329d19 877ef028 8793bab0 83329ca9 nt+0x83ae2
8d750090 8332a15b 879399f0 786d65b0 87929a48 Wdf01000+0x9d19
8d7500c8 8332a2cc 009399f0 8d750130 00000001 Wdf01000+0xa15b
8d7500e8 83336144 879399f0 8d750130 00000001 Wdf01000+0xa2cc
8d75010c 97705581 877f4918 879399f0 87929a48 Wdf01000+0x16144
8d750154 97701768 87846000 00000005 0000ffa4 RTL8187+0x13581
8d750184 97701a63 87846060 00000004 0000ffa4 RTL8187+0xf768
8d7501a8 97705480 87846000 881c874c 879399f0 RTL8187+0xfa63
8d7501cc 83345317 786c6608 786d65b0 881c874c RTL8187+0x13480
8d7501f8 83329c36 8793bab0 87929a48 877ef028 Wdf01000+0x25317
8d750214 83329cde 019399f0 86bda238 8d75024c Wdf01000+0x9c36
8d750224 82c8fa63 00000000 8793bab0 879399f0 Wdf01000+0x9cde
8d75024c 82c84913 00000000 8793bab0 86bda238 nt+0x83a63
8d750290 9062a1c3 00000000 8d7502e8 9062b235 nt+0x78913
8d75029c 9062b235 86cb0028 8793bab0 85990a48 USBPORT+0x51c3
8d7502e8 9062b52c 86cb0028 c000000e 8793bab0 USBPORT+0x6235
8d750310 90628a34 86cb0028 8793bab0 85990a48 USBPORT+0x652c
8d750338 82c4358e 86cb0028 86cb02cc 8793bab0 USBPORT+0x3a34
8d750350 9763ec8e 8793bab0 876690e8 00000000 nt+0x3758e
8d750364 9763eee5 86d110e0 87669030 8793bab0 usbhub+0x1c8e
8d750388 9763eb91 87669030 8793bb8c 87669030 usbhub+0x1ee5
8d75039c 82c4358e 87669030 8793bab0 8d7503f0 usbhub+0x1b91
8d7503b4 83336164 8d750400 786d65b0 786c6608 nt+0x3758e
8d7503cc 97705581 00000005 879399f0 87929a48 Wdf01000+0x16164
8d750414 97701768 87846000 00000005 0000ffa4 RTL8187+0x13581
8d750444 97701a63 87846060 00000004 0000ffa4 RTL8187+0xf768
8d750468 97705480 87846000 881c874c 879399f0 RTL8187+0xfa63
8d75048c 83345317 786c6608 786d65b0 881c874c RTL8187+0x13480
8d7504b8 83329c36 8793bab0 87929a48 877ef028 Wdf01000+0x25317
8d7504d4 83329cde 019399f0 857524d0 8d75050c Wdf01000+0x9c36
8d7504e4 82c8fa63 00000000 8793bab0 879399f0 Wdf01000+0x9cde
8d75050c 82c84913 00000000 8793bab0 857524d0 nt+0x83a63
8d750550 9062a1c3 00000000 8d7505a8 9062b235 nt+0x78913
8d75055c 9062b235 86cb0028 8793bab0 85990a48 USBPORT+0x51c3
8d7505a8 9062b52c 86cb0028 c000000e 8793bab0 USBPORT+0x6235
8d7505d0 90628a34 86cb0028 8793bab0 85990a48 USBPORT+0x652c
8d7505f8 82c4358e 86cb0028 86cb02cc 8793bab0 USBPORT+0x3a34
8d750610 9763ec8e 8793bab0 876690e8 00000000 nt+0x3758e
8d750624 9763eee5 86d110e0 87669030 8793bab0 usbhub+0x1c8e
8d750648 9763eb91 87669030 8793bb8c 87669030 usbhub+0x1ee5
8d75065c 82c4358e 87669030 8793bab0 8d7506b0 usbhub+0x1b91
8d750674 83336164 8d7506c0 786d65b0 786c6608 nt+0x3758e
8d75068c 97705581 00000005 879399f0 87929a48 Wdf01000+0x16164
8d7506d4 97701768 87846000 00000005 0000ffa4 RTL8187+0x13581
8d750704 97701a63 87846060 00000004 0000ffa4 RTL8187+0xf768
8d750728 97705480 87846000 881c874c 879399f0 RTL8187+0xfa63
8d75074c 83345317 786c6608 786d65b0 881c874c RTL8187+0x13480
8d750778 83329c36 8793bab0 87929a48 877ef028 Wdf01000+0x25317
8d750794 83329cde 019399f0 88c04c08 8d7507cc Wdf01000+0x9c36
8d7507a4 82c8fa63 00000000 8793bab0 879399f0 Wdf01000+0x9cde
8d7507cc 82c84913 00000000 8793bab0 88c04c08 nt+0x83a63
8d750810 9062a1c3 00000000 8d750868 9062b235 nt+0x78913
8d75081c 9062b235 86cb0028 8793bab0 85990a48 USBPORT+0x51c3
8d750868 9062b52c 86cb0028 c000000e 8793bab0 USBPORT+0x6235
8d750890 90628a34 86cb0028 8793bab0 85990a48 USBPORT+0x652c
8d7508b8 82c4358e 86cb0028 86cb02cc 8793bab0 USBPORT+0x3a34
8d7508d0 9763ec8e 8793bab0 876690e8 00000000 nt+0x3758e
8d7508e4 9763eee5 86d110e0 87669030 8793bab0 usbhub+0x1c8e
8d750908 9763eb91 87669030 8793bb8c 87669030 usbhub+0x1ee5
8d75091c 82c4358e 87669030 8793bab0 8d750970 usbhub+0x1b91
8d750934 83336164 8d750980 786d65b0 786c6608 nt+0x3758e
8d75094c 97705581 00000005 879399f0 87929a48 Wdf01000+0x16164
8d750994 97701768 87846000 00000005 0000ffa4 RTL8187+0x13581
8d7509c4 97701a63 87846060 00000004 0000ffa4 RTL8187+0xf768
8d7509e8 97705480 87846000 881c874c 879399f0 RTL8187+0xfa63
8d750a0c 83345317 786c6608 786d65b0 881c874c RTL8187+0x13480
8d750a38 83329c36 8793bab0 87929a48 877ef028 Wdf01000+0x25317
8d750a54 83329cde 019399f0 8809f320 8d750a8c Wdf01000+0x9c36
8d750a64 82c8fa63 00000000 8793bab0 879399f0 Wdf01000+0x9cde
8d750a8c 82c84913 00000000 8793bab0 8809f320 nt+0x83a63
8d750ad0 9062a1c3 00000000 8d750b28 9062b235 nt+0x78913
8d750adc 9062b235 86cb0028 8793bab0 85990a48 USBPORT+0x51c3
8d750b28 9062b52c 86cb0028 c000000e 8793bab0 USBPORT+0x6235
8d750b50 90628a34 86cb0028 8793bab0 85990a48 USBPORT+0x652c


STACK_COMMAND: kb

FOLLOWUP_IP:
RTL8187+13581
97705581 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: RTL8187+13581

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: RTL8187.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
 
por lo visto lo tengo actualizado, lo que hice fue desinstalarlo y volverlo a instalar.

¿alguna opción más?
 
a las buenas de nuevo:

perdon, creo que me he equivocado, tienes una tarjeta inalambrica usb???
si no la tienes, desinstala el driver del sonido, pasa el driver sweeper en modo a prueba de errore, despues el ccleanetr y vuevle a instalar...

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


Loading Dump File [C:\Windows\Minidump\021012-19546-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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82c0c000 PsLoadedModuleList = 0x82d554d0
Debug session time: Fri Feb 10 23:31:47.941 2012 (UTC + 0:00)
System Uptime: 1 days 4:39:08.548
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....................
*** WARNING: Unable to verify timestamp for halmacpi.dll
*** ERROR: Module load completed but symbols could not be loaded for halmacpi.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 8d739750, 0, 0}

*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*** WARNING: Unable to verify timestamp for RTL8187.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8187.sys
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.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 : RTL8187.sys ( RTL8187+13581 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 8d739750
Arg3: 00000000
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 ***
*** ***
*************************************************************************

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: RTL8187

FAULTING_MODULE: 82c0c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b1f6add

BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8302192d to 83023b55

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8d754004 8302192d 82d2c5f7 83350ca9 86eff990 hal+0x5b55
8d75405c 82c8fae2 00000000 00000010 73556f49 hal+0x392d
8d754074 83350d19 878c7028 88ea1a00 83350ca9 nt+0x83ae2
8d7540a0 8335115b 86eff990 79cf6a40 863095b8 Wdf01000+0x9d19
8d7540d8 833512cc 00eff990 8d754140 00000001 Wdf01000+0xa15b
8d7540f8 8335d144 86eff990 8d754140 00000001 Wdf01000+0xa2cc
8d75411c a59a6581 859db3c0 86eff990 863095b8 Wdf01000+0x16144
8d754164 a59a2768 8a600000 00000005 0000ffa4 RTL8187+0x13581
8d754194 a59a2a63 8a600060 00000004 0000ffa4 RTL8187+0xf768
8d7541b8 a59a6480 8a600000 859c2c2c 86eff990 RTL8187+0xfa63
8d7541dc 8336c317 79100668 79cf6a40 859c2c2c RTL8187+0x13480
8d754208 83350c36 88ea1a00 863095b8 878c7028 Wdf01000+0x25317
8d754224 83350cde 01eff990 878021d0 8d75425c Wdf01000+0x9c36
8d754234 82c8fa63 00000000 88ea1a00 86eff990 Wdf01000+0x9cde
8d75425c 82c84913 00000000 88ea1a00 878021d0 nt+0x83a63
8d7542a0 914a81c3 00000000 8d7542f8 914a9235 nt+0x78913
8d7542ac 914a9235 86af2028 88ea1a00 85c4c9d8 USBPORT+0x51c3
8d7542f8 914a952c 86af2028 c000000e 88ea1a00 USBPORT+0x6235
8d754320 914a6a34 86af2028 88ea1a00 85c4c9d8 USBPORT+0x652c
8d754348 82c4358e 86af2028 86af22cc 88ea1a00 USBPORT+0x3a34
8d754360 92414c8e 88ea1a00 878970e8 00000000 nt+0x3758e
8d754374 92414ee5 86b610e0 87897030 88ea1a00 usbhub+0x1c8e
8d754398 92414b91 87897030 88ea1adc 87897030 usbhub+0x1ee5
8d7543ac 82c4358e 87897030 88ea1a00 8d754400 usbhub+0x1b91
8d7543c4 8335d164 8d754410 79cf6a40 79100668 nt+0x3758e
8d7543dc a59a6581 00000005 86eff990 863095b8 Wdf01000+0x16164
8d754424 a59a2768 8a600000 00000005 0000ffa4 RTL8187+0x13581
8d754454 a59a2a63 8a600060 00000004 0000ffa4 RTL8187+0xf768
8d754478 a59a6480 8a600000 859c2c2c 86eff990 RTL8187+0xfa63
8d75449c 8336c317 79100668 79cf6a40 859c2c2c RTL8187+0x13480
8d7544c8 83350c36 88ea1a00 863095b8 878c7028 Wdf01000+0x25317
8d7544e4 83350cde 01eff990 85a47708 8d75451c Wdf01000+0x9c36
8d7544f4 82c8fa63 00000000 88ea1a00 86eff990 Wdf01000+0x9cde
8d75451c 82c84913 00000000 88ea1a00 85a47708 nt+0x83a63
8d754560 914a81c3 00000000 8d7545b8 914a9235 nt+0x78913
8d75456c 914a9235 86af2028 88ea1a00 85c4c9d8 USBPORT+0x51c3
8d7545b8 914a952c 86af2028 c000000e 88ea1a00 USBPORT+0x6235
8d7545e0 914a6a34 86af2028 88ea1a00 85c4c9d8 USBPORT+0x652c
8d754608 82c4358e 86af2028 86af22cc 88ea1a00 USBPORT+0x3a34
8d754620 92414c8e 88ea1a00 878970e8 00000000 nt+0x3758e
8d754634 92414ee5 86b610e0 87897030 88ea1a00 usbhub+0x1c8e
8d754658 92414b91 87897030 88ea1adc 87897030 usbhub+0x1ee5
8d75466c 82c4358e 87897030 88ea1a00 8d7546c0 usbhub+0x1b91
8d754684 8335d164 8d7546d0 79cf6a40 79100668 nt+0x3758e
8d75469c a59a6581 00000005 86eff990 863095b8 Wdf01000+0x16164
8d7546e4 a59a2768 8a600000 00000005 0000ffa4 RTL8187+0x13581
8d754714 a59a2a63 8a600060 00000004 0000ffa4 RTL8187+0xf768
8d754738 a59a6480 8a600000 859c2c2c 86eff990 RTL8187+0xfa63
8d75475c 8336c317 79100668 79cf6a40 859c2c2c RTL8187+0x13480
8d754788 83350c36 88ea1a00 863095b8 878c7028 Wdf01000+0x25317
8d7547a4 83350cde 01eff990 8788de20 8d7547dc Wdf01000+0x9c36
8d7547b4 82c8fa63 00000000 88ea1a00 86eff990 Wdf01000+0x9cde
8d7547dc 82c84913 00000000 88ea1a00 8788de20 nt+0x83a63
8d754820 914a81c3 00000000 8d754878 914a9235 nt+0x78913
8d75482c 914a9235 86af2028 88ea1a00 85c4c9d8 USBPORT+0x51c3
8d754878 914a952c 86af2028 c000000e 88ea1a00 USBPORT+0x6235
8d7548a0 914a6a34 86af2028 88ea1a00 85c4c9d8 USBPORT+0x652c
8d7548c8 82c4358e 86af2028 86af22cc 88ea1a00 USBPORT+0x3a34
8d7548e0 92414c8e 88ea1a00 878970e8 00000000 nt+0x3758e
8d7548f4 92414ee5 86b610e0 87897030 88ea1a00 usbhub+0x1c8e
8d754918 92414b91 87897030 88ea1adc 87897030 usbhub+0x1ee5
8d75492c 82c4358e 87897030 88ea1a00 8d754980 usbhub+0x1b91
8d754944 8335d164 8d754990 79cf6a40 79100668 nt+0x3758e
8d75495c a59a6581 00000005 86eff990 863095b8 Wdf01000+0x16164
8d7549a4 a59a2768 8a600000 00000005 0000ffa4 RTL8187+0x13581
8d7549d4 a59a2a63 8a600060 00000004 0000ffa4 RTL8187+0xf768
8d7549f8 a59a6480 8a600000 859c2c2c 86eff990 RTL8187+0xfa63
8d754a1c 8336c317 79100668 79cf6a40 859c2c2c RTL8187+0x13480
8d754a48 83350c36 88ea1a00 863095b8 878c7028 Wdf01000+0x25317
8d754a64 83350cde 01eff990 859e89d8 8d754a9c Wdf01000+0x9c36
8d754a74 82c8fa63 00000000 88ea1a00 86eff990 Wdf01000+0x9cde
8d754a9c 82c84913 00000000 88ea1a00 859e89d8 nt+0x83a63
8d754ae0 914a81c3 00000000 8d754b38 914a9235 nt+0x78913
8d754aec 914a9235 86af2028 88ea1a00 85c4c9d8 USBPORT+0x51c3
8d754b38 914a952c 86af2028 c000000e 88ea1a00 USBPORT+0x6235


STACK_COMMAND: kb

FOLLOWUP_IP:
RTL8187+13581
a59a6581 ?? ???

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: RTL8187+13581

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: RTL8187.sys

BUCKET_ID: WRONG_SYMBOLS

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

sigo teniendo pantallazos azules ¿alguna solución? por favor
 
bueno, he desinstalado el controlador y he buscado en la web de fabricante y me he descargado uno actualizado.

Ahora a esperar que no me de problemas.

Muchas gracias por la respuesta, les mantendré informados.
 
Arriba