Dell Vostro 460 BSOD during regular use

stevenvw · 19 Apr 2013

Hello,
I have a Dell Vostro 460 running Windows 7 Home Premium x64. The processor is a Core i5-2500.
I have been getting BSOD's for a while now. They occur randomly during regular use...at different times with different programs.

After the BSOD's started happening I tested all the memory with Memtest for a minimum of 10 passes per stick (4x2GB). This was the RAM that shipped with the computer from the OEM. The results showed that the RAM was fine. I tested each stick individually in different slots.

I cloned the hard-drive to a new identical hard-drive and the issue still happened. I uninstalled/removed any extra programs, including AV software etc. I ran SFC which did not find any issues with the system.
I even ran checkdisk which didn't make a difference either.

I ended up doing a clean install of the operating system on the new harddrive, and things seemed to be good for a few days, but lo and behold, the problem still wasn't gone.

Every .DMP file that I have opened always mentions ntkrnlmp.exe under IMAGE_NAME:

After reinstalling I forgot to change my settings, so every .DMP file over-wrote the previous one.

This system is of course just a few months outside of warranty as well..
Any help is greatly appreciated!
Following are the results from opening the last dump file...

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [\\PWENTERPRSERVER\RedirectedFolders\steven\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\debuggers\SymbolCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e55670
Debug session time: Thu Apr 18 08:54:35.315 2013 (UTC - 6:00)
System Uptime: 0 days 0:04:54.548
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002f82bba, 1, 18}

Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+29a )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002f82bba, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000018, Parameter 1 of the exception

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!ObpCreateHandle+29a
fffff800`02f82bba f0480fba6f1800 lock bts qword ptr [rdi+18h],0

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000018

WRITE_ADDRESS: 0000000000000018

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0x1E_c0000005

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88008c6dda0 -- (.trap 0xfffff88008c6dda0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800b744b50
rdx=00000000000f001f rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f82bba rsp=fffff88008c6df30 rbp=0000000000000000
r8=fffff8a00ad11220 r9=00000000000000e8 r10=0000000000000000
r11=fffff8a00ad111d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po nc
nt!ObpCreateHandle+0x29a:
fffff800`02f82bba f0480fba6f1800 lock bts qword ptr [rdi+18h],0 ds:00000000`00000018=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cd2728 to fffff80002c87c00

STACK_TEXT:
fffff880`08c6d518 fffff800`02cd2728 : 00000000`0000001e ffffffff`c0000005 fffff800`02f82bba 00000000`00000001 : nt!KeBugCheckEx
fffff880`08c6d520 fffff800`02c87282 : fffff880`08c6dcf8 00000000`00000000 fffff880`08c6dda0 fffffa80`0b744b50 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`08c6dbc0 fffff800`02c85dfa : 00000000`00000001 00000000`00000018 fffffa80`06a48b00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`08c6dda0 fffff800`02f82bba : 00000000`00000000 fffff880`08c6df80 fffffa80`06fd2060 fffff8a0`0ad11220 : nt!KiPageFault+0x23a
fffff880`08c6df30 fffff800`02f7312e : fffffa80`00000000 fffff8a0`0ad11220 fffff8a0`000f001f 00000000`00000000 : nt!ObpCreateHandle+0x29a
fffff880`08c6e040 fffff800`02f6383b : fffffa80`070db670 fffff880`08c6e400 fffffa80`06da73d0 00000000`08000000 : nt!ObInsertObjectEx+0xde
fffff880`08c6e290 fffff800`02c86e93 : fffffa80`0b744b50 fffff880`08c6e538 fffff880`08c6e328 fffffa80`0ab46ec0 : nt!NtCreateSection+0x1fe
fffff880`08c6e310 fffff800`02c83450 : fffffa80`09d1c865 fffff800`02e2d2d8 fffff880`08c6e5a0 fffffa80`09d1e3e0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`08c6e518 fffffa80`09d1c865 : fffff800`02e2d2d8 fffff880`08c6e5a0 fffffa80`09d1e3e0 fffffa80`09d1f3d0 : nt!KiServiceLinkage
fffff880`08c6e520 fffff800`02e2d2d8 : fffff880`08c6e5a0 fffffa80`09d1e3e0 fffffa80`09d1f3d0 fffff880`00000002 : 0xfffffa80`09d1c865
fffff880`08c6e528 fffff880`08c6e5a0 : fffffa80`09d1e3e0 fffffa80`09d1f3d0 fffff880`00000002 00000000`08000000 : nt!ExWorkerQueue+0x58
fffff880`08c6e530 fffffa80`09d1e3e0 : fffffa80`09d1f3d0 fffff880`00000002 00000000`08000000 ffffffff`80000ea4 : 0xfffff880`08c6e5a0
fffff880`08c6e538 fffffa80`09d1f3d0 : fffff880`00000002 00000000`08000000 ffffffff`80000ea4 00000000`00000000 : 0xfffffa80`09d1e3e0
fffff880`08c6e540 fffff880`00000002 : 00000000`08000000 ffffffff`80000ea4 00000000`00000000 00000000`00000000 : 0xfffffa80`09d1f3d0
fffff880`08c6e548 00000000`08000000 : ffffffff`80000ea4 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00000002
fffff880`08c6e550 ffffffff`80000ea4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x8000000
fffff880`08c6e558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffffff`80000ea4

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ObpCreateHandle+29a
fffff800`02f82bba f0480fba6f1800 lock bts qword ptr [rdi+18h],0

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!ObpCreateHandle+29a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5147d9c6

FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!ObpCreateHandle+29a

BUCKET_ID: X64_0x1E_c0000005_nt!ObpCreateHandle+29a

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

Dsprague · 19 Apr 2013

Please follow the Blue Screen of Death (BSOD) Posting Instructions

stevenvw · 19 Apr 2013

here is the info from the sf diagnostic tool

fireberd · 19 Apr 2013

A couple of questions. I used to do a lot of support on the Dell Community users forums. Are you using the Dell supplied drivers or are you using what Windows installs and/or drivers direct from the hardware vendors (e.g. RealTek rather than the Dell supplied RealTek driver)? We found, generally, the Dell drivers should be used, especially the sound driver, due to Dell's custom motherboards and implementations.

Also, I see two video display drivers, the AMD and the Intel. Since you apparently have an AMD (ATI) video card, you don't need the Intel drivers. I also see some references to "Hight Definition Audio Device" which suggests the generic Windows installed sound drivers rather than the (Dell) RealTek drivers.

These items may not have anything to do with your problem, just things I saw.

VistaKing · 19 Apr 2013

??\C:\Windows\SysWOW64\rserver30\raddrvv3.sys

Belongs to No code has to be inserted here.

\??\C:\Windows\system32\Drivers\rikvm_9EC60124.sys

Belongs to CYBERLINK DVD Uninstall that product

But Id run an antivurs scan just to be sure you don't have any ADware or viruses on your machine

Code:

*******************************************************************************
*                                                                                                                                           *
*                        Bugcheck Analysis                                                                                           *
*                                                                                                                                           *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa8009d148c3, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa003c, Parameter 1 of the exception

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
+0
fffffa80`09d148c3 48635a3c        movsxd  rbx,dword ptr [rdx+3Ch]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000000007efa003c

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f13100
GetUlongFromAddress: unable to read from fffff80002f131c0
 000000007efa003c Nonpaged pool

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

BUGCHECK_STR:  0x1e_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  FamItrfc.Exe

FamItrfc.Exe belongs to Radmin Server . Reinstall the Software or Update it

Run a memory Test using Memtest . Take a look at the link below

RAM - Test with Memtest86+

Arc · 19 Apr 2013

Update Broadcom NetLink (TM) Gigabit Ethernet driver, form Ethernet NIC Driver Downloads | Broadcom

Download and install this particular version of Intel Rapid Storage Driver:

Version: 11.2.0.1006
Date: 06/07/2012

Let us know the results.

stevenvw · 22 Apr 2013

Sorry for not replying any sooner...

-I actually did a restore from the Dell Factory Image, so all the default drivers were from Dell, and any updates that I downloaded have been from the Dell website.
-I removed the Intel graphics drivers.
-I uninstalled the Radmin server, as well as Cyberlink DVD
-The network drivers have been updated with the latest Broadcom Drivers for that NIC
-The link for the Intel Rapid Storage Driver was broken, so I just searched for that version on the Intel website and installed them.

stevenvw · 22 Apr 2013

The computer crashed a few times over the weekend..including this morning again when I left for a few hours..I ran the tool again and attached the results as a .zip file to give more updated info..

stevenvw · 24 Apr 2013

I also ran the Windows Based Dell Diagnostics utility which ran for a few hours and did not detect any issues.
I then also ran the bootable diagnostics which also say that everything is ok.

I have run memtest for a minimum of 10 passes for each stick of RAM, each one in a separate slot in the motherboard and everything passed here as well.

I am very confused why this is happening and where the problem could be

Arc · 24 Apr 2013

stevenvw said:

The computer crashed a few times over the weekend..including this morning again when I left for a few hours..I ran the tool again and attached the results as a .zip file to give more updated info..

Unfortunately there is no new crash dumps

Run disc cleanup. It will free up the minidump folder. Then make it sure that crash dump recording is properly configured.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dell Vostro 460 BSOD during regular use

Dell Vostro 460 BSOD during regular use

info

More crash dumps

Diagnostics/memtest show all good