more terrrible driver caused BSOD!!!!! SOB SOB

Gaupz · 30 Jan 2011

ok so i just recently narrowed down some blue screens to my old g15 with bad drivers, i replaced that keyboard with a razer lycosa, but now i am getting LESS_OR_NOT_EQUAL BSOD specifically last one was DRIVER_LESS_OR_NOT_EQUAL i will upload the last two dump files and could someone please read them and tell me what driver is causing this to happen

System:
AMD Phenom 2 x6 1055t cpu
ATI HIS 5850 gpu
asus m4a89gtd pro/usb3 mobo
8 gigs 1600mhz OCZ obsidian ram
wd 1bt hdd
patriot 60gb SSD
Razer naga mouse(updated drivers)
razer megalodon headset (updated drivers)
razer lycosa kyeboard (updated drivers)
as far as when the crash happens turn on pc came back almost 30 min later opened youtube and started a video than got DRIVER_LESS_OR_NOT_EQUAL I have been BSODING alot and would rly like the help thanks!!!!

zigzag3143 · 30 Jan 2011

Gaupz said:

ok so i just recently narrowed down some blue screens to my old g15 with bad drivers, i replaced that keyboard with a razer lycosa, but now i am getting LESS_OR_NOT_EQUAL BSOD specifically last one was DRIVER_LESS_OR_NOT_EQUAL i will upload the last two dump files and could someone please read them and tell me what driver is causing this to happen

System:
AMD Phenom 2 x6 1055t cpu
ATI HIS 5850 gpu
asus m4a89gtd pro/usb3 mobo
8 gigs 1600mhz OCZ obsidian ram
wd 1bt hdd
patriot 60gb SSD
Razer naga mouse(updated drivers)
razer megalodon headset (updated drivers)
razer lycosa kyeboard (updated drivers)
as far as when the crash happens turn on pc came back almost 30 min later opened youtube and started a video than got DRIVER_LESS_OR_NOT_EQUAL I have been BSODING alot and would rly like the help thanks!!!!

Memory corruption caused by WoW. test the memory with memtest
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Code:

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


Loading Dump File [C:\Users\K\Desktop\010102-19156-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03059e50
Debug session time: Tue Jan  1 20:50:33.588 2002 (GMT-5)
System Uptime: 0 days 1:33:50.899
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ecda93, fffff8800b52b000, 0}

Probably caused by : memory_corruption ( nt!MiGetProtoPteAddressExtended+17 )

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

2: 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: fffff80002ecda93, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800b52b000, 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!MiGetProtoPteAddressExtended+17
fffff800`02ecda93 4d8b4808        mov     r9,qword ptr [r8+8]

CONTEXT:  fffff8800b52b000 -- (.cxr 0xfffff8800b52b000)
rax=00000000ffe3fef8 rbx=0000000000000000 rcx=ffb2ffc7fe55f743
rdx=00000000000773c1 rsi=fffffa8007764640 rdi=0000000000000001
rip=fffff80002ecda93 rsp=fffff8800b52b9d0 rbp=0000000000000000
 r8=ff060081fec2ffdf  r9=ffb2ffbfff35ff83 r10=fffffa8007764640
r11=fffffa8007493538 r12=fffff6fb7da00008 r13=fffff680003b9e08
r14=fffff8800b52bac0 r15=00000000000773c1
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!MiGetProtoPteAddressExtended+0x17:
fffff800`02ecda93 4d8b4808        mov     r9,qword ptr [r8+8] ds:002b:ff060081`fec2ffe7=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002e1edaa to fffff80002ecda93

STACK_TEXT:  
fffff880`0b52b9d0 fffff800`02e1edaa : 00000000`00000000 00000000`00000000 00000000`00000000 b2800001`9131d005 : nt!MiGetProtoPteAddressExtended+0x17
fffff880`0b52ba00 fffff800`02e5a80a : fffffa80`07764640 fffffa80`07779b30 fffffa80`07779b30 00000000`773c1000 : nt! ?? ::FNODOBFM::`string'+0x14849
fffff880`0b52ba50 fffff800`03173c38 : 000003bc`00000000 00000000`773c2000 fffffa80`07764640 00000000`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`0b52bac0 fffff800`02e8b993 : ffffffff`ffffffff fffffa80`0772ab60 00000000`0030ebec 00000000`001adc18 : nt!NtQueryVirtualMemory+0x386
fffff880`0b52bbb0 00000000`7783ff8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001adbf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7783ff8a


FOLLOWUP_IP: 
nt!MiGetProtoPteAddressExtended+17
fffff800`02ecda93 4d8b4808        mov     r9,qword ptr [r8+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiGetProtoPteAddressExtended+17

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff8800b52b000 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiGetProtoPteAddressExtended+17

BUCKET_ID:  X64_0x3B_nt!MiGetProtoPteAddressExtended+17

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

Gaupz · 30 Jan 2011

I just got pc my back from a friend who did all sort of troubleshooting and testing and he said all of my hardware is solid and i know for a fact he used memtest86 with cd on boot