RE: Dell Inspiron 15 3521 blue screen of death

Re-Installed from the link you gave me
passed some days and now i got this:


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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff802`5d018000 PsLoadedModuleList = 0xfffff802`5d2e4a20
Debug session time: Mon Aug 26 23:01:25.956 2013 (UTC + 2:00)
System Uptime: 0 days 4:28:47.659
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880010d1861, fffff880009de1f8, fffff880009dda30}

*** WARNING: Unable to verify timestamp for Smb_driver_Intel.sys
*** ERROR: Module load completed but symbols could not be loaded for Smb_driver_Intel.sys
Probably caused by : Smb_driver_Intel.sys ( Smb_driver_Intel+1ef3 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880010d1861, The address that the exception occurred at
Arg3: fffff880009de1f8, Exception Record Address
Arg4: fffff880009dda30, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

FAULTING_IP:
Wdf01000!FxRequest::CompleteInternal+21
fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h]

EXCEPTION_RECORD: fffff880009de1f8 -- (.exr 0xfffff880009de1f8)
ExceptionAddress: fffff880010d1861 (Wdf01000!FxRequest::CompleteInternal+0x0000000000000021)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000b8
Attempt to read from address 00000000000000b8

CONTEXT: fffff880009dda30 -- (.cxr 0xfffff880009dda30)
rax=0000000000000000 rbx=fffffa80073dc020 rcx=fffffa80073dc020
rdx=00000000c0000120 rsi=0000000000000000 rdi=fffffa80090f6c40
rip=fffff880010d1861 rsp=fffff880009de430 rbp=00000000c0000120
r8=00000000c0000120 r9=fffff780000003b0 r10=fffffa8009196010
r11=0000000000000000 r12=0000057ff8c23fd8 r13=0000000000000000
r14=0000000000000000 r15=fffffa8009196010
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
Wdf01000!FxRequest::CompleteInternal+0x21:
fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h] ds:002b:00000000`000000b8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000000b8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8025d370168
GetUlongFromAddress: unable to read from fffff8025d3701f8
00000000000000b8 Nonpaged pool

FOLLOWUP_IP:
Smb_driver_Intel+1ef3
fffff880`0730fef3 ?? ???

BUGCHECK_STR: AV

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffff880010e4b02 to fffff880010d1861

STACK_TEXT:
fffff880`009de430 fffff880`010e4b02 : fffffa80`090b85b0 fffff880`010c63c0 fffffa80`090b85b0 fffffa80`073dc020 : Wdf01000!FxRequest::CompleteInternal+0x21
fffff880`009de4c0 fffff880`0730fef3 : fffffa80`073dc020 fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 : Wdf01000!imp_WdfRequestComplete+0x176
fffff880`009de520 fffffa80`073dc020 : fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 : Smb_driver_Intel+0x1ef3
fffff880`009de528 fffffa80`090f6ef0 : 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 : 0xfffffa80`073dc020
fffff880`009de530 00000000`00000000 : 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 00000000`00000000 : 0xfffffa80`090f6ef0


SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: Smb_driver_Intel+1ef3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Smb_driver_Intel

IMAGE_NAME: Smb_driver_Intel.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 50d3fb27

STACK_COMMAND: .cxr 0xfffff880009dda30 ; kb

FAILURE_BUCKET_ID: AV_Smb_driver_Intel+1ef3

BUCKET_ID: AV_Smb_driver_Intel+1ef3

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880010d1861, The address that the exception occurred at
Arg3: fffff880009de1f8, Exception Record Address
Arg4: fffff880009dda30, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

FAULTING_IP:
Wdf01000!FxRequest::CompleteInternal+21
fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h]

EXCEPTION_RECORD: fffff880009de1f8 -- (.exr 0xfffff880009de1f8)
ExceptionAddress: fffff880010d1861 (Wdf01000!FxRequest::CompleteInternal+0x0000000000000021)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000b8
Attempt to read from address 00000000000000b8

CONTEXT: fffff880009dda30 -- (.cxr 0xfffff880009dda30)
rax=0000000000000000 rbx=fffffa80073dc020 rcx=fffffa80073dc020
rdx=00000000c0000120 rsi=0000000000000000 rdi=fffffa80090f6c40
rip=fffff880010d1861 rsp=fffff880009de430 rbp=00000000c0000120
r8=00000000c0000120 r9=fffff780000003b0 r10=fffffa8009196010
r11=0000000000000000 r12=0000057ff8c23fd8 r13=0000000000000000
r14=0000000000000000 r15=fffffa8009196010
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
Wdf01000!FxRequest::CompleteInternal+0x21:
fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h] ds:002b:00000000`000000b8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000000b8

READ_ADDRESS: 00000000000000b8 Nonpaged pool

FOLLOWUP_IP:
Smb_driver_Intel+1ef3
fffff880`0730fef3 ?? ???

BUGCHECK_STR: AV

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffff880010e4b02 to fffff880010d1861

STACK_TEXT:
fffff880`009de430 fffff880`010e4b02 : fffffa80`090b85b0 fffff880`010c63c0 fffffa80`090b85b0 fffffa80`073dc020 : Wdf01000!FxRequest::CompleteInternal+0x21
fffff880`009de4c0 fffff880`0730fef3 : fffffa80`073dc020 fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 : Wdf01000!imp_WdfRequestComplete+0x176
fffff880`009de520 fffffa80`073dc020 : fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 : Smb_driver_Intel+0x1ef3
fffff880`009de528 fffffa80`090f6ef0 : 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 : 0xfffffa80`073dc020
fffff880`009de530 00000000`00000000 : 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 00000000`00000000 : 0xfffffa80`090f6ef0


SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: Smb_driver_Intel+1ef3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Smb_driver_Intel

IMAGE_NAME: Smb_driver_Intel.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 50d3fb27

STACK_COMMAND: .cxr 0xfffff880009dda30 ; kb

FAILURE_BUCKET_ID: AV_Smb_driver_Intel+1ef3

BUCKET_ID: AV_Smb_driver_Intel+1ef3

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880010d1861, The address that the exception occurred at
Arg3: fffff880009de1f8, Exception Record Address
Arg4: fffff880009dda30, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

FAULTING_IP:
Wdf01000!FxRequest::CompleteInternal+21
fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h]

EXCEPTION_RECORD: fffff880009de1f8 -- (.exr 0xfffff880009de1f8)
ExceptionAddress: fffff880010d1861 (Wdf01000!FxRequest::CompleteInternal+0x0000000000000021)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000b8
Attempt to read from address 00000000000000b8

CONTEXT: fffff880009dda30 -- (.cxr 0xfffff880009dda30)
rax=0000000000000000 rbx=fffffa80073dc020 rcx=fffffa80073dc020
rdx=00000000c0000120 rsi=0000000000000000 rdi=fffffa80090f6c40
rip=fffff880010d1861 rsp=fffff880009de430 rbp=00000000c0000120
r8=00000000c0000120 r9=fffff780000003b0 r10=fffffa8009196010
r11=0000000000000000 r12=0000057ff8c23fd8 r13=0000000000000000
r14=0000000000000000 r15=fffffa8009196010
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
Wdf01000!FxRequest::CompleteInternal+0x21:
fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h] ds:002b:00000000`000000b8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000000b8

READ_ADDRESS: 00000000000000b8 Nonpaged pool

FOLLOWUP_IP:
Smb_driver_Intel+1ef3
fffff880`0730fef3 ?? ???

BUGCHECK_STR: AV

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffff880010e4b02 to fffff880010d1861

STACK_TEXT:
fffff880`009de430 fffff880`010e4b02 : fffffa80`090b85b0 fffff880`010c63c0 fffffa80`090b85b0 fffffa80`073dc020 : Wdf01000!FxRequest::CompleteInternal+0x21
fffff880`009de4c0 fffff880`0730fef3 : fffffa80`073dc020 fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 : Wdf01000!imp_WdfRequestComplete+0x176
fffff880`009de520 fffffa80`073dc020 : fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 : Smb_driver_Intel+0x1ef3
fffff880`009de528 fffffa80`090f6ef0 : 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 : 0xfffffa80`073dc020
fffff880`009de530 00000000`00000000 : 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 00000000`00000000 : 0xfffffa80`090f6ef0


SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: Smb_driver_Intel+1ef3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Smb_driver_Intel

IMAGE_NAME: Smb_driver_Intel.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 50d3fb27

STACK_COMMAND: .cxr 0xfffff880009dda30 ; kb

FAILURE_BUCKET_ID: AV_Smb_driver_Intel+1ef3

BUCKET_ID: AV_Smb_driver_Intel+1ef3

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

0 Kudos