Windows VistaPost your Windows Vista related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
Random Crashes DRIVER_IRQL_NOT_LESS_OR_EQUAL yk60x86.sys
My laptop has been crashing at random with no discernible pattern except that as far as I can remember Firefox has always been open when it crashes, but Firefox is open 90% of the time on my laptop anyway. (and all the crashes have been DRIVER_IRQL_NOT_LESS_OR_EQUAL yk60x86.sys) This has happened about 10 times since I got the laptop back for service (I'll explain this in a bit) Its happened while I'm playing FFXI, Using Visual Studio 2008, while I'm just surfing the web and once when I unplugged the power cord. (that wiped several drivers and I had to re image)
I looked up what yk60x86.sys is, Its a driver for my wired LAN Card a Marvell Yukon 88E8071 PCI-E Gigabit Ethernet Connector which is currently disabled via Device Manager. As far as I remember I have never had a crash while the device has been disabled. about 3 weeks ago I had about 5 crashes in 10 hours, after this I found the latest driver for the Network card and installed it. For 2 weeks I had no crashes, then while at a friends I had the crash that wiped out drivers. I re imaged the computer using the Acer eRecovery partition (therefore I do not have any of the previous dumps) and less than 24 hours later I had another crash.
Now I think a contributing factor may be that 3 months ago I fell down the stairs... with my laptop and cracked the screen. I bought the laptop from Best Buy and accidental damage was covered under the service plan so I had it repaired, while it was going in for service I asked them if they could fix my broken headphone jack which I'm assuming is why the motherboard was replaced (the jack is soldered to the motherboard) after 5 weeks I got it back and returned it the next day due to a dead motherboard. It was sent in for service again and came back 2 weeks later and I had my 1st crash of this type within a month.
Before I got my laptop back from service I had it for 2 months and never had a crash. I think something may have been damaged at the service center (as the right 1/4 of my touch pad has been dead since I got it back too) if this is a hardware problem would uninstalling the driver fix the problem as I cannot take the laptop back in for service until I have a week off school in August? Losing abaility to plug into LAN is not a problem as I've only used that once or twice.
Thank you for your help
This crash was using the driver that came with teh compute from the factory but I've had crashed under the newest version too
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Radical Edward\Desktop\Mini070908-01.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: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Wed Jul 9 13:59:19.545 2008 (GMT-4)
System Uptime: 0 days 0:58:32.414
Loading Kernel Symbols
........................................................................... ........................................................................... ...
Loading User Symbols
Loading unloaded module list
...........
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 0, 89e15b26}
*** ERROR: Module load completed but symbols could not be loaded for yk60x86.sys
Probably caused by : yk60x86.sys ( yk60x86+eb26 )
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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 89e15b26, address which referenced memory
Debugging Details:
------------------
AUTOBUG_OS_SKU: 3
READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
00000000
CURRENT_IRQL: 2
FAULTING_IP:
yk60x86+eb26
89e15b26 f70000000080 test dword ptr [eax],80000000h
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
TRAP_FRAME: 827ffbbc -- (.trap 0xffffffff827ffbbc)
.trap 0xffffffff827ffbbc
ErrCode = 00000000
eax=00000000 ebx=854a2000 ecx=854b4154 edx=854b415c esi=854b2238 edi=854b2238
eip=89e15b26 esp=827ffc30 ebp=827ffc40 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
yk60x86+0xeb26:
89e15b26 f70000000080 test dword ptr [eax],80000000h ds:0023:00000000=????????
.trap
Resetting default scope
If it always crashes with yk60x86.sys you should try installing the latest driver. Try both Acer & Marvell. If that doesn't help, and the cash is always with the Marvel driver, you can safely pinpoint that (hardware) as culprit.
But if it doesn't work is there a way to stop Vista from enabling the device on start up? and could I just uninstall the device in Device Manager without causing other problems?
If you never want to use the wired LAN, the best option would be to disable it from your computers BIOS. If you just remove it from Device Manager, Windows would just 'rediscover' the device when you reboot.