Multiple different BSODs.


Joined
Oct 31, 2010
Messages
4
Reaction score
0
I've been getting multiple different BSODs with varying frequency.

Machine is basically brand new.
Motherboard is ASUS P7P55D-E
Video card is nvidia GTX 470, running newest stable drivers (260.99).
I've let memtest86 run overnight without reporting any errors.

Minidumps attached.
 

Attachments

Ad

Advertisements

Joined
Nov 30, 2009
Messages
1,752
Reaction score
396
Hey there, welcome. Yes, lot's of crashes.

Let's fix the issues.

1) Uninstall AVG in safe mode with the tool found here:

AV Uninstallers - Windows 7 Forums

Reboot and install MSE to replace it.

2) Update all Logitech drivers to all devices on the system, including any cameras mice, keyboard or gamepads etc...

LGVirHid LGVirHid.sys Mon Nov 23 20:36:48 2009
LMouFilt LMouFilt.Sys Wed Jun 17 12:49:43 2009

http://www.logitech.com/en-us/support-downloads

3) Update the NEC USB 3.0 driver:

nusb3xhc nusb3xhc.sys Thu Jan 21 22:22:21 2010

http://usa.asus.com/product.aspx?P_ID=9i872VNaAILRp8bS

4) Update Realtek lan driver:

Rt64win7 Rt64win7.sys Wed Jun 23 05:10:45 2010

RTL8111
 
Last edited:
Joined
Oct 31, 2010
Messages
4
Reaction score
0
Done all that, 3/4 Logitech devices (KB, mouse, gamepad) already had current drivers, updates the others from the links you provided. Got a few more this morning afterward, attaching them as well.
 

Attachments

Joined
Nov 30, 2009
Messages
1,752
Reaction score
396
Unfortunately, that means that there is a memory defect. Test with Memtest86+ overnight again for errors to show. You might have to test modules one at a time until you can find the errors like this.

You could also try raising the VDIMM (voltage) in the bios settings by .1v and save.
 
Last edited:
Joined
Oct 31, 2010
Messages
4
Reaction score
0
Not a memory defect, I seem to have fixed it though, by something that seems very...odd. The backlighting on my keyboard started getting flickery after your last post, and after switching the keyboard out and getting one more blue screen within 5 minutes, they seem to have stopped entirely, or at least for several days.
 
Joined
Nov 30, 2009
Messages
1,752
Reaction score
396
Yes, unfortunately there is memory defect (or incorrect bios setting for it).

The keyboard and/or lights in it can not cause the bsods you've had.

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI00.026\103110-28953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`0325ce50
Debug session time: Sun Oct 31 13:34:27.566 2010 (UTC - 4:00)
System Uptime: 0 days 3:34:33.783
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3452, 2fdf000, fffff700011087a8, 86400000bfe87424}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339e3 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003452, The subtype of the bugcheck.
Arg2: 0000000002fdf000
Arg3: fffff700011087a8
Arg4: 86400000bfe87424

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


BUGCHECK_STR:  0x1a_3452

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003103073 to fffff8000308f740

STACK_TEXT:  
fffff880`06fcf068 fffff800`03103073 : 00000000`0000001a 00000000`00003452 00000000`02fdf000 fffff700`011087a8 : nt!KeBugCheckEx
fffff880`06fcf070 fffff800`0306268a : fffffa80`06a49060 fffffa80`00000000 fffff8a0`00009c1e fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x339e3
fffff880`06fcf920 fffff800`03374dcf : fffff8a0`08098830 fffff880`06fcfc20 00000000`00000000 fffffa80`06a1cb60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`06fcf970 fffff800`0334d635 : 00000000`000000ff fffff8a0`00f8d401 00000000`7efad000 fffffa80`06a12b60 : nt!PspExitThread+0x92f
fffff880`06fcfa30 fffff800`0306c1db : 00000000`7efad000 fffffa80`0a4fa060 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`06fcfa60 fffff800`0306c620 : 00000000`0fe3f948 fffff880`06fcfae0 fffff800`0334d74c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`06fcfae0 fffff800`0308ea37 : fffffa80`06a1cb60 00000000`7efad000 00000000`000000c0 00000000`7efad000 : nt!KiInitiateUserApc+0x70
fffff880`06fcfc20 00000000`779a165a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0747e5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779a165a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339e3
fffff800`03103073 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339e3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+339e3

BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+339e3

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

Advertisements

Joined
Oct 31, 2010
Messages
4
Reaction score
0
Let me rephrase, I've ran memtest86'd since my first post for a fairly long stretch (10PM-4PM the following day), so either I have memory errors memtest86 isn't detecting, or my Logitech G15 keyboard and/or it's drivers are the root cause. Either way, the blue screens seem to have stopped.
 
Ad

Advertisements

Joined
Nov 30, 2009
Messages
1,752
Reaction score
396
Ah yeah, right on. The keyboard drivers could have been responsible then, for sure. Not the actual physical keyboard hardware.

Enjoy man! :)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top