Hallo!
Seit ein paar Tagen startet mein Windows ohne Bluescreen einfach von neu. Dies geschiet komischerweise nach ca. 6 h Betriebszeit.
Danach kommt dann "Schwerwiegender Systemfehler..."
BCCode : 100000d1 BCP1 : 000003E8 BCP2 : 00000002 BCP3 : 00000008
BCP4 : 000003E8 OSVer : 5_1_2600 SP : 2_0 Product : 768_1
- Hab schon mal neueste Chipset drivers draufgeladen.
- memtest86 = RAM ok!
- Antivir = alles ok!
Mein System:
AMD Sempron 3000 mit 64 bit Unterstützung.
nForce 410 chipset
Mainboard: Foxcoon Winfast 6100 K8MB
Graka: Readon X550
Betriebssystemname Microsoft Windows XP Home Edition
Version 5.1.2600 Service Pack 2 Build 2600
Betriebssystemhersteller Microsoft Corporation
Systemname
Systemhersteller NVIDIA
Systemmodell AWRDACPI
Systemtyp X86-basierter PC
Prozessor x86 Family 15 Model 44 Stepping 2 AuthenticAMD ~1808 Mhz
BIOS-Version/-Datum Phoenix Technologies, LTD 6.00 PG, 23.09.2005
SMBIOS-Version 2.2
Windows-Verzeichnis C:\WINDOWS
Systemverzeichnis C:\WINDOWS\system32
Startgerät \Device\HarddiskVolume1
Gebietsschema Deutschland
Hardwareabstraktionsebene Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
Benutzername
Zeitzone Westeuropäische Normalzeit
Gesamter realer Speicher 1.024,00 MB
Verfügbarer realer Speicher 524,76 MB
Gesamter virtueller Speicher 2,00 GB
Verfügbarer virtueller Speicher 1,96 GB
Größe der Auslagerungsdatei 2,26 GB
Auslagerungsdatei C:\pagefile.sys
WinDbg (auslesen einer Minidump):
Probably caused by : NVENETFD.sys ( NVENETFD+45b4 ) Zitat:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini113006-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Nov 30 00:28:52.314 2006 (GMT+1)
System Uptime: 0 days 6:52:35.387
Loading Kernel Symbols
.....................................................................................................................
Loading User Symbols
Loading unloaded module list
.........................
Unable to load image NVENETFD.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for NVENETFD.sys
*** ERROR: Module load completed but symbols could not be loaded for NVENETFD.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {3e8, 2, 8, 3e8}
Probably caused by : NVENETFD.sys ( NVENETFD+45b4 )
Followup: MachineOwner
---------
kd> .reload
Loading Kernel Symbols
.....................................................................................................................
Loading User Symbols
Loading unloaded module list
.........................
kd> !analyze -v
Unable to load image NVENETFD.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for NVENETFD.sys
*** ERROR: Module load completed but symbols could not be loaded for NVENETFD.sys
*******************************************************************************
* *
* 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: 000003e8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 000003e8, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 000003e8
CURRENT_IRQL: 2
FAULTING_IP:
+3e8
000003e8 ?? ???
PROCESS_NAME: Idle
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from f77c45b4 to 000003e8
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
80548bfc f77c45b4 84bbaf88 f77c0435 84bfe900 0x3e8
80548c20 f72f187f 84bfe900 84be0698 84be0698 NVENETFD+0x45b4
80548c48 f6b16061 80548c6c 00000001 f6b16026 NDIS!NdisReturnPackets+0xe9
80548c60 f72f187f 850166e8 84be0698 8543b4e8 psched!MpReturnPacket+0x3b
80548c88 f77328e3 8543b538 00000001 84175938 NDIS!NdisReturnPackets+0xe9
80548c9c f773197f 00000000 84175bd0 f7738fe0 raspppoe!DereferencePacket+0xbf
80548cc4 f7736e9d 84175bd0 84175948 00000000 raspppoe!MpIndicateReceivedPackets+0x99
80548ce4 804ff234 f7739028 f7738fe0 213dc41b raspppoe!TimerEvent+0x7f
80548e00 804ff34b 80551b80 80551920 ffdff000 nt!KiTimerListExpire+0x122
80548e2c 80540d5d 80551f80 00000000 00182cd8 nt!KiTimerExpiration+0xaf
80548e40 80551920 ffdffc50 00000000 00000000 nt!KiRetireDpcList+0x46
80548e50 80540cd6 00000000 0000000e 00000000 nt!KiIdleThread0
80548e54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x26
STACK_COMMAND: kb
FOLLOWUP_IP:
NVENETFD+45b4
f77c45b4 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: NVENETFD+45b4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NVENETFD
IMAGE_NAME: NVENETFD.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43f615cd
FAILURE_BUCKET_ID: 0xD1_W_NVENETFD+45b4
BUCKET_ID: 0xD1_W_NVENETFD+45b4
Followup: MachineOwner
---------
|
Kann mir jemand weiterhelfen?
30.11.2006, 19:43
Baum-Darstellung