Having alot of problems tracking down a "windows 7 ATK 0110" driver.
The only thing i've been able to read upon so far is that, mentioned on the asus forums for my motherboard.. the M2N-Sli Deluxe.
That the Windows Vista 64bit driver can be used because apparently that board is not supported by Windows 7!?
OK According to Device Manager my current version that i just installed from the Vista 64bit package for the ATK0110 driver from the asus website for my M2N-Sli Deluxe board is as follows.
Driver Date: 16/07/2009
Driver Version: 1043.6.0.0
Now if anyone knows of a newer more updated driver, please let me know.
I'm gonna monitor this from this second on, as soon as i get another BSOD relating to a 0x3b or 0x1e i'm gonna scream!
AWESOME!!
Time to scream starts now..
AAAAAAAARRRRRRRRRRRGGGGGGGGGGGHHHHHHHHHHHHH!!!!!!! O_o
Just installed the drivers for the nForce chipset 15.53 from the nvidia website, latest drivers for my board which included the ethernet driver and storage driver..
That part went fine, got to the 2nd part "would you like to install the nvidia network access manager" ... Sure why not?!?!
BAM!! BSOD
Minidump attatched :)
Not since my last post there hasn't been.
I'm not entirely sure if the nforce drivers i installed were completed correctly or not, because usually when a BSOD occurs, anything you've done in that session is usually lost.
Hi,
If you get more BSODs try driver verifier
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Yeah its still happening unfortunately..
its 99% of the time the 0x3b error.
Please follow reventon's instructions above for enabling Driver Verifier.Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\Desktop\062310-28423-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: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50 Debug session time: Tue Jun 22 18:16:54.787 2010 (UTC - 4:00) System Uptime: 0 days 0:09:01.893 Loading Kernel Symbols ............................................................... ................................................................ ............................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002ef0795, fffff8800b18c840, 0} Probably caused by : ntkrnlmp.exe ( nt!HvpFindFreeCellInThisViewWindow+45 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002ef0795, Address of the instruction which caused the bugcheck Arg3: fffff8800b18c840, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. 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!HvpFindFreeCellInThisViewWindow+45 fffff800`02ef0795 418b840ca8000000 mov eax,dword ptr [r12+rcx+0A8h] CONTEXT: fffff8800b18c840 -- (.cxr 0xfffff8800b18c840) rax=0000000001bc7000 rbx=0000000001bc7000 rcx=fffff8a000b9d010 rdx=0000000000000002 rsi=0000000000000000 rdi=fffff8a000b9d010 rip=fffff80002ef0795 rsp=fffff8800b18d210 rbp=0000000000000000 r8=0000000000000018 r9=0000000000000000 r10=0000000001bc8000 r11=0000000000000006 r12=ffed7c1b65470e00 r13=fffff8a000b9d010 r14=0000000001bc8000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!HvpFindFreeCellInThisViewWindow+0x45: fffff800`02ef0795 418b840ca8000000 mov eax,dword ptr [r12+rcx+0A8h] ds:002b:ffed74bb`6600deb8=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: SearchIndexer. CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002ef0795 STACK_TEXT: fffff880`0b18d210 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvpFindFreeCellInThisViewWindow+0x45 FOLLOWUP_IP: nt!HvpFindFreeCellInThisViewWindow+45 fffff800`02ef0795 418b840ca8000000 mov eax,dword ptr [r12+rcx+0A8h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!HvpFindFreeCellInThisViewWindow+45 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb STACK_COMMAND: .cxr 0xfffff8800b18c840 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!HvpFindFreeCellInThisViewWindow+45 BUCKET_ID: X64_0x3B_nt!HvpFindFreeCellInThisViewWindow+45 Followup: MachineOwner ---------
So i'm guessing what this driver verifier does is basically flag the driver at fault of causing the actual BSOD.
I thought that was supposed to be mentioned in the minidump it takes?
Question remains, is if the driver thats at fault has been updated to the most recent driver yet the BSOD continues, it would most likely have to be a direct hardware failure?
New drivers can be buggy, and old ones can be buggy and incompatible. Sadly, newer isn't always better. I often tell people that the latest nVidia drivers for my card have issues, and the September drivers Windows Update finds work best.
Driver Verifier strains the drivers, and hopefully flags the correct one in the dump.
Quote