ich bekomme hin und wieder einen bluescreen und möchte euch fragen, ob mir jemand weiter helfen kann.
hier zunächst angaben zu meinem system
4GB-Kit G-Skill PC3-12800U CL9
AMD Phenom II X4 955 Black Edition Box, Sockel AM3
BE Quiet! Pure Power 530 Watt / BQT L7
Gigabyte GA-770TA-UD3, AMD 770
LG GH22LS50 Retail
Microsoft Windows 7 Home Premium 64-Bit (SB-Version)
Samsung SpinPoint F3 500GB, SATA II (HD502HJ)
Sapphire HD 5770 1GB GDDR5 PCI-Express
ZITAT
Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File C:\Windows\MEMORY.DMP
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a2e50
Debug session time: Mon Apr 19 19:11:05.725 2010 (UTC + 2:00)
System Uptime: 0 days 0:33:37.036
Loading Kernel Symbols
..................................................
.............
..................................................
..............
....................................
Loading User Symbols
Loading unloaded module list
......
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff8800b70cff8, 2, 1, fffff80002e3902e}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )
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: fffff8800b70cff8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002e3902e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: fffff8800b70cff8
CURRENT_IRQL: 2
FAULTING_IP:
hal!memcpy+25e
fffff800`02e3902e 48894118 mov qword ptr [rcx+18h],rax
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002ffb7e0 -- (.trap 0xfffff88002ffb7e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=2020202020202020 rbx=0000000000000000 rcx=fffff8800b70cfe0
rdx=fffffffffa552000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e3902e rsp=fffff88002ffb978 rbp=0000000000000002
r8=00000000000005b0 r9=000000000000002d r10=2020202020202020
r11=fffff8800b70ca50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
hal!memcpy+0x25e:
fffff800`02e3902e 48894118 mov qword ptr [rcx+18h],rax ds:db80:cff8=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ed4b69 to fffff80002ed5600
STACK_TEXT:
fffff880`02ffb698 fffff800`02ed4b69 : 00000000`0000000a fffff880`0b70cff8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02ffb6a0 fffff800`02ed37e0 : fffffa80`0499c010 fffff880`0b70ca50 00000000`00000000 00000000`00000002 : nt!KiBugCheckDispatch+0x69
fffff880`02ffb7e0 fffff800`02e3902e : fffff800`02e1ee15 fffff880`0b70ca50 00000000`00000002 fffffa80`04286cd0 : nt!KiPageFault+0x260
fffff880`02ffb978 fffff800`02e1ee15 : fffff880`0b70ca50 00000000`00000002 fffffa80`04286cd0 00000000`00000000 : hal!memcpy+0x25e
fffff880`02ffb980 fffff800`02e1e69a : fffffa80`053d2c80 fffff880`0b70ca00 fffffa80`053d3bc0 00000000`0000ff90 : hal!HalpDmaSyncMapBuffers+0x1bd
fffff880`02ffba30 fffff800`02e2183f : fffffa80`053d2c80 fffff880`0b70ca50 fffffa80`053d3bc0 00000000`0000ff90 : hal!HalpDmaFlushScatterTransfer+0xae
fffff880`02ffba80 fffff800`02e207d5 : fffffa80`049c5580 fffff880`0b70ca50 00000000`0000ff90 fffffa80`04286cd0 : hal!IoFlushAdapterBuffers+0xaf
fffff880`02ffbac0 fffff880`03f6f023 : fffffa80`04d851a0 fffffa80`0426ea80 fffffa80`04d85050 fffffa80`04d851a0 : hal!HalPutScatterGatherList+0x85
fffff880`02ffbb20 fffff880`03f6fab7 : 00000000`00000000 fffffa80`054b2af0 fffffa80`04d85a02 00000000`00000002 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x45f
fffff880`02ffbc00 fffff880`03f6d64f : fffffa80`04d85ea8 fffffa80`04d851a0 fffffa80`04d86040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02ffbc60 fffff880`03f5ef89 : fffffa80`04d85050 00000000`00000000 fffffa80`04d85e02 fffffa80`04d85ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02ffbca0 fffff800`02ee0cdc : fffff880`02fd3180 fffffa80`04d85ea8 fffffa80`04d85ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffbcd0 fffff800`02edddfa : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`03f5edb0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
fffff880`03f6f023 4533c0 xor r8d,r8d
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07
FAILURE_BUCKET_ID: X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
BUCKET_ID: X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
Followup: MachineOwner
---------
3: kd> lmvm USBPORT
start end module name
fffff880`03f5c000 fffff880`03fb2000 USBPORT (pdb symbols) c:\websymbols\usbport.pdb\845F4E75FADE4484B3A6EF6B6F404FA31\usbport.pdb
Loaded symbol image file: USBPORT.SYS
Image path: \SystemRoot\system32\DRIVERS\USBPORT.SYS
Image name: USBPORT.SYS
Timestamp: Tue Jul 14 02:06:31 2009 (4A5BCC07)
CheckSum: 0005E0B4
ImageSize: 00056000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: usbport.sys
OriginalFilename: usbport.sys
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: USB 1.1 & 2.0 Port Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
weiss jemand damit was anzufangen?
die treiber des mainboards und der grafikkarte habe ich über die jeweiligen herstellerseiten aktualisiert.
ich hoffe auf eure hilfe.