BSOD once or more times a day - Win 7 Ultimate (x64)

Paul Hatch

New Member
Dear all,

My system has been running smoothly for quite some time now (6+ months) but over the past few weeks it's been suffering from BSOD daily, it appears (to me) to be totally random in terms of what I am using the computer for, some times surfing and others gaming.


Slot1.jpgSlot2.jpgSlot3.jpg
Not sure what else I need to provide but should I be missing anything please let me know and I will do my best to find/update it.

Kind regards

P.View attachment 062911-30170-01.zip
 


Captain Jack

Extraordinary Member
Hello and Welcome!

Seems like the dumps are pointing to Windows Kernel which may not be the problem. I would recommend to run Hardware Diagnostic Hardware Diagnostic | Captain Debugger
Then run SFC /SCANNOW to Repair Windows 7 Files | Captain Debugger to make sure all the system files are intact. Uninstall AVG and replace it with Microsoft Security essentials. Make sure you run the Removal Tool.

Update the following drivers:

Code:
ASACPI.sys   Mon Mar 28 08:00:36 2005
RecFltr.sys  Thu Jan 18 06:53:09 2007
lv302a64.sys Thu May 10 09:51:51 2007
LV302V64.SYS Thu May 10 09:52:39 2007
Follow this guide for assistance How to Update Drivers on Windows 7 | Captain Debugger

Regarding ASACPI.sys download: Link Removed due to 404 Error

Code:
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: fffff8000337e6fc, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObReferenceObjectByHandleWithTag+8c
fffff800`0337e6fc ff66ff          jmp     qword ptr [rsi-1]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b8100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  ServiceManager

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030d45d8 to fffff80003088d00

STACK_TEXT:  
fffff880`0a6cf418 fffff800`030d45d8 : 00000000`0000001e ffffffff`c0000005 fffff800`0337e6fc 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a6cf420 fffff800`03088382 : fffff880`0a6cfbf8 fffff880`0a6cff50 fffff880`0a6cfca0 fffff8a0`00001700 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0a6cfac0 fffff800`03086c8a : 00000000`0a6c0000 fffff880`00000014 fffff880`0a6cfe00 00000000`00000801 : nt!KiExceptionDispatch+0xc2
fffff880`0a6cfca0 fffff800`0337e6fc : fffff880`0a6cfe98 fffff880`0a6cfe5b fffff880`0a6cfe68 00000000`00000004 : nt!KiGeneralProtectionFault+0x10a
fffff880`0a6cfe30 fffff800`033958c1 : fffff8a0`1416b700 fffff8a0`00000001 fffffa80`0523d080 00000000`00000000 : nt!ObReferenceObjectByHandleWithTag+0x8c
fffff880`0a6cff00 fffff800`03087f93 : fffffa80`099d6740 fffff880`0a6d00a0 fffffa80`0520b040 fffff8a0`14637060 : nt!NtAlpcSendWaitReceivePort+0x71
fffff880`0a6cffb0 fffff800`03084530 : fffff880`0107e625 fffff8a0`10b07000 00000000`00000000 fffff8a0`11fb8300 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a6d01b8 fffff880`0107e625 : fffff8a0`10b07000 00000000`00000000 fffff8a0`11fb8300 fffff880`0107e8e2 : nt!KiServiceLinkage
fffff880`0a6d01c0 fffff880`0107e7c5 : fffff8a0`020d6000 00000000`00000001 fffff8a0`12c41820 fffff880`0108ce12 : msrpc!LRPC_BASE_CCALL::AlpcSend+0x35
fffff880`0a6d0210 fffff880`0107e736 : fffff8a0`01f41130 fffff8a0`128fbbf8 fffff8a0`01f41130 fffff880`01079480 : msrpc!LRPC_BASE_CCALL::DoAsyncSend+0x65
fffff880`0a6d02d0 fffff880`0107ec93 : fffff8a0`128fba10 00000000`00000001 00000000`00000001 fffff8a0`128fba60 : msrpc!LRPC_FAST_CCALL::AsyncSend+0x46
fffff880`0a6d0300 fffff880`01062ee0 : 00000000`00000000 fffff8a0`00000000 00000000`00000001 fffff8a0`128fba60 : msrpc!NdrSend+0x93
fffff880`0a6d0360 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msrpc!Ndr64AsyncClientCall+0x240


STACK_COMMAND:  kb

FOLLOWUP_IP: 
msrpc!LRPC_BASE_CCALL::AlpcSend+35
fffff880`0107e625 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  msrpc!LRPC_BASE_CCALL::AlpcSend+35

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: msrpc

IMAGE_NAME:  msrpc.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79334

FAILURE_BUCKET_ID:  X64_0x1E_msrpc!LRPC_BASE_CCALL::AlpcSend+35

BUCKET_ID:  X64_0x1E_msrpc!LRPC_BASE_CCALL::AlpcSend+35

Followup: MachineOwner
 


Paul Hatch

New Member
View attachment 100611-47689-01.dmp

Thanks for the help all those months ago! the problem went away for a while but then a couple of days ago this happened (memory stats are the same as in my first post)

Kind regards

Paul
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top