Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random BSODS


  • Please log in to reply
1 reply to this topic

#1 EvilSmoothie

EvilSmoothie

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:12:46 PM

Posted 19 May 2009 - 02:34 PM

I am now frequently getting BSOD's whilst using Windows 7 and I am struggling to find the cause of it. Every dump I get seems to produce completely differnt information Could somebody please look at my logs and have a bash at trying to work out why I am getting these dumps.

[codebox]
Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`0285d000 PsLoadedModuleList = 0xfffff800`02a96e90
Debug session time: Tue May 12 02:17:22.005 2009 (GMT+1)
System Uptime: 0 days 7:14:52.768
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800aece2b0, 0, fffff8800130847e, 2}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsInsertCachedLcn+8e )

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

0: kd> !analyse -v
No export analyse found
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8800aece2b0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800130847e, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b010e0
fffff8800aece2b0

FAULTING_IP:
Ntfs!NtfsInsertCachedLcn+8e
fffff880`0130847e 49837ccb0800 cmp qword ptr [r11+rcx*8+8],0

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff88002fb62b0 -- (.trap 0xfffff88002fb62b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000008c7 rbx=0000000000000000 rcx=0000000000001a55
rdx=00000000000008c7 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800130847e rsp=fffff88002fb6440 rbp=0000000000d48000
r8=0000000000a8d485 r9=00000000000008c8 r10=00000000000008c8
r11=fffff8800aec1000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
Ntfs!NtfsInsertCachedLcn+0x8e:
fffff880`0130847e 49837ccb0800 cmp qword ptr [r11+rcx*8+8],0 ds:fffff880`0aece2b0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002943ffa to fffff800028dbf80

STACK_TEXT:
fffff880`02fb6148 fffff800`02943ffa : 00000000`00000050 fffff880`0aece2b0 00000000`00000000 fffff880`02fb62b0 : nt!KeBugCheckEx
fffff880`02fb6150 fffff800`028da06e : 00000000`00000000 00000000`000008c8 00000000`001a9000 fffff880`02fb64d8 : nt! ?? ::FNODOBFM::`string'+0x3de60
fffff880`02fb62b0 fffff880`0130847e : fffffa80`048e6180 00000000`00d48000 fffff880`02fb6600 fffffa80`05a56820 : nt!KiPageFault+0x16e
fffff880`02fb6440 fffff880`013080a6 : fffffa80`048e6180 fffffa80`048e6180 fffffa80`04847a00 00000000`000008c8 : Ntfs!NtfsInsertCachedLcn+0x8e
fffff880`02fb64d0 fffff880`012be760 : fffffa80`06082000 fffffa80`04847a50 00000000`00d48000 00000000`00000000 : Ntfs!NtfsAddCachedRun+0x56
fffff880`02fb6510 fffff880`012d3b78 : fffff800`02a6e5e0 fffffa80`048e6180 fffffa80`04847a50 fffffa80`06082000 : Ntfs!NtfsAddCachedRunMult+0x50
fffff880`02fb6550 fffff880`012c51b0 : fffffa80`04847a50 fffffa80`048e6180 00000000`00000000 00000000`00d48000 : Ntfs!NtfsScanEntireBitmap+0x458
fffff880`02fb6840 fffff880`012d20ee : fffffa80`04847a50 fffffa80`048e6180 fffffa80`048e6180 fffffa80`048e6180 : Ntfs!NtfsInitializeClusterAllocation+0x60
fffff880`02fb6870 fffff880`012e78f1 : fffff880`02fb6c40 00000000`00000000 00000000`00000000 fffffa80`06078b80 : Ntfs!NtfsMountVolume+0x13de
fffff880`02fb6ba0 fffff880`0124e65c : 00000000`00000000 00000000`00000000 fffffa80`04847a50 fffff880`05795e83 : Ntfs!NtfsCommonFileSystemControl+0x51
fffff880`02fb6be0 fffff800`028e1744 : fffff800`02a6e500 fffffa80`04c58400 fffffa80`036fdb00 00000000`00000001 : Ntfs!NtfsFspDispatch+0x25c
fffff880`02fb6cb0 fffff800`02b61e66 : 00000000`00000000 00000000`00000000 fffffa80`036fdb60 ffff16ff`3f00ff00 : nt!ExpWorkerThread+0x11a
fffff880`02fb6d40 fffff800`0288ea86 : fffff880`009e6180 fffffa80`036fdb60 fffff880`009f0f40 b5bf68ff`7f00ff00 : nt!PspSystemThreadStartup+0x5a
fffff880`02fb6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
Ntfs!NtfsInsertCachedLcn+8e
fffff880`0130847e 49837ccb0800 cmp qword ptr [r11+rcx*8+8],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: Ntfs!NtfsInsertCachedLcn+8e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee8de7

FAILURE_BUCKET_ID: X64_0x50_Ntfs!NtfsInsertCachedLcn+8e

BUCKET_ID: X64_0x50_Ntfs!NtfsInsertCachedLcn+8e

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

0: kd> !pool
The pool page you have specified is not in this dump.
0: kd> !pte
VA 0000000000000000
PXE @ FFFFF6FB7DBED000 PPE at FFFFF6FB7DA00000 PDE at FFFFF6FB40000000 PTE at FFFFF68000000000
Unable to get PXE FFFFF6FB7DBED000
[/codebox]


[codebox]
Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02859000 PsLoadedModuleList = 0xfffff800`02a92e90
Debug session time: Tue May 19 19:39:04.512 2009 (GMT+1)
System Uptime: 1 days 0:29:35.401
Loading Kernel Symbols
...................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8800188b6c0, 0, ffffffffffffffff}

Probably caused by : tcpip.sys ( tcpip!ConcatenateList+30 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800188b6c0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
tcpip!ConcatenateList+30
fffff880`0188b6c0 c3 ret

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002afd0e0
ffffffffffffffff

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff8000293da1a to fffff800028d7f80

STACK_TEXT:
fffff800`00b9b928 fffff800`0293da1a : 00000000`0000001e ffffffff`c0000005 fffff880`0188b6c0 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9b930 fffff800`028d75c2 : fffff800`00b9c108 fffffa80`041bc7b0 fffff800`00b9c1b0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3b64a
fffff800`00b9bfd0 fffff800`028d5eca : fffffa80`03b33390 fffff880`0187ef47 fffffa80`03b33390 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c1b0 fffff880`0188b6c0 : fffff880`0187b07d fffffa80`036fbc68 00000000`00000001 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c348 fffff880`0187b07d : fffffa80`036fbc68 00000000`00000001 00000000`00000000 fffffa80`036fbc68 : tcpip!ConcatenateList+0x30
fffff800`00b9c350 fffff880`0187b3ad : fffffa80`05521900 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TtFireTimerEx+0xed
fffff800`00b9c3b0 fffff880`0187ab4a : fffffa80`041ba988 fffff880`0187a708 fffffa80`05521900 00000000`00000000 : tcpip!IppAddressSetTimeout+0x5d
fffff800`00b9c4d0 fffff880`0187ad98 : fffffa80`041ba928 fffff800`00b9c680 00000000`00000000 00000000`01c9d8b1 : tcpip!Ipv4pInterfaceSetTimeout+0x7f
fffff800`00b9c550 fffff880`0187af2a : fffff800`00b9c680 00000000`01c9d8b1 00000000`00000001 fffff800`00b9ccd0 : tcpip!IppCompartmentSetTimeout+0x88
fffff800`00b9c5c0 fffff800`02907906 : fffffa80`06673060 fffff800`028dfdde fffffa80`06673120 fffffa80`06673060 : tcpip!IppTimeout+0x5a
fffff800`00b9c5f0 fffff800`028dab67 : fffff800`02a3fe80 fffffa80`06673120 00000000`00000001 fffff800`02a3fe80 : nt!KiProcessTimerDpcTable+0x86
fffff800`00b9c660 fffff800`028da9e2 : 000000cd`4ca2776c 00000000`00563f09 fffff800`02a423a0 00000000`00000003 : nt!KiProcessExpiredTimerList+0x137
fffff800`00b9ccb0 fffff800`028da6cf : 00000000`000000c2 fffff800`02a423a8 00000000`00000009 00000000`00000002 : nt!KiTimerExpiration+0x272
fffff800`00b9cd50 fffff800`028cf41a : fffff800`02a3fe80 00000000`00000002 fffff800`02a4dc40 fffffa80`05938b60 : nt!KiRetireDpcList+0xc9
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
tcpip!ConcatenateList+30
fffff880`0188b6c0 c3 ret

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: tcpip!ConcatenateList+30

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME: tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee8ebc

FAILURE_BUCKET_ID: X64_0x1E_tcpip!ConcatenateList+30

BUCKET_ID: X64_0x1E_tcpip!ConcatenateList+30

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

[/codebox]

[codebox]
Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02859000 PsLoadedModuleList = 0xfffff800`02a92e90
Debug session time: Tue May 19 19:52:30.906 2009 (GMT+1)
System Uptime: 0 days 0:12:47.795
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002bb5d90, fffff88005b92120, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+40 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002bb5d90, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88005b92120, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!ObReferenceObjectByHandleWithTag+40
fffff800`02bb5d90 4c8923 mov qword ptr [rbx],r12

CONTEXT: fffff88005b92120 -- (.cxr 0xfffff88005b92120)
rax=fffffa800678f060 rbx=7ffff88005b92c28 rcx=00000000000002f4
rdx=0000000000000002 rsi=0000000073a990e0 rdi=fffffa800678f060
rip=fffff80002bb5d90 rsp=fffff88005b92b00 rbp=fffff88005b92c00
r8=fffffa80036f3570 r9=0000000077dc0001 r10=fffff80002b6f510
r11=0000000000293e10 r12=0000000000000000 r13=0000000002f5fd20
r14=0000000000000001 r15=fffffa8006047340
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!ObReferenceObjectByHandleWithTag+0x40:
fffff800`02bb5d90 4c8923 mov qword ptr [rbx],r12 ds:002b:7ffff880`05b92c28=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: aim6.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002b6f54f to fffff80002bb5d90

STACK_TEXT:
fffff880`05b92b00 fffff800`02b6f54f : 00000000`00000000 00000000`00000002 fffffa80`036f3570 fffff880`05b92c01 : nt!ObReferenceObjectByHandleWithTag+0x40
fffff880`05b92bd0 fffff800`028d71d3 : fffffa80`0678f060 fffff880`05b92ca0 00000000`00000000 fffffa80`067789a0 : nt!NtClearEvent+0x3f
fffff880`05b92c20 00000000`744e2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02f5f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x744e2dd9


FOLLOWUP_IP:
nt!ObReferenceObjectByHandleWithTag+40
fffff800`02bb5d90 4c8923 mov qword ptr [rbx],r12

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ObReferenceObjectByHandleWithTag+40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee9439

STACK_COMMAND: .cxr 0xfffff88005b92120 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!ObReferenceObjectByHandleWithTag+40

BUCKET_ID: X64_0x3B_nt!ObReferenceObjectByHandleWithTag+40

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

[/codebox]


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

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`0281b000 PsLoadedModuleList = 0xfffff800`02a54e90
Debug session time: Tue May 19 20:03:03.649 2009 (GMT+1)
System Uptime: 0 days 0:09:47.537
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C7, {5, fffff880010c27c0, 0, 0}

Probably caused by : storport.sys ( storport!RaidpAdapterTimerDpcRoutine+0 )

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

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

TIMER_OR_DPC_INVALID (c7)
Kernel timer or DPC used incorrectly.
Arguments:
Arg1: 0000000000000005, Thread APC disable count was changed during timer DPC routine execution.
Arg2: fffff880010c27c0, Address of the DPC routine.
Arg3: 0000000000000000, Thread APC disable count before calling DPC routine.
Arg4: 0000000000000000, Thread APC disable count after calling DPC routine.
The APC disable count is decremented each time a driver calls
KeEnterCriticalRegion, FsRtlEnterFileSystem, or acquires a mutex. The APC
disable count is incremented each time a driver calls KeLeaveCriticalRegion,
FsRtlExitFileSystem, or KeReleaseMutex.

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


INVALID_DPC_FOUND: fffff880010c27c0

FAULTING_IP:
storport!RaidpAdapterTimerDpcRoutine+0
fffff880`010c27c0 48895c2408 mov qword ptr [rsp+8],rbx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xC7

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800028c9974 to fffff80002899f80

STACK_TEXT:
fffff800`03c855e8 fffff800`028c9974 : 00000000`000000c7 00000000`00000005 fffff880`010c27c0 00000000`00000000 : nt!KeBugCheckEx
fffff800`03c855f0 fffff800`0289cb67 : fffff800`02a01e80 fffffa80`053c4600 00000000`00000003 fffff800`02a01e80 : nt!KiProcessTimerDpcTable+0xf4
fffff800`03c85660 fffff800`0289c9e2 : 00000001`5e331b98 00000000`0000931e fffff800`02a04640 00000000`00000006 : nt!KiProcessExpiredTimerList+0x137
fffff800`03c85cb0 fffff800`0289c6cf : 00000000`000000c5 fffff800`02a04648 00000000`0000001e 00000000`00000002 : nt!KiTimerExpiration+0x272
fffff800`03c85d50 fffff800`0289141a : fffff800`02a01e80 00000000`00000002 fffff800`02a0fc40 fffffa80`06925060 : nt!KiRetireDpcList+0xc9
fffff800`03c85d80 00000000`00000000 : fffff800`03c86000 fffff800`03c80000 fffff800`03c85d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
storport!RaidpAdapterTimerDpcRoutine+0
fffff880`010c27c0 48895c2408 mov qword ptr [rsp+8],rbx

SYMBOL_NAME: storport!RaidpAdapterTimerDpcRoutine+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: storport

IMAGE_NAME: storport.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee98a6

FAILURE_BUCKET_ID: X64_0xC7_storport!RaidpAdapterTimerDpcRoutine+0

BUCKET_ID: X64_0xC7_storport!RaidpAdapterTimerDpcRoutine+0

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

0: kd> lmv m storport
start end module name
fffff880`010b3000 fffff880`01115000 storport (pdb symbols) c:\websymbols\storport.pdb\9E559F174DDD4E6DB8072569EB0DC9892\storport.pdb
Loaded symbol image file: storport.sys
Mapped memory image file: c:\websymbols\storport.sys\49EE98A662000\storport.sys
Image path: \SystemRoot\system32\DRIVERS\storport.sys
Image name: storport.sys
Timestamp: Wed Apr 22 05:10:14 2009 (49EE98A6)
CheckSum: 00031C71
ImageSize: 00062000
File version: 6.1.7100.0
Product version: 6.1.7100.0
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0000.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: storport.sys
OriginalFilename: storport.sys
ProductVersion: 6.1.7100.0
FileVersion: 6.1.7100.0 (winmain_win7rc.090421-1700)
FileDescription: Microsoft Storage Port Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
[/codebox]

That there is just 4 of many.. Any help would be greatly apprciated.
Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.

BC AdBot (Login to Remove)

 


#2 bandaid1968

bandaid1968

  • Members
  • 89 posts
  • OFFLINE
  •  
  • Local time:06:46 AM

Posted 21 May 2009 - 12:07 AM

sounds like you have a driver problem with your network card, try updating your drivers or replace your network card,but i could be wrong but its somewhere to start




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users