BSOD - Tried Most Everything

[dchobanik]

I have a computer with a fresh installation of windows 7 on my media center. I had perviously have windows vista on the machine but changed the operating system and recently motherboard to try to create a more stable platform with no provail so far.

Previouly on the vista machine with the XFX680i board and 4 GB of ram, i mainly had tones of freezing and in troubleshooting the issues had changed ram, video cards, different software installation, updates, BIOS etc everything but the board to try to solve the problem with no provail.

On the new machine I only get the BSOD at random times ofter while proccessing something (does not tend to do this when I am not working with the machine). I now have a new board, same RAM and new video card, and the same proccesor. I tried identifiying issues from the event logs and I have a tone of event issues mainly I get kernel power issues. I'm really not that knowledgable on diagnosing crash dumps and I have been having issues for months so I am really hoping that someone with more knowledge then me could help out

This is very frustrating, I have never had issues like this on any other computer.

Thanks

Devin

 

[dchobanik]

Update

Oh also I am using 64 bit Windows 7 on this machine

 

[Pauly]

Start with the basics, make sure all drivers & bios etc are up to date
If your OCing return settings to default

Your most recent dump says memory corruption, try running memtest for a period of time preferably overnight and see if you get any errors

Other dumps are pointing towards other things lsass.exe & wmpnetwk.exe + more
Possible driver issues?
Havent been thru them all sure others will have a look, but id start with memory check

Let us know how it goes

 

[Geo64]

You are getting 0x3b errors, so please completely uninstall your antivirus and firewall to test. Disabling will not help.

Install the latest chipset/motherboard drivers from the manufacturer's site.

Update your audio driver to latest from Realtek's website:

RTKVHD64 RTKVHD64.sys Thu Jul 24 06:05:39 2008

Update your video driver to latest from NVIDIA's website:

nvlddmkm nvlddmkm.sys Thu May 14 16:48:07 2009

Update this driver:

lmimirr  lmimirr.sys  Tue Apr 10 18:32:45 2007

Update your network driver from Realtek's site:

Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009

After you do these things, it should be alright.

Update these as well, if possible:

RaInfo   RaInfo.sys   Fri Jan 04 13:57:14 2008
LMIRfsDriver LMIRfsDriver.sys Mon Jul 14 12:26:56 2008

 

[usasma]

Is this a dual boot system with XP? I ask because the first BSOD is for a STOP 0x9c - which is for XP and ealier. It was replaced by STOP 0x124 in Vista and Win7.

I'd also suggest updating your JMicron drivers due to the age of this one: jraid.sys Mon Jul 21 23:59:14 2008. Storage drivers are finicky in Win7, so the latest Win7 version is essential for the system to function properly. Try the JMicron site for drivers: Driver

You may also get drivers for the Chipset and SATA RAID drivers from here: GIGABYTE - Support&Download - Motherboard - Driver - GA-EP45-UD3R (rev. 1.0)
These SATA RAID drivers will update your jraid.sys to file with a date of 8/13/2009

There are a bunch of different errors listed, so I'd suggest following all the instructions to see if that fixes the BSOD issues. If you have any difficulties in doing any of this stuff, please post back for advice.

 

[dchobanik]

Thanks all

Thanks for the information, this is definatly helpfull. I ran Memtest last night with no issues. I have to step out for a few hours today but I will start with all of the updates and things you have suggested and I will let you know.

Devin

 

[dchobanik]

Update

Ok, to awnser usasma, this is only a single install system with windows 7 installed.

I did do all of the below with the exception for the jmicron driver as when I tried to download the link was missing I can try this latter today.

I did update the following:

Lan Driver
Chipset driver
Raid Driver
Video Card Driver
Audio Driver

I just removed antivirus but most of the components had been installed with this not installed.

I have included the new dump so please let me know what you think?

Devin

 

[chev65]

Vsserv.exe shows up as the cause of the last BSOD. Are you running bit defender or bullguard?

If so uninstall them and see if the problem is fixed.

When you uninstalled Norton did you use this uninstall tool for it? Download and run the Norton Removal Tool

The vsserv.exe process is a core component of your BitDefender internet security software. If you stop this process, BitDefender will not be able to effectively protect your computer from viruses and trojans, so unless it causes problems with your system you should try and leave it running.

What are your FSB and memory settings on your 680i? Those settings can have a profound effect on stablity.

 

[dchobanik]

Yes it is bit defender. I removed it this morning and the previous antivirus was Panda.

I'll see in a day or two if this was the problem.

I did change the board and I am at factory settings. GA-EP45-UD3R (rev. 1.0) is the current board i am using.

I'll see what happens over the next few days.

Thanks

 

[usasma]

I'm seeing a lot of issues with GA-EP45 boards - almost as many as with the Asus P5 series.

 

[dchobanik]

Updated Minidump

Ok I did remove the antivirus and went about 2-3 days with no problem then yesterday I checked and had this issue.

The minidump is attached.

Thanks

Devin

 

[zigzag3143]

Ok I did remove the antivirus and went about 2-3 days with no problem then yesterday I checked and had this issue.

The minidump is attached.

Thanks

Devin

Hi Devin

this one is pretty clear cut. You vid driver (nvlddmkm.sys and dxgkrnl.sys) probably caused it. the dxgkrnl is the direct x component so you might want to consider updating that as well

I would update that and the other old drivers listed below
run a system file check to verify and repair your system fiels
type cmd in search>right click and run as admin>sfc /scannow

Of course if you are overclocking stop
if you have a raid update its driver

secdrv.SYS        fffff880`06195000    fffff880`061a0000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
lmimirr.sys        fffff880`044a4000    fffff880`044ab000    0x00007000    0x461c108d    4/10/2007 5:32:45 PM                        
RaInfo.sys        fffff880`04bb5000    fffff880`04bbc000    0x00007000    0x477e818a    1/4/2008 1:57:14 PM                        
LMIRfsDriver.sys        fffff880`04a00000    fffff880`04a13000    0x00013000    0x487b7e50    7/14/2008 11:26:56 AM

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


Loading Dump File [C:\Users\K\Desktop\121709-42089-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e50
Debug session time: Thu Dec 17 20:13:31.283 2009 (GMT-5)
System Uptime: 1 days 9:37:00.546
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
[B]Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys[/B]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[B]BugCheck 116, {fffffa800876d4e0, fffff8801031d230, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+10d230 )[/B]

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

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

VIDEO_TDR_FAILURE (116)
[B]Attempt to reset the display driver and recover from timeout failed.[/B]
Arguments:
Arg1: fffffa800876d4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801031d230, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+10d230
fffff880`1031d230 803d39d3b60000  cmp     byte ptr [nvlddmkm+0xc7a570 (fffff880`10e8a570)],0
[B]
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT[/B]

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`055e69c8 fffff880`0450bef8 : 00000000`00000116 fffffa80`0876d4e0 fffff880`1031d230 00000000`00000000 : nt!KeBugCheckEx
fffff880`055e69d0 00000000`00000116 : fffffa80`0876d4e0 fffff880`1031d230 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`055e69d8 fffffa80`0876d4e0 : fffff880`1031d230 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`055e69e0 fffff880`1031d230 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`0876d4e0
fffff880`055e69e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`0450bc02 : nvlddmkm+0x10d230


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+10d230
fffff880`1031d230 803d39d3b60000  cmp     byte ptr [nvlddmkm+0xc7a570 (fffff880`10e8a570)],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+10d230

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b07613e

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

 

[dchobanik]

The Saga Continues

Hello I'm back and included is the latest dump, I have had a few recent crashes and have also checked to ensure all my drivers are up to date and I replaced my video card with a new one. Please let me know what is happening here.

Thanks

File is now included.

Thanks

 

[zigzag3143]

Hello I'm back and included is the latest dump, I have had a few recent crashes and have also checked to ensure all my drivers are up to date and I replaced my video card with a new one. Please let me know what is happening here.

Thanks

Nothing attached try again

 

[usasma]

The last 2 dumps blame the OS kernel.

Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

Here's the older drivers:

LHidFilt.Sys Tue Jan 23 18:41:13 2007
lmimirr.sys  Tue Apr 10 18:32:45 2007
LMIRfsDriver.sys Mon Jul 14 12:26:56 2008
LMouFilt.Sys Tue Jan 23 18:41:16 2007
RaInfo.sys   Fri Jan 04 13:57:14 2008

Once you've updated everything, please try running Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Here's a summary of the last 2 BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 27 04:31:27.197 2009 (GMT-5)
System Uptime: 0 days 4:29:13.295
BugCheck 7F, {8, 80050031, 6f8, fffff80001ead4d4}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Dec 31 08:31:21.835 2009 (GMT-5)
System Uptime: 1 days 9:31:20.694
BugCheck 1E, {ffffffffc0000005, fffff800021880f1, 0, 1}
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+21 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LogMeIn.exe