Pantalla Azul T_T

[dhetox]

Desde el dia de ayer me esta aparecio pantalla azul y reinicio de PC... ayer fue solo una vez, hoy dia ya son 3 veces... no he hecho ningun cambio de hardware y lo unico q he cambiado de software fue el mozila q lo actualize, ventrilo que lo tengo hace una semana. :S

Pongo los MiniDump:

Primer pantallaso!!

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

Loading Dump File [C:\Windows\Minidump\Mini061609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*rutalocal*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`02fc6dd0
Debug session time: Tue Jun 16 19:29:09.330 2009 (GMT-5)
System Uptime: 0 days 1:01:48.263
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
...........................
Loading User Symbols
Loading unloaded module list
....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff81a02f7bdd0, c, 0, fffff80002e64eb7}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+47 )
Followup: MachineOwner
---------
3: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff81a02f7bdd0, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e64eb7, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003029080
fffff81a02f7bdd0
CURRENT_IRQL: c
FAULTING_IP:
nt!KiInsertTimerTable+47
fffff800`02e64eb7 488b5ff8 mov rbx,qword ptr [rdi-8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: dwm.exe
TRAP_FRAME: fffffa6006da6280 -- (.trap 0xfffffa6006da6280)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000061 rbx=0000000000000000 rcx=fffffa8007663c68
rdx=fffff80002f7bdd8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e64eb7 rsp=fffffa6006da6410 rbp=fffff80002f7b4c0
r8=fffffa8007663c68 r9=0000000000000001 r10=00001390a24bf1c2
r11=fffff80002f7bdd8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiInsertTimerTable+0x47:
fffff800`02e64eb7 488b5ff8 mov rbx,qword ptr [rdi-8] ds:6600:ffffffff`fffffff8=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e5c1ee to fffff80002e5c450
STACK_TEXT:
fffffa60`06da6138 fffff800`02e5c1ee : 00000000`0000000a fffff81a`02f7bdd0 00000000`0000000c 00000000`00000000 : nt!KeBugCheckEx
fffffa60`06da6140 fffff800`02e5b0cb : 00000000`00000000 00000000`00000000 00000000`00000000 00001390`a24bf1c2 : nt!KiBugCheckDispatch+0x6e
fffffa60`06da6280 fffff800`02e64eb7 : fffffa60`019d27f0 fffff800`02e64338 00001390`a24bf1c2 fffffa80`07663bb0 : nt!KiPageFault+0x20b
fffffa60`06da6410 fffff800`02e64338 : 00001390`a24bf1c2 fffffa80`07663bb0 fffffa60`019d2910 fffff960`0000000b : nt!KiInsertTimerTable+0x47
fffffa60`06da6420 fffff800`030bd84e : fffffa60`00000002 00000000`00000002 00000000`00000001 fffffa60`00000006 : nt!KeWaitForMultipleObjects+0x638
fffffa60`06da64a0 fffff800`030bde93 : 00000000`00000002 fffffa60`06da6a01 fffff900`00000001 fffff800`02e6a600 : nt!ObpWaitForMultipleObjects+0x26e
fffffa60`06da6960 fffff800`02e5bef3 : fffffa80`07663bb0 00000000`02bff588 fffffa60`06da6bc8 fffffa60`06da6ca0 : nt!NtWaitForMultipleObjects+0xe2
fffffa60`06da6bb0 00000000`776672ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02bff568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776672ca

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiInsertTimerTable+47
fffff800`02e64eb7 488b5ff8 mov rbx,qword ptr [rdi-8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiInsertTimerTable+47
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0237f
FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+47
BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+47
Followup: MachineOwner
---------

Segundo pantallaso!!


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

Loading Dump File [C:\Windows\Minidump\Mini061609-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*rutalocal*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`02e15000 PsLoadedModuleList = 0xfffff800`02fd9dd0
Debug session time: Tue Jun 16 23:09:07.834 2009 (GMT-5)
System Uptime: 0 days 3:39:14.732
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
.....................
Loading User Symbols
Loading unloaded module list
....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8, c, 0, fffff80002e94e4a}
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+89 )
Followup: MachineOwner
---------
3: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e94e4a, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000303c080
0000000000000008
CURRENT_IRQL: c
FAULTING_IP:
nt!KeSetEventBoostPriority+5a
fffff800`02e94e4a 48391b cmp qword ptr [rbx],rbx
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: main.exe
TRAP_FRAME: fffffa6008096390 -- (.trap 0xfffffa6008096390)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8000303e440 rbx=0000000000000000 rcx=fffffa60019d27f0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e94e4a rsp=fffffa6008096520 rbp=fffffa80061d01b0
r8=0000000000000000 r9=0000000000000000 r10=fffff8800fdf8000
r11=fffffa8004ee8260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeSetEventBoostPriority+0x5a:
fffff800`02e94e4a 48391b cmp qword ptr [rbx],rbx ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e6f1ee to fffff80002e6f450
STACK_TEXT:
fffffa60`08096248 fffff800`02e6f1ee : 00000000`0000000a 00000000`00000008 00000000`0000000c 00000000`00000000 : nt!KeBugCheckEx
fffffa60`08096250 fffff800`02e6e0cb : 00000000`00000000 fffffa80`06b214d0 00000000`00000000 00000000`00000008 : nt!KiBugCheckDispatch+0x6e
fffffa60`08096390 fffff800`02e94e4a : 00000000`00000000 fffffa80`08790af0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`08096520 fffffa60`02ed2545 : 00000000`00000000 fffffa80`041df420 fffffa80`041df480 00000000`80000011 : nt!KeSetEventBoostPriority+0x5a
fffffa60`08096560 fffffa60`02e78231 : 00000000`00000000 00000000`00000340 fffffa60`08096ca0 fffff880`0fc97770 : dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+0x89
fffffa60`080965c0 fffffa60`02e77ce1 : fffffa80`08703b01 fffffa80`00000001 fffffa60`019d2180 fffffa80`0470a9b0 : dxgkrnl!DXGCONTEXT::Render+0x1f9
fffffa60`080969b0 fffff960`0025255e : 00000000`0007e410 00000000`0b6bce01 fffffa60`000007dd 00000000`00000000 : dxgkrnl!DxgkRender+0x345
fffffa60`08096bf0 fffff800`02e6eef3 : fffffa80`08703bb0 fffffa60`08096ca0 00000000`0000032c fffffa80`0470a9b0 : win32k!NtGdiDdDDIRender+0x12
fffffa60`08096c20 00000000`7590b87a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0007e3e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7590b87a

STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+89
fffffa60`02ed2545 488b4730 mov rax,qword ptr [rdi+30h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+89
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49e02635
FAILURE_BUCKET_ID: X64_0xA_dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+89
BUCKET_ID: X64_0xA_dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+89
Followup: MachineOwner
---------
3: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e94e4a, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: 0000000000000008
CURRENT_IRQL: c
FAULTING_IP:
nt!KeSetEventBoostPriority+5a
fffff800`02e94e4a 48391b cmp qword ptr [rbx],rbx
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: main.exe
TRAP_FRAME: fffffa6008096390 -- (.trap 0xfffffa6008096390)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8000303e440 rbx=0000000000000000 rcx=fffffa60019d27f0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e94e4a rsp=fffffa6008096520 rbp=fffffa80061d01b0
r8=0000000000000000 r9=0000000000000000 r10=fffff8800fdf8000
r11=fffffa8004ee8260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeSetEventBoostPriority+0x5a:
fffff800`02e94e4a 48391b cmp qword ptr [rbx],rbx ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e6f1ee to fffff80002e6f450
STACK_TEXT:
fffffa60`08096248 fffff800`02e6f1ee : 00000000`0000000a 00000000`00000008 00000000`0000000c 00000000`00000000 : nt!KeBugCheckEx
fffffa60`08096250 fffff800`02e6e0cb : 00000000`00000000 fffffa80`06b214d0 00000000`00000000 00000000`00000008 : nt!KiBugCheckDispatch+0x6e
fffffa60`08096390 fffff800`02e94e4a : 00000000`00000000 fffffa80`08790af0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`08096520 fffffa60`02ed2545 : 00000000`00000000 fffffa80`041df420 fffffa80`041df480 00000000`80000011 : nt!KeSetEventBoostPriority+0x5a
fffffa60`08096560 fffffa60`02e78231 : 00000000`00000000 00000000`00000340 fffffa60`08096ca0 fffff880`0fc97770 : dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+0x89
fffffa60`080965c0 fffffa60`02e77ce1 : fffffa80`08703b01 fffffa80`00000001 fffffa60`019d2180 fffffa80`0470a9b0 : dxgkrnl!DXGCONTEXT::Render+0x1f9
fffffa60`080969b0 fffff960`0025255e : 00000000`0007e410 00000000`0b6bce01 fffffa60`000007dd 00000000`00000000 : dxgkrnl!DxgkRender+0x345
fffffa60`08096bf0 fffff800`02e6eef3 : fffffa80`08703bb0 fffffa60`08096ca0 00000000`0000032c fffffa80`0470a9b0 : win32k!NtGdiDdDDIRender+0x12
fffffa60`08096c20 00000000`7590b87a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0007e3e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7590b87a

STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+89
fffffa60`02ed2545 488b4730 mov rax,qword ptr [rdi+30h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+89
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49e02635
FAILURE_BUCKET_ID: X64_0xA_dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+89
BUCKET_ID: X64_0xA_dxgkrnl!VIDMM_DMA_POOL::AcquireBuffer+89
Followup: MachineOwner
---------


Tercer pantallaso!!

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

Loading Dump File [C:\Windows\Minidump\Mini061609-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*rutalocal*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0301edd0
Debug session time: Tue Jun 16 23:32:42.814 2009 (GMT-5)
System Uptime: 0 days 0:22:11.043
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
.....................
Loading User Symbols
Loading unloaded module list
....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffffa0004bafde0, 2, 0, fffffa6000cdd258}
Unable to load image kl1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by : NETIO.SYS ( NETIO!RtlLookupEntryHashTable+58 )
Followup: MachineOwner
---------
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa0004bafde0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa6000cdd258, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003081080
fffffa0004bafde0
CURRENT_IRQL: 2
FAULTING_IP:
NETIO!RtlLookupEntryHashTable+58
fffffa60`00cdd258 488b4110 mov rax,qword ptr [rcx+10h]
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffffa60060e8830 -- (.trap 0xfffffa60060e8830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa0004bafdd0
rdx=0000000090049dd5 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6000cdd258 rsp=fffffa60060e89c0 rbp=0000000000000000
r8=fffffa8004bafdd0 r9=fffffa60060e8a28 r10=fffffa8004bafdd0
r11=fffffa8004bac030 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
NETIO!RtlLookupEntryHashTable+0x58:
fffffa60`00cdd258 488b4110 mov rax,qword ptr [rcx+10h] ds:fffffa00`04bafde0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002eb41ee to fffff80002eb4450
STACK_TEXT:
fffffa60`060e86e8 fffff800`02eb41ee : 00000000`0000000a fffffa00`04bafde0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`060e86f0 fffff800`02eb30cb : 00000000`00000000 fffffa80`04a8d7a0 00000000`0000000c fffffa80`05124d10 : nt!KiBugCheckDispatch+0x6e
fffffa60`060e8830 fffffa60`00cdd258 : fffffa80`05124d10 00000000`00000001 fffffa80`05124d10 fffffa60`01069938 : nt!KiPageFault+0x20b
fffffa60`060e89c0 fffffa60`0106bde3 : fffffa80`05124d10 00000000`00000000 00000000`90049dd5 fffffa80`04b89540 : NETIO!RtlLookupEntryHashTable+0x58
fffffa60`060e89f0 fffffa60`0106ca3a : 00000000`00000001 fffffa80`05124d10 fffffa80`05124d10 00180000`00000000 : tcpip!TcpInsertTcb+0x93
fffffa60`060e8a90 fffffa60`01063535 : 00000000`0000444d fffffa80`057887c9 fffffa80`073d7350 00000000`00001002 : tcpip!TcpCreateAndConnectTcbRateLimitComplete+0x12 a
fffffa60`060e8be0 fffffa60`01068116 : 00000000`00000001 00000000`00000030 fffffa80`04b887c9 fffffa80`073d7350 : tcpip!TcpCreateAndConnectTcbInspectComplete+0x25
fffffa60`060e8c60 fffffa60`0106c7da : 00000000`00000000 fffffa80`04b89f01 fffffa80`05120002 fffffa60`060e92a0 : tcpip!TcpCreateAndConnectTcbWorkQueueRoutine+0x4d6
fffffa60`060e8f80 fffffa60`048c5f16 : fffffa80`052ad5e0 fffffa80`06a5ac00 00000000`00000000 fffffa80`05118850 : tcpip!TcpCreateAndConnectTcb+0x48a
fffffa60`060e9030 fffffa60`048c40e4 : fffffa80`0854a088 fffffa80`0854a010 fffffa80`052b6010 fffffa60`060e92a0 : tdx!TdxConnectConnection+0x4e6
fffffa60`060e9140 fffffa60`04a526bc : fffffa80`052b6010 fffff800`02ebf6e6 fffffa80`052b6010 00000000`fffffffe : tdx!TdxTdiDispatchInternalDeviceControl+0x158
fffffa60`060e9170 fffffa80`052b6010 : fffff800`02ebf6e6 fffffa80`052b6010 00000000`fffffffe 00000000`00000004 : kl1+0x476bc
fffffa60`060e9178 fffff800`02ebf6e6 : fffffa80`052b6010 00000000`fffffffe 00000000`00000004 fffffa80`08aca194 : 0xfffffa80`052b6010
fffffa60`060e9180 fffffa60`04a0d416 : 00000000`00000000 00000000`00000000 00000000`060e92e8 00000000`00000000 : nt!IopAllocateIrpPrivate+0x126
fffffa60`060e91e0 00000000`00000000 : 00000000`00000000 00000000`060e92e8 00000000`00000000 00000000`00000000 : kl1+0x2416

STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!RtlLookupEntryHashTable+58
fffffa60`00cdd258 488b4110 mov rax,qword ptr [rcx+10h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: NETIO!RtlLookupEntryHashTable+58
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 49e02e06
FAILURE_BUCKET_ID: X64_0xD1_NETIO!RtlLookupEntryHashTable+58
BUCKET_ID: X64_0xD1_NETIO!RtlLookupEntryHashTable+58
Followup: MachineOwner
---------


En espera de su ayuda nuevamente :(

[Terrano]

haber vams de "apoquitos" xD

1ero---http://www.bloodzone.net/forums/showthread.php?t=61910


2do-- pueda ser q sea un problema de temperatura de la tarjeta grafica o un problema con la ram..("testea" la ram) para esta ultima limpiala con mucho cuidado ( con alcohol isopropilico..nada de borrador ni esas cosas.. si no saes hacerlo moja un isopo y limpia con suavidad los conectores de oro con mucho cuidado ) y tb limpia los slot de la memoria esto con un inflador de globos para sacar el polvo y de paso limpias toda tu placa xD )
..ahora busca si hay alguna actualizacion de tus drivers de video

[ryohnosuke]

Has instalado los drivers manualmente? Quiero decir, vista me ha traído uno que otro dolor de cabeza cuando es este el que instala sus drivers.

Por ahí hace alguna referencia a la red, quizá si actualizas tu driver...

Saludos

[dhetox]

haber vams de "apoquitos" xD

1ero---http://www.bloodzone.net/forums/showthread.php?t=61910


2do-- pueda ser q sea un problema de temperatura de la tarjeta grafica o un problema con la ram..("testea" la ram) para esta ultima limpiala con mucho cuidado ( con alcohol isopropilico..nada de borrador ni esas cosas.. si no saes hacerlo moja un isopo y limpia con suavidad los conectores de oro con mucho cuidado ) y tb limpia los slot de la memoria esto con un inflador de globos para sacar el polvo y de paso limpias toda tu placa xD )
..ahora busca si hay alguna actualizacion de tus drivers de video

No creo que sea cosas de hardware de por si, porque todo es relativamente nuevo (ram 2 meses de uso, video 3 meses) todo esta limpio dentro

[dhetox]

Has instalado los drivers manualmente? Quiero decir, vista me ha traído uno que otro dolor de cabeza cuando es este el que instala sus drivers.

Por ahí hace alguna referencia a la red, quizá si actualizas tu driver...

Saludos

Nada de drivers recientemente,...
Lo unico que creo q puede ser es el HDD debidoa q mi disco esta dentro de los seagate que tienen q actualizarse el firmware... aun no lo he hecho xq no he podido hacer el backup... el viernes lo hare xq recien me prestaran un disco externo...
Q tan probbable es de q sea el disco?

[dhetox]

haber vams de "apoquitos" xD

1ero---http://www.bloodzone.net/forums/showthread.php?t=61910


2do-- pueda ser q sea un problema de temperatura de la tarjeta grafica o un problema con la ram..("testea" la ram) para esta ultima limpiala con mucho cuidado ( con alcohol isopropilico..nada de borrador ni esas cosas.. si no saes hacerlo moja un isopo y limpia con suavidad los conectores de oro con mucho cuidado ) y tb limpia los slot de la memoria esto con un inflador de globos para sacar el polvo y de paso limpias toda tu placa xD )
..ahora busca si hay alguna actualizacion de tus drivers de video

XD xcierto ese post fue creado por mi tambien xD hace algun tiempo,... cuando compre las ram.. y el error era por cuestion de voltajes de las ram...

EDIT: GRacias Terrano!!! Me hiciste recordar mi post anterior y lo del voltaje de las RAM y recorde que hace un dia o dia y medio actualice el bios de mi pc a la ultima version y se desconfiguro... osea el voltaje de mis ram eran nuevamente 1.8v.. ya lo cambie a 2.1v como deberia de ser... Ahora a esperar si todo vuelve a la normalidad :P

[dhetox]

Bueno puedo decir que el problema se arreglo, como dije en mi anterior replica fue xq actualice el bios y se cambiaron los valores que habia configurado anteriormente. :)

Gracias a todos por su ayuda