BSOD

D

der_kannichen

Junior Member
Joined
Apr 8, 2011
Messages
92
Reaction score
7
Hi all,

I have been getting BSOD frequently on my 4-year windows 7 PC.
Just today, the PC began to have clicking sounds on top of the BSOD.

Going through previous threads I have ran the dump file on http://www.osronline.com. The most recent dump report can be found below:

*******************************************************************************
* *
* 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: 0000000000000010, 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: fffff80003304ec2, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350e100
GetUlongFromAddress: unable to read from fffff8000350e1c8
0000000000000010 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`03304ec2 48890a mov qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: NvStreamNetwor

TRAP_FRAME: fffff8800a646520 -- (.trap 0xfffff8800a646520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800a6467a8
rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003304ec2 rsp=fffff8800a6466b0 rbp=0000000000000000
r8=fffff8800a6467a8 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`03304ec2 48890a mov qword ptr [rdx],rcx ds:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032d23a9 to fffff800032d2e00

STACK_TEXT:
fffff880`0a6463d8 fffff800`032d23a9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a6463e0 fffff800`032d1020 : 00000000`00000010 fffff880`03a2b393 00000000`00000010 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0a646520 fffff800`03304ec2 : fffffa80`09f3ab60 fffffa80`099a6c80 fffffa80`0699bfd0 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0a6466b0 fffff800`032dcebd : 00000000`00000000 fffff880`00000000 fffffa80`06704640 00000000`00000001 : nt!KxWaitForLockOwnerShip+0x12
fffff880`0a6466e0 fffff880`03a497e8 : 00000000`00000000 00000000`00000000 fffffa80`099a6dd0 fffffa80`099a6dd0 : nt!KeAcquireInStackQueuedSpinLock+0x8d
fffff880`0a646730 fffff880`03a49f39 : fffffa80`09fc7010 fffffa80`09fc7200 fffffa80`0699bf00 fffffa80`00000000 : afd!AfdPoll64+0x587
fffff880`0a646820 fffff800`035e1e4a : 00000000`00000002 00000000`00000000 fffffa80`099a6ea0 fffffa80`09fc7010 : afd!AfdPoll+0x29
fffff880`0a646850 fffff800`035f635c : fffffa80`099a6ea0 00000000`00000030 fffffa80`099a6ea0 fffff880`009ed180 : nt!IopSynchronousServiceTail+0xfa
fffff880`0a6468c0 fffff800`035f63f6 : fffff880`0a646ab8 00000000`00000784 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xc49
fffff880`0a646a00 fffff800`032d2093 : fffff880`0a646b60 fffffa80`099a8870 fffff880`0a646ab8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0a646a70 00000000`7793bdaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`045ff578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7793bdaa


STACK_COMMAND: kb

FOLLOWUP_IP:
afd!AfdPoll64+587
fffff880`03a497e8 488b442440 mov rax,qword ptr [rsp+40h]

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: afd!AfdPoll64+587

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: afd

IMAGE_NAME: afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 58e3b35c

FAILURE_BUCKET_ID: X64_0xA_afd!AfdPoll64+587

BUCKET_ID: X64_0xA_afd!AfdPoll64+587

Followup: MachineOwner


-----------------

I really wish to just troubleshoot/repair some parts if possible in order to save costs. Could anyone help on this?

It'd be great if I could have some preventive tips here too. Thank you!
 
tmfwy

tmfwy

Supremacy Member
Joined
Jun 3, 2000
Messages
7,448
Reaction score
6
der_kannichen said:
Hi all,

I have been getting BSOD frequently on my 4-year windows 7 PC.
Just today, the PC began to have clicking sounds on top of the BSOD.

Going through previous threads I have ran the dump file on http://www.osronline.com. The most recent dump report can be found below:

*******************************************************************************
* *
* 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: 0000000000000010, 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: fffff80003304ec2, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350e100
GetUlongFromAddress: unable to read from fffff8000350e1c8
0000000000000010 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`03304ec2 48890a mov qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: NvStreamNetwor

TRAP_FRAME: fffff8800a646520 -- (.trap 0xfffff8800a646520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800a6467a8
rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003304ec2 rsp=fffff8800a6466b0 rbp=0000000000000000
r8=fffff8800a6467a8 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`03304ec2 48890a mov qword ptr [rdx],rcx ds:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032d23a9 to fffff800032d2e00

STACK_TEXT:
fffff880`0a6463d8 fffff800`032d23a9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a6463e0 fffff800`032d1020 : 00000000`00000010 fffff880`03a2b393 00000000`00000010 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0a646520 fffff800`03304ec2 : fffffa80`09f3ab60 fffffa80`099a6c80 fffffa80`0699bfd0 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0a6466b0 fffff800`032dcebd : 00000000`00000000 fffff880`00000000 fffffa80`06704640 00000000`00000001 : nt!KxWaitForLockOwnerShip+0x12
fffff880`0a6466e0 fffff880`03a497e8 : 00000000`00000000 00000000`00000000 fffffa80`099a6dd0 fffffa80`099a6dd0 : nt!KeAcquireInStackQueuedSpinLock+0x8d
fffff880`0a646730 fffff880`03a49f39 : fffffa80`09fc7010 fffffa80`09fc7200 fffffa80`0699bf00 fffffa80`00000000 : afd!AfdPoll64+0x587
fffff880`0a646820 fffff800`035e1e4a : 00000000`00000002 00000000`00000000 fffffa80`099a6ea0 fffffa80`09fc7010 : afd!AfdPoll+0x29
fffff880`0a646850 fffff800`035f635c : fffffa80`099a6ea0 00000000`00000030 fffffa80`099a6ea0 fffff880`009ed180 : nt!IopSynchronousServiceTail+0xfa
fffff880`0a6468c0 fffff800`035f63f6 : fffff880`0a646ab8 00000000`00000784 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xc49
fffff880`0a646a00 fffff800`032d2093 : fffff880`0a646b60 fffffa80`099a8870 fffff880`0a646ab8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0a646a70 00000000`7793bdaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`045ff578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7793bdaa


STACK_COMMAND: kb

FOLLOWUP_IP:
afd!AfdPoll64+587
fffff880`03a497e8 488b442440 mov rax,qword ptr [rsp+40h]

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: afd!AfdPoll64+587

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: afd

IMAGE_NAME: afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 58e3b35c

FAILURE_BUCKET_ID: X64_0xA_afd!AfdPoll64+587

BUCKET_ID: X64_0xA_afd!AfdPoll64+587

Followup: MachineOwner


-----------------

I really wish to just troubleshoot/repair some parts if possible in order to save costs. Could anyone help on this?

It'd be great if I could have some preventive tips here too. Thank you!
Click to expand...
Clicking sound most probably indicated Hard Drive failure

Change to new Hard Drive or Solid State Drive and reinstall Windows ( whichever version )
Reseat Rams
 
it_geek

it_geek

Master Member
Joined
Feb 12, 2017
Messages
3,391
Reaction score
760
clicking hard drive is a sign of platter failure.


Extract the drive and prep it for backup not ASAP, but NAO!!!!


If you just changed the hard drive RMA it, if it does not change the problem try a different power socket or SATA cable
 
You must log in or register to reply here.
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top