Blue screen- bsod IMAGE_NAME: NVENETFD.sys

[kat666]

WRITE_ADDRESS: 00751790

CURRENT_IRQL: 2

FAULTING_IP:
tcpip!SendACK+cd
b47d14d8 891f mov dword ptr [edi],ebx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b47d4058 to b47d14d8

STACK_TEXT:
b84d3b58 b47d4058 0077ee68 00000040 00000000 tcpip!SendACK+0xcd
b84d3b78 b47cda0e 00000002 00000002 b84d3ba4 tcpip!ProcessPerCpuTCBDelayQ+0xc6
b84d3bac b47cd955 00000002 b47cd901 b47cd3d6 tcpip!ProcessTCBDelayQ+0xc4
b84d3bb8 b47cd3d6 00000000 89a15ad0 b47cd7f8 tcpip!TCPRcvComplete+0x20
b84d3bc4 b47cd7f8 b7e4fc40 899a49e8 b6fd6b40 tcpip!IPRcvComplete+0x21
b84d3bc8 b7e4fc40 899a49e8 b6fd6b40 889dd780 tcpip!ARPRcvComplete+0x5
b84d3c18 b6fd101d 000278c8 89b10100 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
b84d3c2c b6fd11b4 89a15ad0 89b10100 00000001 psched!PsFlushReceiveQueue+0x15
b84d3c50 b6fd15f9 889dd788 00000000 89a15ad0 psched!PsEnqueueReceivePacket+0xda
b84d3c68 b7e4fc40 889dd780 00000000 89624000 psched!ClReceiveComplete+0x13
b84d3cb8 b827b9dc 000278c8 896245f0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 NVENETFD+0x39dc


STACK_COMMAND: kb

FOLLOWUP_IP:
NVENETFD+39dc
b827b9dc ?? ???

SYMBOL_STACK_INDEX: b

SYMBOL_NAME: NVENETFD+39dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NVENETFD

IMAGE_NAME: NVENETFD.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 463be0da

FAILURE_BUCKET_ID: 0xD1_NVENETFD+39dc

BUCKET_ID: 0xD1_NVENETFD+39dc

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

Fotka:
Dostępne tylko dla zarejestrowanych użytkowników


Notorycznie wyplywa mi takie blue screeny, jakieś pomysły co może być przyczyną?

[cosik_ktosik]

NVENETFD.sys

Jest to sterownik chyba sieci o nazwie:
NVIDIA nForce Networking Controller Driver

Proponuję jego aktualizację.

[kat666]

Zainstalowałem najnowszy sterownik ze strony nvidii nforce, blue screen ponownie wyskoczył.

Tym razem takie coś, nie wiem czy jest różnica:


BUGCHECK_STR: 0x7f_d

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: javaw.exe

LAST_CONTROL_TRANSFER: from 804fc8ac to c07fe000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b458d918 804fc8ac 00000000 8a477550 00023cb4 0xc07fe000
b458d92c 804fc97c 8a13badc 00000001 00000000 nt!KeReleaseMutant+0x10
b458d944 b4f284e6 8a13badc 00000000 b458da14 nt!KeReleaseMutex+0x14
b458d96c b4dd7209 02477550 b458d98c b458da14 RtkHDAud+0x1344e6
b458d990 b4dd2835 02477b6c b458d9cc 8a478668 portcls!CPortPinWaveCyclic::GetPosition+0x2f
b458d9b4 b4dd72c1 000b2008 b458d9cc 8a477b68 portcls!CIrpStream::GetPosition+0x5a
b458da14 b4dd73c8 8a477b68 892fa4f0 0000000c portcls!CPortPinWaveCyclic::GetKsAudioPosition+0x1d
b458da2c b7c57ea8 8a478668 892fa500 892fa4f0 portcls!CPortPinWaveCyclic::GetKsAudioPosition+0x124
b458da90 b7c57ed9 8a478668 0000000c e1b2ddc0 ks!KspPropertyHandler+0x602
b458dab4 b4de06a9 8a478668 0000000c e1b2dd98 ks!KsPropertyHandler+0x19
b458dac8 b4ded70f 8a478668 0000000c e1b2dd98 portcls!PcHandlePropertyWithTable+0x1b
b458db00 b4de074d 8a477b68 8a4bddb0 8a478668 portcls!CPortPinWaveCyclic::DeviceIoControl+0x1e5
b458db1c b7c57f1f 8a4bddb0 8a478668 b458db44 portcls!DispatchDeviceIoControl+0x49
b458db2c b4de08c0 8a4bddb0 8a478668 8a4bde68 ks!KsDispatchIrp+0x126
b458db44 b4de0881 8a4bddb0 8a478668 b458db78 portcls!KsoDispatchIrp+0x43
b458db54 b51bc08e 8a4bddb0 8a478668 00000000 portcls!PcDispatchIrp+0x5f
b458db78 804ef19f 8a4bddb0 00000010 8a478668 RtkHDAud+0x3c808e
b458db88 b4872774 e29c98d8 00000000 8a478668 nt!IopfCallDriver+0x31
b458dbd8 b48752a2 8a478668 00000000 e114b938 sysaudio!ForwardIrpNode+0x1b2
b458dc30 b7c57f95 892ea030 8a478668 b458dc64 sysaudio!CPinInstance::PinDispatchIoControl+0x153
b458dc40 804ef19f 892ea030 8a478668 806e7410 ks!DispatchDeviceIoControl+0x28
b458dc50 8057f98e 8a4787b0 89265900 8a478668 nt!IopfCallDriver+0x31
b458dc64 8058081d 892ea030 8a478668 89265900 nt!IopSynchronousServiceTail+0x70
b458dd00 80579298 000001fc 00000380 00000000 nt!IopXxxControlFile+0x5c5
b458dd34 8054167c 000001fc 00000380 00000000 nt!NtDeviceIoControlFile+0x2a
b458dd34 7c90e514 000001fc 00000380 00000000 nt!KiFastCallEntry+0xfc
4cb6fe5c 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
RtkHDAud+1344e6
b4f284e6 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: RtkHDAud+1344e6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME: RtkHDAud.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4670ff4f

FAILURE_BUCKET_ID: 0x7f_d_RtkHDAud+1344e6

BUCKET_ID: 0x7f_d_RtkHDAud+1344e6

Followup: MachineOwner

[djkamil09061991]

Tym razem sterownik od karty dzwiękowej Realtek HD. Tak więc również przeinstaluj go na inną wersję.

[cosik_ktosik]

I sterownik od chipsetu bo to jakby nie patrzeć on zawiaduje całym komputerem, a cała reszta jest zależna właśnie od niego.

[kat666]

Wszystkie sterowniki zaktualizowałem. Dzisiaj robiłem format, mam w pełni zaktualizowanego win xp. Dodam jeszcze, że kości ramu sprawdzałem każdą pojedynczo(po jednej wyciągałem ze slotu). Hd Tune, Memtest86 żadnych błędów nie znalazły.


Przed chwilą:
EXCEPTION_CODE: (Win32) 0x80 (128) - Nie ma proces w podrz dnych, na kt re trzeba by czeka .

FAULTING_IP:
nt!KeReleaseMutant+59
804fc8f5 ff4604 inc dword ptr [esi+4]

TRAP_FRAME: b4367564 -- (.trap 0xffffffffb4367564)
ESP EDITED! New esp=b4367914
ErrCode = 00000000
eax=00000080 ebx=00000002 ecx=00000041 edx=00000000 esi=82196adc edi=88ff9450
eip=804fc8f5 esp=b43675d8 ebp=b4367924 iopl=0 nv up ei pl nz ac po cy
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000213
nt!KeReleaseMutant+0x59:
804fc8f5 ff4604 inc dword ptr [esi+4] ds:0023:82196ae0=0001f1fc
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: javaw.exe

LAST_CONTROL_TRANSFER: from 804fc97c to 804fc8f5

STACK_TEXT:
b4367924 804fc97c 0001f1fc 00000001 00000000 nt!KeReleaseMutant+0x59
b436793c b4bb1e6d 8a196adc 00000000 b4367a14 nt!KeReleaseMutex+0x14
WARNING: Stack unwind information not available. Following frames may be wrong.
b436796c b4b29209 02f4f008 b436798c b4367a14 RtkHDAud+0x6be6d
b4367990 b4b24835 02f3eaa4 b43679cc 88f21008 portcls!CPortPinWaveCyclic::GetPosition+0x2f
b43679b4 b4b292c1 00fd4490 b43679cc 88f3eaa0 portcls!CIrpStream::GetPosition+0x5a
b4367a14 b4b293c8 88f3eaa0 88f9e128 0000000c portcls!CPortPinWaveCyclic::GetKsAudioPosition+0x1d
b4367a2c b7c57ea8 88f21008 88f9e138 88f9e128 portcls!CPortPinWaveCyclic::GetKsAudioPosition+0x124
b4367a90 b7c57ed9 88f21008 0000000c e1b3fb30 ks!KspPropertyHandler+0x602
b4367ab4 b4b326a9 88f21008 0000000c e1b3fb08 ks!KsPropertyHandler+0x19
b4367ac8 b4b3f70f 88f21008 0000000c e1b3fb08 portcls!PcHandlePropertyWithTable+0x1b
b4367b00 b4b3274d 88f3eaa0 8a333030 88f21008 portcls!CPortPinWaveCyclic::DeviceIoControl+0x1e5
b4367b1c b7c57f1f 8a333030 88f21008 b4367b44 portcls!DispatchDeviceIoControl+0x49
b4367b2c b4b328c0 8a333030 88f21008 8a3330e8 ks!KsDispatchIrp+0x126
b4367b44 b4b32881 8a333030 88f21008 b4367b78 portcls!KsoDispatchIrp+0x43
b4367b54 b511f121 8a333030 88f21008 00000000 portcls!PcDispatchIrp+0x5f
b4367b78 804ef19f 8a333030 00000010 88f21008 RtkHDAud+0x5d9121
b4367b88 b4344774 e12a0928 00000000 88f21008 nt!IopfCallDriver+0x31
b4367bd8 b43472a2 88f21008 00000000 e37bc1e8 sysaudio!ForwardIrpNode+0x1b2
b4367c30 b7c57f95 891ba030 88f21008 b4367c64 sysaudio!CPinInstance::PinDispatchIoControl+0x153
b4367c40 804ef19f 891ba030 88f21008 806e7410 ks!DispatchDeviceIoControl+0x28
b4367c50 8057f98e 88f21150 89271028 88f21008 nt!IopfCallDriver+0x31
b4367c64 8058081d 891ba030 88f21008 89271028 nt!IopSynchronousServiceTail+0x70
b4367d00 80579298 00000254 000003d8 00000000 nt!IopXxxControlFile+0x5c5
b4367d34 8054167c 00000254 000003d8 00000000 nt!NtDeviceIoControlFile+0x2a
b4367d34 7c90e514 00000254 000003d8 00000000 nt!KiFastCallEntry+0xfc
4caffe5c 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
RtkHDAud+6be6d
b4bb1e6d ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: RtkHDAud+6be6d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME: RtkHDAud.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ee7282d

FAILURE_BUCKET_ID: 0x8E_RtkHDAud+6be6d

BUCKET_ID: 0x8E_RtkHDAud+6be6d

Followup: MachineOwner

-- 09 lut 2012, 11:05 --

Ponad 3 miesiące się już z blue screenami męczę, kolejny:


WRITE_ADDRESS: 8afc21e8

CURRENT_IRQL: 2

FAULTING_IP:
hal!KfReleaseSpinLock+4
806e7904 c60100 mov byte ptr [ecx],0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: javaw.exe

LAST_CONTROL_TRANSFER: from b39b9296 to 806e7904

STACK_TEXT:
b29c9974 b39b9296 b29c9a14 8912a648 88fc20e8 hal!KfReleaseSpinLock+0x4
b29c9990 b39b4835 02fc200c b29c99cc 88fab9a0 portcls!CPortPinWaveCyclic::GetPosition+0xbc
b29c99b4 b39b92c1 0012a578 b29c99cc 88fc2008 portcls!CIrpStream::GetPosition+0x5a
b29c9a14 b39b93c8 88fc2008 89656718 0000000c portcls!CPortPinWaveCyclic::GetKsAudioPosition+0x1d
b29c9a2c b7c57ea8 88fab9a0 89656728 89656718 portcls!CPortPinWaveCyclic::GetKsAudioPosition+0x124
b29c9a90 b7c57ed9 88fab9a0 0000000c e19259b8 ks!KspPropertyHandler+0x602
b29c9ab4 b39c26a9 88fab9a0 0000000c e1925990 ks!KsPropertyHandler+0x19
b29c9ac8 b39cf70f 88fab9a0 0000000c e1925990 portcls!PcHandlePropertyWithTable+0x1b
b29c9b00 b39c274d 88fc2008 8a3c6e18 88fab9a0 portcls!CPortPinWaveCyclic::DeviceIoControl+0x1e5
b29c9b1c b7c57f1f 8a3c6e18 88fab9a0 b29c9b44 portcls!DispatchDeviceIoControl+0x49
b29c9b2c b39c28c0 8a3c6e18 88fab9a0 8a3c6ed0 ks!KsDispatchIrp+0x126
b29c9b44 b39c2881 8a3c6e18 88fab9a0 b29c9b78 portcls!KsoDispatchIrp+0x43
b29c9b54 b3faf121 8a3c6e18 88fab9a0 00000000 portcls!PcDispatchIrp+0x5f
WARNING: Stack unwind information not available. Following frames may be wrong.
b29c9b78 804ef19f 8a3c6e18 00000010 88fab9a0 RtkHDAud+0x5d9121
b29c9b88 b376f774 e112f328 00000000 88fab9a0 nt!IopfCallDriver+0x31
b29c9bd8 b37722a2 88fab9a0 00000000 e11b66a0 sysaudio!ForwardIrpNode+0x1b2
b29c9c30 b7c57f95 891c4f08 88fab9a0 b29c9c64 sysaudio!CPinInstance::PinDispatchIoControl+0x153
b29c9c40 804ef19f 891c4f08 88fab9a0 806e7410 ks!DispatchDeviceIoControl+0x28
b29c9c50 8057f98e 88fabae8 8941e8d0 88fab9a0 nt!IopfCallDriver+0x31
b29c9c64 8058081d 891c4f08 88fab9a0 8941e8d0 nt!IopSynchronousServiceTail+0x70
b29c9d00 80579298 00000228 000003ac 00000000 nt!IopXxxControlFile+0x5c5
b29c9d34 8054167c 00000228 000003ac 00000000 nt!NtDeviceIoControlFile+0x2a
b29c9d34 7c90e514 00000228 000003ac 00000000 nt!KiFastCallEntry+0xfc
4d12fe5c 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
portcls!CPortPinWaveCyclic::GetPosition+bc
b39b9296 8b45f8 mov eax,dword ptr [ebp-8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: portcls!CPortPinWaveCyclic::GetPosition+bc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: portcls

IMAGE_NAME: portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025ccc

FAILURE_BUCKET_ID: 0xA_portcls!CPortPinWaveCyclic::GetPosition+bc

BUCKET_ID: 0xA_portcls!CPortPinWaveCyclic::GetPosition+bc

Followup: MachineOwner

-- 09 lut 2012, 14:59 --

Kolejny, dodawać kolejne zrzuty czy nie ma sensu?

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000001
Arg2: 8054e5f0
Arg3: b6000000
Arg4: 00000181

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

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011011000000000000000000000000000000000000000000000000110000001


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

ADDRV - IA32_MCi_ADDR register valid
Indicates that the IA32_MCi_ADDR register contains the address where
the error occurred.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

MEMHIRERR - Memory Hierarchy Error {TT}CACHE{LL}_{RRRR}_ERR
These errors match the format 0000 0001 RRRR TTLL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_ADDRV_PCC_MEMHIRERR_81

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_AuthenticAMD

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: firefox.exe

LAST_CONTROL_TRANSFER: from 806eabfb to 804f9f43

STACK_TEXT:
8054e5c8 806eabfb 0000009c 00000001 8054e5f0 nt!KeBugCheckEx+0x1b
8054e6f4 806e5c52 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
8054e6f4 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0x9C_AuthenticAMD_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

-- 09 lut 2012, 15:17 --

To jest ktoś w stanie coś doradzić? Czytałem coś o rookitach, które po formacie i tak się nie usuwają. Kolejny zrzut:


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: 00441800, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, 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: 80540b21, address which referenced memory

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


WRITE_ADDRESS: 00441800

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KeReleaseQueuedSpinLockFromDpcLevel+15
80540b21 f00fb111 lock cmpxchg dword ptr [ecx],edx

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 80545bdc to 80540b21

STACK_TEXT:
b84d3d44 80545bdc ffffffff 00000286 80545e2d nt!KeReleaseQueuedSpinLockFromDpcLevel+0x15
b84d3d50 80545e2d 00000000 0000000e 00000000 nt!SwapContext+0xcc
b84d3d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x81


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeReleaseQueuedSpinLockFromDpcLevel+15
80540b21 f00fb111 lock cmpxchg dword ptr [ecx],edx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KeReleaseQueuedSpinLockFromDpcLevel+15

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ea6b0e6

FAILURE_BUCKET_ID: 0xA_nt!KeReleaseQueuedSpinLockFromDpcLevel+15

BUCKET_ID: 0xA_nt!KeReleaseQueuedSpinLockFromDpcLevel+15

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

-- 09 lut 2012, 22:56 --

WAŻNE INFORMACJE
Przy próbach instalacji systemów z różnych sprawdzonych płytek(xp, 7, debian. ubuntu, mandriva itp.) każdorazowo wypluwa błędy przy instalacji(albo jeszcze przed) płytki w większości przypadków w stanie idealnym, na laptopie odpalają bez zająknięcia. Programy, sterowniki lub gry z płytek odpalają i instalują się bez problemu, problemy pojawią się dopiero w przypadkach instalacji systemu, screeny:
Dostępne tylko dla zarejestrowanych użytkowników
Dostępne tylko dla zarejestrowanych użytkowników


Jak będzie trzeba mogę wrzucić screeny z błędów przy instalacji innych systemów.

Jeszcze analiza SMART, może się przyda:
HD Tune Pro: SAMSUNG HD501LJ Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 100 100 51 0 ok
(03) Spin Up Time 100 100 15 5312 ok
(04) Start/Stop Count 92 92 0 8467 ok
(05) Reallocated Sector Count 253 253 10 0 ok
(07) Seek Error Rate 253 253 51 0 ok
(08) Seek Time Performance 253 253 15 0 ok
(09) Power On Hours Count 100 100 0 20141 ok
(0A) Spin Retry Count 253 253 51 0 ok
(0B) Calibration Retry Count 253 100 0 0 ok
(0C) Power Cycle Count 96 96 0 4344 ok
(0D) Soft Read Error Rate 100 100 0 2536542 ok
(BB) Reported Uncorrectable Errors 69 69 0 65568 ok
(BC) Command Timeout 99 99 0 173 ok
(BE) Airflow Temperature 60 50 0 40 ok
(C2) Temperature 118 88 0 40 ok
(C3) Hardware ECC Recovered 100 100 0 2536542 ok
(C4) Reallocated Event Count 253 253 0 0 ok
(C5) Current Pending Sector 253 100 0 0 ok
(C6) Offline Uncorrectable 253 253 0 0 ok
(C7) Ultra DMA CRC Error Count 200 200 0 0 ok
(C8) Write Error Rate 100 100 0 0 ok
(C9) Soft Read Error Rate 253 100 0 0 ok
(CA) Data Address Marker errors 253 253 0 0 ok

Health Status : ok

[cosik_ktosik]

Z tego co widzę to do reinstalacji Java oraz sterowniki Realteka od karty dźwiękowej (to zmieniałeś).

Wg SMARTa, dysk jest zdrowy.

[kat666]

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: 00000001, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b7e4088f, address which referenced memory

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


READ_ADDRESS: 00000001

CURRENT_IRQL: 2

FAULTING_IP:
NDIS!ndisPmInitializeMiniport+1d6
b7e4088f 1a00 sbb al,byte ptr [eax]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

MISALIGNED_IP:
NDIS!ndisPmInitializeMiniport+1d6
b7e4088f 1a00 sbb al,byte ptr [eax]

LAST_CONTROL_TRANSFER: from b6ff3061 to b7e4088f

STACK_TEXT:
b84d3ba8 b6ff3061 b84d3bcc 00000001 89bad230 NDIS!ndisPmInitializeMiniport+0x1d6
b84d3bc0 b7e4fc09 890c3780 89bad1e8 b6ff8b40 psched!MpReturnPacket+0x3b
b84d3c14 b6ff301d 007ce748 8a5492d8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x56d
b84d3c28 b6ff31b4 8a546ad0 8a5492d8 00000001 psched!PsFlushReceiveQueue+0x15
b84d3c4c b6ff35f9 890c3788 00000000 8a546ad0 psched!PsEnqueueReceivePacket+0xda
b84d3c64 b7e4fc40 890c3780 805409e0 89d10000 psched!ClReceiveComplete+0x13
b84d3cb4 b820b2e4 007ce748 89d105d4 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 NVENETFD+0x32e4


STACK_COMMAND: kb

FOLLOWUP_IP:
NVENETFD+32e4
b820b2e4 ?? ???

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: NVENETFD+32e4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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


Co tym razem? Komputer resetuje się cały czas.

[djkamil09061991]

IMAGE_NAME: hardware

Dysk był wcześniej sprawdzany i jest ok, może czas sprawdzić ram:
http://www.hotfix.pl/instrukcja-obslugi ... m-a204.htm
Dla pewności możesz sprawdzić napięcia i temperatury, oraz podaj marke i moc zasilacza

[kat666]

Ram jak pisałem wcześniej sprawdzałem i jestem na 100 % sprawny, że to nie jego wina. Sprawdzałem go całą noc memtestem i nic nie znalazł, wyjmowałem także po jednej kości ramu ze slotu i nie pomogło. Jeżeli wspominasz o zasilaczu to myślę, że już znam przyczynę jest nim zasilacz modecom II 400w. Sprzet:
Procesor:Amd 64 6000+
grafika: gf 8600gt 256mb
płyta:gigabyte m56s-s3
dysk twardy: samsung hd501lj 3,5'' 500gb

Dodatkowo czuć od niego spaleniznę, czytałem o tym na necie i podobno to normalne

[djkamil09061991]

zasilacz modecom II 400w

Zasilacz z czarnej listy ;/ tak więc i tak radzę wymienić nawet na jakiegoś fortona czy chiefteca którego można za małe pieniądze kupić na allegro.Bo szkoda byłoby gdyby spalił ci jakiś podzespół.

Dodatkowo czuć od niego spaleniznę, czytałem o tym na necie i podobno to normalne

lol no niewiem czy zapach spalenizny z zasilacza to taka normalna sprawa

Pobierz dla pewności program HWMonitor i pokaż z niego ss, bedą tam napięcia itp itd

[kat666]

Dostępne tylko dla zarejestrowanych użytkowników

[djkamil09061991]

Złe napięcie na linii 5V. Tak więc sprawdziłbym jak komputer zachowywałby się na innym zasilaczu.

[kat666]

A da się napięcie bezpiecznie skonfigurować na tym zasilaczu aby sprawdzić czy to faktyczna przyczyna problemu? Wymianę zasilacza i tak planowałem, ale sprawdzić nie zaszkodzi.

[djkamil09061991]

A da się napięcie bezpiecznie skonfigurować na tym zasilaczu aby sprawdzić czy to faktyczna przyczyna problemu?

Nie. Jedynie co możesz zrobić to pożyczyć od kogoś zasilacz i sprawdzić. A zasilacz i tak zmienić warto choćby gdybyś chciał w przyszłości zmodernizować komputer