waaa BSOD

[killingZ]

hi i having problems on my computer recently when i turn on my computer,My OS is windows 7 ultimate x86
here is the information about this error:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 13321

Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 89DFB32C
BCP3: 80FB6AEC
BCP4: 80FB66D0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

I hope that u can help me

here is the Windows_NT6_BSOD_jcgriff2 file:

 

[Lemur]

Welcome to SF.

First please complete your System Specs more completely:

HOW TO FILL OUT YOUR SYSTEM SPECS

In the line at the top of “www.SevenForums.com” you will see UserCP.
That is an abbreviation for User Control Panel.
Click on UserCP.
In the left-hand column, under Your Profile you will see Edit System Spec.
Click on Edit System Spec
You can copy and paste from the output of Speccy, Speccy - System Information - Free Download to fill out much of the info. Be sure to use the Other Info section of your System Specs for such info as your optical drive, your wireless adapter, your speakers, etc.


Next do the following:

BSOD Posting Instructions

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

**EDIT**

BugCheck 1000007E, {c0000005, 89dfb32c, 80fb6aec, 80fb66d0}

Probably caused by : rdyboost.sys ( rdyboost!SmdRBReadWriteCompletion+c )

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

0: kd> !analyze -v;r;kv;lmtn;lmtsmn
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 89dfb32c, The address that the exception occurred at
Arg3: 80fb6aec, Exception Record Address
Arg4: 80fb66d0, Context Record Address

 

[killingZ]

ok thanks i will update my profile and my post above there..

 

[killingZ]

sir ive been updated my profile and my post above will u please help me now??

 

[killingZ]

...... anyone there??

 

[killingZ]

hello anyone help??

 

[Lemur]

Suspect it may be a driver issue.

Video driver is good.

Please update audio and network drivers:
viahduaa viahduaa.sys Thu May 07 23:23:18 2009

Name: Atheros L2 Fast Ethernet 10/100Base-T Controller
Device ID: PCI\VEN_1969&DEV_2048&SUBSYS_20481019&REV_A0\4&56138DB&0&00E0
Driver: C:\Windows\system32\DRIVERS\l260x86.sys, 2.06.0007.0017 (English), 10/16/2008 23:17:00, 29184 bytes

Also, select "automatically detect drivers" for Intel chipset
Support for the Intel® Chipset Software Installation Utility

Let us know how that goes.

 

[killingZ]

ok thank you!