Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: Dell Inspiron N5010 BSOD

16 Feb 2011   #1

Windows 7 Ultimate x64
 
 
Dell Inspiron N5010 BSOD

Hey guys,

Attached you will find BSOD Dump & System File Collection files along with System Health Report.

I get BSOD a few times a day, mostly when playing video games.

I updated the BIOS and all the drivers. Please advice, thank you in advance

Is Windows 7 . . .
- x86 (32-bit) or x64 - x64
- the original installed OS on the system? OpenDos
- an OEM or full retail version? Full retail
- What is the age of system (hardware)? brand new computer, bought a week ago
- What is the age of OS installation (have you re-installed the OS?) Did a fresh install right after I bought it.

My System SpecsSystem Spec
.

16 Feb 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by killerch0 View Post
Hey guys,

Attached you will find BSOD Dump & System File Collection files along with System Health Report.

I get BSOD a few times a day, mostly when playing video games.

I updated the BIOS and all the drivers. Please advice, thank you in advance

Is Windows 7 . . .
- x86 (32-bit) or x64 - x64
- the original installed OS on the system? OpenDos
- an OEM or full retail version? Full retail
- What is the age of system (hardware)? brand new computer, bought a week ago
- What is the age of OS installation (have you re-installed the OS?) Did a fresh install right after I bought it.


These were all caused by your video subsystem. Probably the driver, perhaps heat, or the card itself.

I would start with the driver since it is the most frequent thing to fail

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.


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\Windows_NT6_BSOD_jcgriff2\021511-13806-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Tue Feb 15 15:30:53.118 2011 (GMT-5)
System Uptime: 0 days 1:10:45.866
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880051aecf7, fffff8800216f6a8, fffff8800216ef10}

Probably caused by : dxgmms1.sys ( dxgmms1+20cf7 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880051aecf7, The address that the exception occurred at
Arg3: fffff8800216f6a8, Exception Record Address
Arg4: fffff8800216ef10, Context Record Address

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


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

FAULTING_IP: 
dxgmms1+20cf7
fffff880`051aecf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

EXCEPTION_RECORD:  fffff8800216f6a8 -- (.exr 0xfffff8800216f6a8)
ExceptionAddress: fffff880051aecf7 (dxgmms1+0x0000000000020cf7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800216ef10 -- (.cxr 0xfffff8800216ef10)
rax=fffff8a00b456930 rbx=bffff8a00b7ffe50 rcx=fffffa8005747000
rdx=fffffa80045826a0 rsi=fffffa8005747000 rdi=fffffa8005747000
rip=fffff880051aecf7 rsp=fffff8800216f8e0 rbp=fffffa8004023998
 r8=fffffa80046de701  r9=0000000000000000 r10=0000000000000000
r11=00000000000000d8 r12=fffffa80045826a0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1+0x20cf7:
fffff880`051aecf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh ds:002b:bffff8a0`0b7ffea4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0d0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1+20cf7
fffff880`051aecf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 00000000ffffd94a to fffff880051aecf7

STACK_TEXT:  
fffff880`0216f8e0 00000000`ffffd94a : 00000000`0000000f fffffa80`05704000 fffffa80`05705750 00000000`00000000 : dxgmms1+0x20cf7
fffff880`0216f8e8 00000000`0000000f : fffffa80`05704000 fffffa80`05705750 00000000`00000000 fffff880`051abed3 : 0xffffd94a
fffff880`0216f8f0 fffffa80`05704000 : fffffa80`05705750 00000000`00000000 fffff880`051abed3 00000000`00000000 : 0xf
fffff880`0216f8f8 fffffa80`05705750 : 00000000`00000000 fffff880`051abed3 00000000`00000000 fffffa80`04756330 : 0xfffffa80`05704000
fffff880`0216f900 00000000`00000000 : fffff880`051abed3 00000000`00000000 fffffa80`04756330 00000000`00000072 : 0xfffffa80`05705750


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1+20cf7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

STACK_COMMAND:  .cxr 0xfffff8800216ef10 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1+20cf7

BUCKET_ID:  X64_0x7E_dxgmms1+20cf7

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880051aecf7, The address that the exception occurred at
Arg3: fffff8800216f6a8, Exception Record Address
Arg4: fffff8800216ef10, Context Record Address

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


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

FAULTING_IP: 
dxgmms1+20cf7
fffff880`051aecf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

EXCEPTION_RECORD:  fffff8800216f6a8 -- (.exr 0xfffff8800216f6a8)
ExceptionAddress: fffff880051aecf7 (dxgmms1+0x0000000000020cf7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800216ef10 -- (.cxr 0xfffff8800216ef10)
rax=fffff8a00b456930 rbx=bffff8a00b7ffe50 rcx=fffffa8005747000
rdx=fffffa80045826a0 rsi=fffffa8005747000 rdi=fffffa8005747000
rip=fffff880051aecf7 rsp=fffff8800216f8e0 rbp=fffffa8004023998
 r8=fffffa80046de701  r9=0000000000000000 r10=0000000000000000
r11=00000000000000d8 r12=fffffa80045826a0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1+0x20cf7:
fffff880`051aecf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh ds:002b:bffff8a0`0b7ffea4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1+20cf7
fffff880`051aecf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 00000000ffffd94a to fffff880051aecf7

STACK_TEXT:  
fffff880`0216f8e0 00000000`ffffd94a : 00000000`0000000f fffffa80`05704000 fffffa80`05705750 00000000`00000000 : dxgmms1+0x20cf7
fffff880`0216f8e8 00000000`0000000f : fffffa80`05704000 fffffa80`05705750 00000000`00000000 fffff880`051abed3 : 0xffffd94a
fffff880`0216f8f0 fffffa80`05704000 : fffffa80`05705750 00000000`00000000 fffff880`051abed3 00000000`00000000 : 0xf
fffff880`0216f8f8 fffffa80`05705750 : 00000000`00000000 fffff880`051abed3 00000000`00000000 fffffa80`04756330 : 0xfffffa80`05704000
fffff880`0216f900 00000000`00000000 : fffff880`051abed3 00000000`00000000 fffffa80`04756330 00000000`00000072 : 0xfffffa80`05705750


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1+20cf7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

STACK_COMMAND:  .cxr 0xfffff8800216ef10 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1+20cf7

BUCKET_ID:  X64_0x7E_dxgmms1+20cf7

Followup: MachineOwner
---------
My System SpecsSystem Spec
16 Feb 2011   #3

Windows 7 Ultimate x64
 
 

[QUOTE=zigzag3143;1243841]
Quote   Quote: Originally Posted by killerch0 View Post
Hey guys,
These were all caused by your video subsystem. Probably the driver, perhaps heat, or the card itself.

I would start with the driver since it is the most frequent thing to fail

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.
I did try to reinstall the driver, probably without wiping fully the old one. I am now installing the new driver after removing it with Guru 3d Driver Sweeper, will tell you if it helps

as for overheating, the laptop doesn't seem to be that hot, its on a flat surface and the fans output are not blocked. lets hope its not a factory defected card.

Thank you zigzag3143 will post again if the problem presist
My System SpecsSystem Spec
.


20 Feb 2011   #4

Windows 7 Ultimate x64
 
 

The problem still persist I have attached the new BSOD Dump & System File Collection files

Please advice
My System SpecsSystem Spec
21 Feb 2011   #5

Windows 7 Ultimate x64
 
 

help still needed
My System SpecsSystem Spec
06 Mar 2011   #6

Windows 7 Ultimate x64
 
 

the problem still persist, I even did a fresh install
My System SpecsSystem Spec
Reply

 Dell Inspiron N5010 BSOD





Thread Tools



Similar help and support threads for2: Dell Inspiron N5010 BSOD
Thread Forum
Dell Inspiron 15R (N5010) Heat Problem..Help Please! Performance & Maintenance
Dell inspiron 15R (N5010) fan problems Hardware & Devices
Dell Inspiron N5010 stuck up at starting window General Discussion
Windows 7 x64 i5 Dell Inspiron N5010 lags when music played Performance & Maintenance
Solved Dell Inspiron n5010 bluetooth problem Hardware & Devices
BSOD with dell inspiron n5010 BSOD Help and Support
Where can i download 32-bit drivers for my Dell Inspiron n5010? Drivers

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:47 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33