Windows 7 - Windows has recovered from an unexpected shutdown

[danakom8110]

Please help, i got problem :
Windows 7 32 bit in leptop HP Pavilion dv6000 after clean install- Windows has recovered from an unexpected shutdown

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

Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 8FEB6BC0
BCP3: 8BFADB10
BCP4: 8BFAD6F0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\010107-22869-01.dmp
C:\Windows\Temp\WER-38563-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

please....please..help me, i have antivirus but no solve

this file minidump

 

[zigzag3143]

Please help, i got problem :
Windows 7 32 bit in leptop HP Pavilion dv6000 after clean install- Windows has recovered from an unexpected shutdown

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

Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 8FEB6BC0
BCP3: 8BFADB10
BCP4: 8BFAD6F0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\010107-22869-01.dmp
C:\Windows\Temp\WER-38563-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

please....please..help me, i have antivirus but no solve

this file minidump

This crash was caused by The HP Expresscard DVB-T Model EC300 DVB-TV Tuner driver. It and several other critical ones are over two years old.

You need to update them before we can do anything else

How To Find Drivers:

- 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

Let us know if you need help

Ken

rimsptsk.sys        0x8ffdc000    0x8fff0000    0x00014000    0x45b5bbe3    1/23/2007 03:40:19                        
rimmptsk.sys        0x8ffcd000    0x8ffdc000    0x0000f000    0x45dfd03d    2/24/2007 01:42:21                        
rixdptsk.sys        0x90227000    0x90278000    0x00051000    0x46012cca    3/21/2007 09:02:02                        
[COLOR=Red][U][I][B]yuanmodbda2.sys    yuanmodbda2.sys+1bc0    0x8feb5000    0x8febce00    0x00007e00    0x461303ab    4/3/2007 21:47:23  [/B][/I][/U][/COLOR]                      
[COLOR=Red]nvlddmkm.sys        0x9102d000    0x91772ea0    0x00745ea0    0x46f1ebb3    9/19/2007 23:40:35   [/COLOR]                     
SynTP.sys        0x8fd28000    0x8fd56680    0x0002e680    0x4790f4e7    1/18/2008 14:50:15                        
VSTCNXT3.SYS        0x82010000    0x820c5000    0x000b5000    0x48f68ad9    10/15/2008 20:29:13                        
VSTAZL3.SYS        0x81eba000    0x81ef7000    0x0003d000    0x48f68b0b    10/15/2008 20:30:03                        
VSTDPV3.SYS        0x81ef7000    0x81ff9000    0x00102000    0x48f68b84    10/15/2008 20:32:04                        
[COLOR=Red]nvm62x32.sys        0x90278000    0x902ccc80    0x00054c80    0x48f8fcf7    10/17/2008 17:00:39[/COLOR]                        
[COLOR=Red]avgtdix.sys        0x8a800000    0x8a818e00    0x00018e00    0x49da06c3    4/6/2009 09:42:27  [/COLOR]                      
spldr.sys        0x8b000000    0x8b008000    0x00008000    0x4a084ebb    5/11/2009 12:13:47                        
GEARAspiWDM.sys        0x8ff63000    0x8ff68280    0x00005280    0x4a1151b5    5/18/2009 08:16:53                        
amdxata.sys        0x8ab91000    0x8ab9a000    0x00009000    0x4a12f30f    5/19/2009 13:57:35                        
athr.sys        0x902cd000    0x903dd000    0x00110000    0x4a2ea444    6/9/2009 14:04:52                        
avgmfx86.sys        0x8fbf2000    0x8fbf7280    0x00005280    0x4a4bc901    7/1/2009 16:37:21                        
avgldx86.sys        0x8fe2d000    0x8fe7d380    0x00050380    0x4a5688ad    7/9/2009 20:17:49

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


Loading Dump File [C:\Users\K\Desktop\010107-22869-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;*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL] ;srv*e:\symbols
*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a14000 PsLoadedModuleList = 0x82b5c810
Debug session time: Mon Jan  1 00:46:43.903 2007 (GMT-4)
System Uptime: 0 days 0:17:40.260
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\Drivers\yuanmodbda2.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for yuanmodbda2.sys
*** ERROR: Module load completed but symbols could not be loaded for yuanmodbda2.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8feb6bc0, 8bfadb10, 8bfad6f0}

Probably caused by : yuanmodbda2.sys ( yuanmodbda2+1bc0 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 8feb6bc0, The address that the exception occurred at
Arg3: 8bfadb10, Exception Record Address
Arg4: 8bfad6f0, Context Record Address

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


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

FAULTING_IP: 
yuanmodbda2+1bc0
8feb6bc0 8b4308          mov     eax,dword ptr [ebx+8]

EXCEPTION_RECORD:  8bfadb10 -- (.exr 0xffffffff8bfadb10)
ExceptionAddress: 8feb6bc0 (yuanmodbda2+0x00001bc0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000018
Attempt to read from address 00000018

CONTEXT:  8bfad6f0 -- (.cxr 0xffffffff8bfad6f0)
eax=8bfadbec ebx=00000010 ecx=00000000 edx=8617f074 esi=85e38ae0 edi=00000000
eip=8feb6bc0 esp=8bfadbd8 ebp=8bfadc04 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
yuanmodbda2+0x1bc0:
8feb6bc0 8b4308          mov     eax,dword ptr [ebx+8] ds:0023:00000018=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000018

READ_ADDRESS: GetPointerFromAddress: unable to read from 82b7c718
Unable to read MiSystemVaType memory at 82b5c160
 00000018 

FOLLOWUP_IP: 
yuanmodbda2+1bc0
8feb6bc0 8b4308          mov     eax,dword ptr [ebx+8]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 8feb9aa0 to 8feb6bc0

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8bfadc04 8feb9aa0 8617f074 84f0b268 8618e2c8 yuanmodbda2+0x1bc0
8bfadc30 8feb72ee 8617f074 8bfadc64 00000006 yuanmodbda2+0x4aa0
8bfadc50 8feb83d3 8617f074 00000401 8bfadc9e yuanmodbda2+0x22ee
8bfadc94 8feb581f 8617f074 86892008 8bfadcd0 yuanmodbda2+0x33d3
8bfadca4 8fedc154 8617f074 86892008 00000004 yuanmodbda2+0x81f
8bfadcd0 8fedbbee 8617f18c 8bfadcf0 8617e970 ks!CKsDevice::DispatchDeviceSetPowerIrp+0x1cf
8bfadcf8 82a1f823 8617f008 86892008 00000000 ks!CKsDevice::DispatchPower+0x211
8bfadd50 82c2266d 870e9478 a4cf8685 00000000 nt!PopIrpWorker+0x351
8bfadd90 82ad40d9 82a1f4d2 870e9478 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  yuanmodbda2+1bc0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: yuanmodbda2

IMAGE_NAME:  yuanmodbda2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  461303ab

STACK_COMMAND:  .cxr 0xffffffff8bfad6f0 ; kb

FAILURE_BUCKET_ID:  0x7E_yuanmodbda2+1bc0

BUCKET_ID:  0x7E_yuanmodbda2+1bc0

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

 

[danakom8110]

Thanks Zigzag3143,

Unfortunely I have googling but I can't found appropriate driver HP Expresscard DVB-T Model EC300 DVB-TV Tuner driver for leptop HP Pavilion dv6000 n windows 7 32 bit...Please help me to find driver ?

 

[Capt.Jack Sparrow]

Thanks Zigzag3143,

Unfortunely I have googling but I can't found appropriate driver HP Expresscard DVB-T Model EC300 DVB-TV Tuner driver for leptop HP Pavilion dv6000 n windows 7 32 bit...Please help me to find driver ?

Hello,

Try these Drivers Microsoft Update Catalog seems like most of the users have the same problem with Yuan EC300 TV Tuner card. Here in this thread few of them have mentioned various link for Drivers Yuan EC300 DVB-T TV Tuner Card Crashes Windows 7 If nothings works the it's best to Disable the Device and remove the Drivers completely.

Hope this helps,
Captain

 

[Fireengineer]

Hello everybody!

Here in this thread few of them have mentioned various link for Drivers Yuan EC300 DVB-T TV Tuner Card Crashes Windows 7

Please go to the bottom of that page to find now an updated driver from Yuan that will solve the problems.

For those who don't have time to read a little bit more, here is the direct link:
https://docs.google.com/open?id=0B76yYQabm16qb1RtWUZ6ZVpOdEE

Regards
Fireengineer