Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: anyone help..

14 Sep 2010   #1
donpower

windows 7 Professional x86
 
 
anyone help..

i often face the bluescreen....

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1057

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 8D186282
BCP3: 8F26FBC0
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\091410-34507-01.dmp
C:\Users\DONNI\AppData\Local\Temp\WER-94599-0.sysdata.xml


My System SpecsSystem Spec
.
14 Sep 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by donpower View Post
i often face the bluescreen....

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1057

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 8D186282
BCP3: 8F26FBC0
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\091410-34507-01.dmp
C:\Users\DONNI\AppData\Local\Temp\WER-94599-0.sysdata.xml


Ok where to start. This crash was caused by two things. First your EagleNT file, and drivers that are from 1996, 2003, 2006, etc. There is no way that you are going to become stable untill you remove the Hackershield/EAgleNT and update the drivers.

How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\091410-34507-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x83449000 PsLoadedModuleList = 0x83591810
Debug session time: Tue Sep 14 05:39:25.304 2010 (GMT-4)
System Uptime: 0 days 4:47:28.317
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
...........................
Unable to load image \??\C:\Windows\system32\drivers\EagleNT.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for EagleNT.sys
*** ERROR: Module load completed but symbols could not be loaded for EagleNT.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8d186282, 8f26fbc0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : EagleNT.sys ( EagleNT+4282 )

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: 8d186282, The address that the exception occurred at
Arg3: 8f26fbc0, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: EagleNT

FAULTING_MODULE: 83449000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c4ffd00

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

FAULTING_IP: 
EagleNT+4282
8d186282 3b4208          cmp     eax,dword ptr [edx+8]

TRAP_FRAME:  8f26fbc0 -- (.trap 0xffffffff8f26fbc0)
ErrCode = 00000000
eax=000003c4 ebx=836a6510 ecx=00000000 edx=00000000 esi=030cfee4 edi=00000304
eip=8d186282 esp=8f26fc34 ebp=8f26fc40 iopl=0         nv up ei pl nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010203
EagleNT+0x4282:
8d186282 3b4208          cmp     eax,dword ptr [edx+8] ds:0023:00000008=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8d186547 to 8d186282

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8f26fc40 8d186547 8d1a4d20 000003c4 004b0549 EagleNT+0x4282
8f26fc58 8d18d30c 8d1a4d20 000003c4 00000084 EagleNT+0x4547
8f26fcd0 836a653a 00000304 0000055c 00000000 EagleNT+0xb30c
8f26fd04 8348c44a 00000304 0000055c 00000000 nt!NtDeviceIoControlFile+0x2a
8f26fd34 779664f4 badb0d00 030cfebc 00000000 nt!ZwYieldExecution+0xb56
8f26fd38 badb0d00 030cfebc 00000000 00000000 0x779664f4
8f26fd3c 030cfebc 00000000 00000000 00000000 0xbadb0d00
8f26fd40 00000000 00000000 00000000 00000000 0x30cfebc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
EagleNT+4282
8d186282 3b4208          cmp     eax,dword ptr [edx+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  EagleNT+4282

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  EagleNT.sys

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------
Really Old Drivers
Code:
giveio.sys        0x8bbef000    0x8bbef680    0x00000680    0x316334f5    4/3/1996 22:33:25                        
hwinterface.sys        0x90942000    0x90942a40    0x00000a40    0x3f1d662b    7/22/2003 12:28:27                                                
al8wa38w.SYS        0x9218a000    0x921d4000    0x0004a000    0x45084f29    9/13/2006 14:34:17                        
speedfan.sys        0x8bbd5000    0x8bbd6480    0x00001480    0x4516880f    9/24/2006 09:28:47                        
tshd4_kern_i386.sys        0x91a7c000    0x91a87800    0x0000b800    0x46a8cae0    7/26/2007 12:25:04                        
wowhd_kern_i386.sys        0x91e00000    0x91e07d00    0x00007d00    0x46a8cae2    7/26/2007 12:25:06                        
csiidecoder_kern_i386.sys        0x91e08000    0x91e12480    0x0000a480    0x46a8cae2    7/26/2007 12:25:06                        
surroundhp_kern_i386.sys        0x91e13000    0x91e1e900    0x0000b900    0x46a8cae2    7/26/2007 12:25:06                        
srs_sscfilter_i386.sys        0x921f5000    0x921feb80    0x00009b80    0x46a8cae8    7/26/2007 12:25:12                        
Apfiltr.sys        0x9214d000    0x92179000    0x0002c000    0x47a1d7c7    1/31/2008 10:14:31                        
PxHelp20.sys        0x8b578000    0x8b581200    0x00009200    0x47d88a18    3/12/2008 21:57:44                        
LVUSBSta.sys        0xaf1e1000    0xaf1e9900    0x00008900    0x488b3bd8    7/26/2008 10:59:36                        
adfs.SYS        0xaf172000    0xaf182e80    0x00010e80    0x48a447cb    8/14/2008 10:57:15                        
AGRSM.sys        0x97ea5000    0x97fab000    0x00106000    0x49184ba5    11/10/2008 10:56:37                        
CT_ZTEMT_U_USBSER.sys        0xaf1c7000    0xaf1e0880    0x00019880    0x492b60ad    11/24/2008 22:19:25                        
Rt86win7.sys        0x92099000    0x920be000    0x00025000    0x49a65b16    2/26/2009 05:04:22                        
spldr.sys        0x8bbcd000    0x8bbd5000    0x00008000    0x4a084ebb    5/11/2009 12:13:47
My System SpecsSystem Spec
26 Jan 2011   #3
donpower

windows 7 Professional x86
 
 

Thanks 4 the help!
I already change my windows into 64bit.. Cuz my RAM 4 GB so it's useless if i still use 32bit
My System SpecsSystem Spec
.

Reply

 anyone help..




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 20:00.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App