Hallo, ich habe ein Problem mit meinem Rechner. Seit kurzem bekomme ich immer wieder Bluescreens. Am häufigsten treten sie beim Booten auf. Es kommt jedoch auch vor das der Rechner Stundenlang vollkommen stabil läuft.
Was mir dazu aufgefallen ist, das manchmal nur 3,5 gb (von 6gb) RAM verwendbar sind, anders rum sind die manchmal komplett nutzbar.
Informationen zum System:
Processor ID = 0
Number of cores 2 (max 2)
Number of threads 2 (max 2)
Name Intel Core 2 Duo E8400
Codename Wolfdale
Specification Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Package (platform ID) Socket 775 LGA (0x0)
CPUID 6.7.6
Extended CPUID 6.17
Core Stepping C0
Technology 45 nm
Core Speed 1999.8 MHz
Multiplier x FSB 6.0 x 333.3 MHz
Rated Bus speed 1333.2 MHz
Stock frequency 3000 MHz
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, EM64T, VT-x
L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 6144 KBytes, 24-way set associative, 64-byte line size
FID/VID Control yes
FID range 6.0x - 9.0x
Max VID 1.225 V
TDP Limit 65 Watts
Chipset
Northbridge Intel P35/G33/G31 rev. A2
Southbridge Intel 82801IR (ICH9R) rev. 02
Graphic Interface PCI-Express
PCI-E Link Width x16
PCI-E Max Link Width x16
Memory Type DDR2
Memory Size 6144 MBytes
Channels Dual, (Symmetric)
Memory Frequency 400.0 MHz (5:6)
CAS# latency (CL) 5.0
RAS# to CAS# delay (tRCD) 5
RAS# Precharge (tRP) 5
Cycle Time (tRAS) 15
Row Refresh Cycle Time (tRFC) 52
Command Rate (CR) 2T
Name NVIDIA GeForce 8800 GT (Microsoft Corporation - WDDM v1.1)
Revision A2
Codename G92
Technology 65 nm
Memory size 512 MB
Memory bus width 256 bits
DIMM # 1
SMBus address 0x50
Memory type DDR2
Module format Regular UDIMM
Manufacturer (ID) G.Skill (7F7F7F7FCD000000)
Size 2048 MBytes
Max bandwidth PC2-6400 (400 MHz)
Part number F2-6400CL5-2GBPQ
Number of banks 2
Data width 64 bits
Correction None
Nominal Voltage 1.80 Volts
EPP no
XMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 4.0-4-4-10-16 @ 266 MHz
JEDEC #2 5.0-5-5-15-24 @ 400 MHz
DIMM # 2
SMBus address 0x51
Memory type DDR2
Module format Regular UDIMM
Manufacturer (ID) G.Skill (7F7F7F7FCD000000)
Size 1024 MBytes
Max bandwidth PC2-6400 (400 MHz)
Part number F2-6400CL5-1GBNQ
Number of banks 1
Data width 64 bits
Correction None
Nominal Voltage 1.80 Volts
EPP no
XMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 3.0-3-3-8-12 @ 200 MHz
JEDEC #2 4.0-4-4-10-16 @ 266 MHz
JEDEC #3 5.0-5-5-15-23 @ 400 MHz
DIMM # 3
SMBus address 0x52
Memory type DDR2
Module format Regular UDIMM
Manufacturer (ID) G.Skill (7F7F7F7FCD000000)
Size 2048 MBytes
Max bandwidth PC2-6400 (400 MHz)
Part number F2-6400CL5-2GBPQ
Number of banks 2
Data width 64 bits
Correction None
Nominal Voltage 1.80 Volts
EPP no
XMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 4.0-4-4-10-16 @ 266 MHz
JEDEC #2 5.0-5-5-15-24 @ 400 MHz
DIMM # 4
SMBus address 0x53
Memory type DDR2
Module format Regular UDIMM
Manufacturer (ID) G.Skill (7F7F7F7FCD000000)
Size 1024 MBytes
Max bandwidth PC2-6400 (400 MHz)
Part number F2-6400CL5-1GBNQ
Number of banks 1
Data width 64 bits
Correction None
Nominal Voltage 1.80 Volts
EPP no
XMP no
Windows 7 64 Bit
Ich habe mit dem Windows Debugger eine Dump Datei ausgelesen.
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112610-16458-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: (copy&paste)srv*c:\symbols*http://msdl.microsoft.com/download/symbols;SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02865000 PsLoadedModuleList = 0xfffff800`02aa2e50
Debug session time: Fri Nov 26 14:00:19.367 2010 (GMT+1)
System Uptime: 0 days 0:09:17.224
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002bdb0b9, 0, f0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpDispatchReplyToWaitingThread+29 )
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: fffff80002bdb0b9, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 00000000000000f0, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt!AlpcpDispatchReplyToWaitingThread+29
fffff800`02bdb0b9 493b85e0000000 cmp rax,qword ptr [r13+0E0h]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000000000f0
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0d0e0
00000000000000f0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: mscorsvw.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff88007df1a38 -- (.exr 0xfffff88007df1a38)
ExceptionAddress: fffff80002bdb0b9 (nt!AlpcpDispatchReplyToWaitingThread+0x0000000000000029)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000f0
Attempt to read from address 00000000000000f0
TRAP_FRAME: fffff88007df1ae0 -- (.trap 0xfffff88007df1ae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000d0 rbx=0000000000000000 rcx=fffff88007df1e78
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002bdb0b9 rsp=fffff88007df1c70 rbp=0000000080010001
r8=fffff88007df22b8 r9=00000000000000a8 r10=fffff80002a619c0
r11=fffff88007df1d20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!AlpcpDispatchReplyToWaitingThread+0x29:
fffff800`02bdb0b9 493b85e0000000 cmp rax,qword ptr [r13+0E0h] ds:00000000`000000e0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000290fa39 to fffff800028d5740
STACK_TEXT:
fffff880`07df1268 fffff800`0290fa39 : 00000000`0000001e ffffffff`c0000005 fffff800`02bdb0b9 00000000`00000000 : nt!KeBugCheckEx
fffff880`07df1270 fffff800`028d4d82 : fffff880`07df1a38 00000000`00000000 fffff880`07df1ae0 fffff8a0`06018d00 : nt!KiDispatchException+0x1b9
fffff880`07df1900 fffff800`028d38fa : 00000000`00000000 00000000`00000000 fffffa80`057ec100 fffff880`00001f80 : nt!KiExceptionDispatch+0xc2
fffff880`07df1ae0 fffff800`02bdb0b9 : 00000000`00000000 00000000`00000000 fffffa80`053d1330 fffff880`07df1d60 : nt!KiPageFault+0x23a
fffff880`07df1c70 fffff800`02bd549d : fffffa80`00000104 00000000`00032000 00000000`00000010 00000000`00000036 : nt!AlpcpDispatchReplyToWaitingThread+0x29
fffff880`07df1cd0 fffff800`02bd9a06 : 00000000`02969cb2 00000000`00000080 00000000`00000000 00000000`00000000 : nt!AlpcpSendMessage+0x66b
fffff880`07df1dd0 fffff800`02be83dd : fffffa80`06e16c90 fffff880`00020002 fffff880`07df2290 00000000`00000000 : nt!AlpcpProcessSynchronousRequest+0x2f3
fffff880`07df1ef0 fffff800`02cc7879 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!LpcpRequestWaitReplyPort+0x9c
fffff880`07df1f50 fffff800`02cc799f : 00000000`00000003 00000000`00000000 fffff680`00000190 00000000`00000111 : nt!LpcRequestWaitReplyPortEx+0x29
fffff880`07df1f90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpSendApiMessageLpc+0x3f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!AlpcpDispatchReplyToWaitingThread+29
fffff800`02bdb0b9 493b85e0000000 cmp rax,qword ptr [r13+0E0h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!AlpcpDispatchReplyToWaitingThread+29
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_nt!AlpcpDispatchReplyToWaitingThread+29
BUCKET_ID: X64_0x1E_nt!AlpcpDispatchReplyToWaitingThread+29
Followup: MachineOwner
---------
Ich haben seit dem Problem einmal das System neu aufegesetzt. Es wurde damit etwas besser, aber das Problem ist noch nicht behoben.
So ich hoffe ich haben den Ramen nicht gesprengt.Hoffe ihr könnt mir weiterhelfen.
Gruß Hauke
draco2601 Gast |
