• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Bad Driver Finder?

eits

eits

Lifer
lately, i've been getting a lot of bsod whenever my computer comes out of hibernate mode.

i get "irql_not_less_or_equal," "driver_not_less_or_equal," and "memory_management"

i just built the system a couple weeks ago. i've tried repairing, but there was nothing wrong with the windows install. i haven't downloaded anything suspect or anything.

i've run memtest before and came up with nothing, but that was only after about 2 hrs. i'm running memtest now and i'm gonna check it tonight.

i'm worried it might be a psu issue, but i really hope it isn't. i hope it isn't because i don't wanna deal with sending yet ANOTHER thing back to newegg and getting a new product. it's a raidmax psu.

so, i'm hoping it's a driver issue. i want to know if there's anything that can show me which driver is bad. if not, is there a program that can show me the list of drivers and uninstall options?
 
Looks like you posted this over in OS's too, prolly should stick to one post...

Anyway could you please provide the specs of the pc? I'm sure that will help a bit. I'm guessing it's a driver error but we'll need more info.
 
Originally posted by: mc866
could you please provide the specs of the pc? I'm sure that will help a bit. I'm guessing it's a driver error but we'll need more info.
Click to expand...

e8400
4gb (4x1gb) ddr2 corsair xms
evga gtx 260
gigabyte ep45-ud3r
raidmax hybrid 2 rx-530ss 530w atx 12v v2.2/ eps 12v
wd 640gb hdd <--- primary, windows vista installed
2x wd 250gb hdd <--- both empty, only for backup
 
i reformatted and i hadn't had problems until a little bit ago. i bsod'ed, then rebooted, and bsod'ed again.

for some reason, i can't open the first minidump bsod file on the windows debugger tool, but i can do the second one.

here it is...

Loading Dump File [C:\Windows\Minidump\Mini011809-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16754.x86fre.vista_gdr.080917-1612
Machine Name:
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Sun Jan 18 19:48:28.641 2009 (GMT-6)
System Uptime: 0 days 0:00:41.485
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {f9ec84, 2, 0, 8a89f8ba}

Probably caused by : ecache.sys ( ecache!EcBlockFind+5e )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00f9ec84, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8a89f8ba, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
00f9ec84

CURRENT_IRQL: 2

FAULTING_IP:
ecache!EcBlockFind+5e
8a89f8ba 8b5004 mov edx,dword ptr [eax+4]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 8b647ac8 -- (.trap 0xffffffff8b647ac8)
ErrCode = 00000000
eax=00f9ec80 ebx=00000029 ecx=29747d68 edx=00003e69 esi=ffffffff edi=8a8af360
eip=8a89f8ba esp=8b647b3c ebp=8b647b50 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ecache!EcBlockFind+0x5e:
8a89f8ba 8b5004 mov edx,dword ptr [eax+4] ds:0023:00f9ec84=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8a89f8ba to 81c8fdc4

STACK_TEXT:
8b647ac8 8a89f8ba badb0d00 00003e69 8b647b38 nt!KiTrap0E+0x2ac
8b647b50 8a8a4a4c 8a8af360 85934758 29747d68 ecache!EcBlockFind+0x5e
8b647be0 8a8a66d3 8a8af360 8b647c98 8b647c74 ecache!EcCacheManagerStartDeviceIo+0x400
8b647ca8 81c27f9b 859346a0 86a60b58 86a60cc4 ecache!EcDispatchReadWrite+0xbcf
8b647cc0 81cb07e7 8a8dc32c 00000000 00000000 nt!IofCallDriver+0x63
8b647cc4 8a8dc32c 00000000 00000000 85983cd8 nt!IoCallDriverStackSafe+0x5
8b647ce0 8a8dd98b 86a60b58 859346a0 00000004 volsnap!VspAsynchronousIo+0x110
8b647d4c 8a8d7c01 00d4e968 86d4e9a0 00000000 volsnap!VspWriteVolumePhase25+0x2a1
8b647d60 8a8d73ac 86d4e968 00000000 84dcd828 volsnap!VspWriteVolumePhase22+0x1d
8b647d7c 81e25556 84de6d68 8b64c680 00000000 volsnap!VspWorkerThread+0x82
8b647dc0 81c915fe 8a8d732a 8596e150 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
ecache!EcBlockFind+5e
8a89f8ba 8b5004 mov edx,dword ptr [eax+4]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ecache!EcBlockFind+5e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ecache

IMAGE_NAME: ecache.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4549b1da

FAILURE_BUCKET_ID: 0xD1_ecache!EcBlockFind+5e

BUCKET_ID: 0xD1_ecache!EcBlockFind+5e

Followup: MachineOwner
---------
Click to expand...
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top