STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
This means the BSOD's are hard ware or hardware related problem. Note that Code A mentions virus scanner as a possible cause. The code A dump points to rdbss.sys as the cause. However, this is unlikely as this is a Microsoft driver.
I find you still have some obsolete drivers; the ones in red font are very out of date. Update these drivers as ZigZag recommended. Simply unplugging a device will not remove the drivers.
atksgt.sys Sun May 10 10:50:58 2009
dadder.sys Thu Aug 02 05:32:24 2007
lirsgt.sys Sat Mar 07 10:17:27 2009
ov519cmd.sys Thu Aug 29 20:09:39 2002
ov519vid.sys Tue Feb 25 18:05:52 2003
Rt86win7.sys Thu Feb 26 04:04:22 2009
I would also suggest that your follow his advice to uninstall Eset antivirus. Troubleshooting is process of elimination. You want to eliminate all possible causes. Once you get your system running smoothly, you can try Eset again and see what happens. It has caused BSOD's on some Win 7 systems. Use this tool to uninstall it > Info > Tool
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\Downloads\A-Rar\Windows7_BSOD_jcgriff2\080110-29906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82c05000 PsLoadedModuleList = 0x82d44570
Debug session time: Sun Aug 1 11:28:29.817 2010 (GMT-4)
System Uptime: 0 days 7:12:21.833
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, 82c73486}
Probably caused by : rdbss.sys ( rdbss!RxConstructLogicalView+71 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82c73486, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d64700
Unable to read MiSystemVaType memory at 82d440c0
00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeReleaseSemaphore+44
82c73486 f00fba2807 lock bts dword ptr [eax],7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: 9f6e45a4 -- (.trap 0xffffffff9f6e45a4)
ErrCode = 00000002
eax=00000000 ebx=82d26d20 ecx=866f0302 edx=00000000 esi=00000000 edi=00000000
eip=82c73486 esp=9f6e4618 ebp=9f6e4628 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KeReleaseSemaphore+0x44:
82c73486 f00fba2807 lock bts dword ptr [eax],7 ds:0023:00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82c73486 to 82c3db7b
STACK_TEXT:
9f6e45a4 82c73486 badb0d00 00000000 82c59d83 nt!KiTrap0E+0x2cf
9f6e4628 82c5d175 00000000 00000000 00000001 nt!KeReleaseSemaphore+0x44
9f6e4670 82c5cffe 85e32d48 930635d3 930557b8 nt!ExpReleaseResourceForThreadLite+0x171
9f6e4678 930635d3 930557b8 93052000 00000000 nt!ExReleaseResourceLite+0xf
9f6e4694 93065427 866f0020 872428a8 877a67c0 rdbss!RxConstructLogicalView+0x71
9f6e4728 93058725 866f0020 872428a8 9f6e47a8 rdbss!RxFindOrConstructLogicalView+0xbea
9f6e4800 93056e23 872428a8 8580b6c0 9f6e482c rdbss!RxFindOrConstructVirtualNetRoot+0x8f8
9f6e4844 9305a8cd 872428a8 8580b6c0 86b1ffb0 rdbss!RxCanonicalizeNameAndObtainNetRoot+0x2cb
9f6e487c 93041fb1 872428a8 8580b6c0 0c6b6e6a rdbss!RxCommonCreate+0x25b
9f6e4904 9305ce2b 93052240 8580b6c0 86b1ff80 rdbss!RxFsdCommonDispatch+0x646
9f6e4934 9156b298 86b68860 0080b6c0 8580b778 rdbss!RxFsdDispatch+0x1ab
9f6e4950 82c33f44 86b68860 0180b6c0 8580b79c mrxsmb!MRxSmbFsdDispatch+0x9a
9f6e4968 8d221bb0 00000103 856bebe8 86b1ff80 nt!IofCallDriver+0x63
9f6e4984 8d220b52 856bebe8 c0000016 8580b778 mup!MupiCallUncProvider+0x10f
9f6e499c 8d220f5b 856bebe8 124fb97b 00000000 mup!MupStateMachine+0x9b
9f6e49e8 82c33f44 86416a70 8580b6c0 8580b6c0 mup!MupCreate+0x109
9f6e4a00 8ccd920c 8580b6c0 00000000 8580b79c nt!IofCallDriver+0x63
9f6e4a24 8ccec8c9 9f6e4a44 864165e0 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
9f6e4a70 82c33f44 864165e0 86417008 86b1ffdc fltmgr!FltpCreate+0x2db
9f6e4a88 82e0778d af6a3ea9 9f6e4c30 00000000 nt!IofCallDriver+0x63
9f6e4b60 82e0a968 86416a70 855ea838 8742b678 nt!IopParseDevice+0xed7
9f6e4bdc 82e49332 00000000 9f6e4c30 00000040 nt!ObpLookupObjectName+0x4fa
9f6e4c38 82e04d2e 017aed9c 855ea838 84d0ed01 nt!ObOpenObjectByName+0x159
9f6e4cb4 82e4fcb3 017aee58 00100080 017aed9c nt!IopCreateFile+0x673
9f6e4d00 82c3a79a 017aee58 00100080 017aed9c nt!NtCreateFile+0x34
9f6e4d00 77cf64f4 017aee58 00100080 017aed9c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
017aee00 00000000 00000000 00000000 00000000 0x77cf64f4
STACK_COMMAND: kb
FOLLOWUP_IP:
rdbss!RxConstructLogicalView+71
930635d3 a100200593 mov eax,dword ptr [rdbss!WPP_GLOBAL_Control (93052000)]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: rdbss!RxConstructLogicalView+71
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rdbss
IMAGE_NAME: rdbss.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbfd2
FAILURE_BUCKET_ID: 0xA_rdbss!RxConstructLogicalView+71
BUCKET_ID: 0xA_rdbss!RxConstructLogicalView+71
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\Downloads\A-Rar\Windows7_BSOD_jcgriff2\080210-17968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82c3a000 PsLoadedModuleList = 0x82d79570
Debug session time: Sun Aug 1 18:39:58.704 2010 (GMT-4)
System Uptime: 0 days 5:52:35.705
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 82e80e1a, 80e6bb48, 80e6b720}
Probably caused by : ntkrnlmp.exe ( nt!IopDeleteFileObjectExtension+98 )
Followup: MachineOwner
---------
0: 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: 82e80e1a, The address that the exception occurred at
Arg3: 80e6bb48, Exception Record Address
Arg4: 80e6b720, 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:
nt!IopDeleteFileObjectExtension+98
82e80e1a 8b4014 mov eax,dword ptr [eax+14h]
EXCEPTION_RECORD: 80e6bb48 -- (.exr 0xffffffff80e6bb48)
ExceptionAddress: 82e80e1a (nt!IopDeleteFileObjectExtension+0x00000098)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000015
Attempt to read from address 00000015
CONTEXT: 80e6b720 -- (.cxr 0xffffffff80e6b720)
eax=00000001 ebx=85895f80 ecx=82d9a300 edx=00000000 esi=866a5f78 edi=80e6bc44
eip=82e80e1a esp=80e6bc10 ebp=80e6bc24 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!IopDeleteFileObjectExtension+0x98:
82e80e1a 8b4014 mov eax,dword ptr [eax+14h] ds:0023:00000015=????????
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: 00000015
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d99700
Unable to read MiSystemVaType memory at 82d790c0
00000015
FOLLOWUP_IP:
nt!IopDeleteFileObjectExtension+98
82e80e1a 8b4014 mov eax,dword ptr [eax+14h]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 82e52932 to 82e80e1a
STACK_TEXT:
80e6bc24 82e52932 85895f80 855ea838 85895f68 nt!IopDeleteFileObjectExtension+0x98
80e6bc6c 82e8227f 85895f80 85895f80 85895f68 nt!IopDeleteFile+0x1df
80e6bc84 82c903aa 00000000 8786a690 00000000 nt!ObpRemoveObjectRoutine+0x59
80e6bc98 82c9031a 85895f80 82e5cdc7 858a6008 nt!ObfDereferenceObjectWithTag+0x88
80e6bca0 82e5cdc7 858a6008 858a6030 82d9b680 nt!ObfDereferenceObject+0xd
80e6bccc 82cf54b0 858a6008 00000000 00000000 nt!MiSegmentDelete+0x191
80e6bd28 82c5802a 85611020 00000000 fba0fbe0 nt!MiProcessDereferenceList+0xdb
80e6bd50 82e21d6e 00000000 b0eb91e0 00000000 nt!MiDereferenceSegmentThread+0xc5
80e6bd90 82cc3159 82c57f63 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IopDeleteFileObjectExtension+98
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cac3
STACK_COMMAND: .cxr 0xffffffff80e6b720 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!IopDeleteFileObjectExtension+98
BUCKET_ID: 0x7E_nt!IopDeleteFileObjectExtension+98
Followup: MachineOwner
---------
Update the obsolete drivers or uninstall the hardware or software associated with them. If you need help with this, please ask. Uninstall Eset. Run your system and see what happens. Upload any new BSOD's
so i uninstalled ALL updates and now will try to solve something with windows debugger. btw here is my new files
Quote