Bugcheck code: 0x1000008E

Hello :)

Bugcheck code: 0x1000008E


thanks for all

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\r2u\Windows_NT6_BSOD_jcgriff2\011412-30186-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x83446000 PsLoadedModuleList = 0x83586230
Debug session time: Sat Jan 14 12:04:16.240 2012 (UTC - 7:00)
System Uptime: 0 days 4:40:30.003
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 834ba4ef, 80e4c2c0, 0}

Probably caused by : cng.sys ( cng!GatherRandomKey+272 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 834ba4ef, The address that the exception occurred at
Arg3: 80e4c2c0, Trap Frame
Arg4: 00000000

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!ObReferenceObjectSafe+3
834ba4ef 8b0a            mov     ecx,dword ptr [edx]

TRAP_FRAME:  80e4c2c0 -- (.trap 0xffffffff80e4c2c0)
ErrCode = 00000000
eax=85b87700 ebx=86ef4cd0 ecx=00000000 edx=7e267898 esi=854a9d48 edi=7e267b18
eip=834ba4ef esp=80e4c334 ebp=80e4c354 iopl=0         nv up ei pl nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010203
nt!ObReferenceObjectSafe+0x3:
834ba4ef 8b0a            mov     ecx,dword ptr [edx]  ds:0023:7e267898=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 836abe05 to 834ba4ef

STACK_TEXT:  
80e4c330 836abe05 c14bb6d8 80e4c378 c14bb420 nt!ObReferenceObjectSafe+0x3
80e4c354 83632991 85b877a8 80e4c378 8365659e nt!PsGetNextProcessThread+0x65
80e4c360 8365659e a2beb7ba 00000000 0001ff68 nt!ExpGetNextProcessThread+0x11
80e4c3fc 8363f8a8 c14b8098 0001ff68 80e4c844 nt!ExpGetProcessInformation+0x18b
80e4c874 8363e873 00000005 00000000 00000000 nt!ExpQuerySystemInformation+0x102c
80e4c890 8347b85a 00000005 c14b8098 0001ff68 nt!NtQuerySystemInformation+0x76
80e4c890 8347a22d 00000005 c14b8098 0001ff68 nt!KiFastCallEntry+0x12a
80e4c918 89dcafdf 00000005 c14b8098 0001ff68 nt!ZwQuerySystemInformation+0x11
80e4cc78 89da815e 00000000 00000000 80e4cc98 cng!GatherRandomKey+0x272
80e4ccdc 89da81bf 00000000 80e4cd00 83633694 cng!ReadExternalEntropyIntoPool+0x1a6
80e4cce8 83633694 85df1948 00000000 85cd3378 cng!scavengingWorkItemRoutine+0x15
80e4cd00 834a1173 85cd3378 00000000 854a9d48 nt!IopProcessWorkItem+0x2d
80e4cd50 8362e46a 00000001 a2beb9d6 00000000 nt!ExpWorkerThread+0x10d
80e4cd90 834cf989 834a1066 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cng!GatherRandomKey+272
89dcafdf 83fb20          cmp     ebx,20h

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  cng!GatherRandomKey+272

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec48143

FAILURE_BUCKET_ID:  0x8E_cng!GatherRandomKey+272

BUCKET_ID:  0x8E_cng!GatherRandomKey+272

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

You had a KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (start each one an hour before bed so you can check that they are still running before going to sleep).

Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs.

Also, recommend updating Rtnicxp.sys

Code:

Rtnicxp	91e93000	91ea4000	Sun Mar 30 23:41:05 2008 (47f07971)	0001c10b		Rtnicxp.sys

Also, recommend updating Rtnicxp.sys<============ what is this ?

r2u said:

Also, recommend updating Rtnicxp.sys<============ what is this ?

If you click on the link (links are shown in blue), more information is provided via Rtnicxp.sys. Also, Google is your friend. Realtek 10/100/1000 NDIS 5.1 Driver is a network adapter driver (probably for Ethernet). http://www.google.com/search?aq=f&so...&q=Rtnicxp.sys

http://www.realtek.com/downloads/dow...&GetDown=false may also be of interest. Download the Win7 version.

Did updating your Realtek driver help?