Dell XPS fairly frequent BSOD

pannonia909 · Oct 27, 2013

Hi I hope someone can help. I'm getting frequent (once or twice a week) BSODs on laptop ever since I bought it second hand about a year ago. I saw it mentioned on an other thread about hibernating might cause these problems and I have been turning it off recently instead. This has not solved issue.
I have also stopped running the coolers under the machine now.
I'm no techie as such, so please be patient with me...

Other info:
· OS - Windows 7 professional
· x86
· What was original installed OS on system? - possibly Vista, not sure
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - pre-installed by previous owner
· Age of system (hardware) unsure
· Age of OS installation - have you re-installed the OS? about year ago, not re-installed since

· CPU - intel r core tm 2 duo
· Video Card - geforce 8600 gt
· MotherBoard - unsure
· Power Supply - brand & wattage (if laptop, skip this one)

· System Manufacturer Dell
· Exact model number (if laptop, check label on bottom) PP28L

Thank you in advance

Patrick · Oct 27, 2013

Hi,

The attached jcgriff2 output zip is corrupt, it seems. Can you manually zip up your DMP files and attach them rather than using the collection app?

Regards,

Patrick

Wrench97 · Oct 27, 2013

Looks like Win 7 was installed in Sept of 2012 and Bsod's started in February?
The only older drivers are for the camera and they are the newest available( I had a m1530 with Win7)
Did you upgrade from Vista because of a problem or just to move to Win7?

Lets try running driver verifier I ran the dumps from this month and there is nothing conclusive.

Be sure to set a restore point and follow the instructions here> https://www.sysnative.com/forums/bs...er-verifier-blue-screen-of-death-related.html

Code:

Debug session time: Wed Oct 23 08:56:10.383 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\102313-20248-01.dmp]
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 0:20:30.224
Probably caused by : win32k.sys ( win32k!UserThreadCallout+0 )
BugCheck 1000008E, {c000001d, 989dcb61, 8ff93c84, 0}
BugCheck Info: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
Bugcheck code 1000008E
Arguments: 
Arg1: c000001d, The exception code that was not handled
Arg2: 989dcb61, The address that the exception occurred at
Arg3: 8ff93c84, Trap Frame
Arg4: 00000000
BUGCHECK_STR:  0x8E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  0x8E_BAD_IP_win32k!UserThreadCallout+0
MaxSpeed:     2200
CurrentSpeed: 2194
BiosVersion = A12
BiosReleaseDate = 11/19/2008
SystemManufacturer = Dell Inc.
SystemProductName = XPS M1530                       
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Oct 16 14:14:48.871 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\101613-36145-01.dmp]
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 12:46:41.713
Probably caused by : ntkrpamp.exe ( nt!PoIdle+239 )
BugCheck A, {43a83584, ff, 0, 82acc4fd}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments: 
Arg1: 43a83584, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82acc4fd, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xA_nt!PoIdle+239
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Oct 13 05:36:01.129 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\101313-20716-01.dmp]
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 0:27:00.375
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::RecordPagingOperation+dc )
BugCheck 50, {8cde5770, 1, 931571fc, 0}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: 8cde5770, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 931571fc, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x50_dxgmms1!VIDMM_GLOBAL::RecordPagingOperation+dc
MaxSpeed:     2200
CurrentSpeed: 2194
BiosVersion = A12
BiosReleaseDate = 11/19/2008
SystemManufacturer = Dell Inc.
SystemProductName = XPS M1530                       
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Patrick · Oct 27, 2013

Hm, if Bruce was able to open them it must just have been a problem on my end with downloading. I tried downloading twice. I digress.

pannonia909 · Oct 28, 2013

Wrench97 said:

Looks like Win 7 was installed in Sept of 2012 and Bsod's started in February?
The only older drivers are for the camera and they are the newest available( I had a m1530 with Win7)
Did you upgrade from Vista because of a problem or just to move to Win7?

Lets try running driver verifier I ran the dumps from this month and there is nothing conclusive.

Be sure to set a restore point and follow the instructions here> https://www.sysnative.com/forums/bs...er-verifier-blue-screen-of-death-related.html

Code:

Debug session time: Wed Oct 23 08:56:10.383 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\102313-20248-01.dmp]
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 0:20:30.224
Probably caused by : win32k.sys ( win32k!UserThreadCallout+0 )
BugCheck 1000008E, {c000001d, 989dcb61, 8ff93c84, 0}
BugCheck Info: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
Bugcheck code 1000008E
Arguments: 
Arg1: c000001d, The exception code that was not handled
Arg2: 989dcb61, The address that the exception occurred at
Arg3: 8ff93c84, Trap Frame
Arg4: 00000000
BUGCHECK_STR:  0x8E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  0x8E_BAD_IP_win32k!UserThreadCallout+0
MaxSpeed:     2200
CurrentSpeed: 2194
BiosVersion = A12
BiosReleaseDate = 11/19/2008
SystemManufacturer = Dell Inc.
SystemProductName = XPS M1530                       
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Oct 16 14:14:48.871 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\101613-36145-01.dmp]
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 12:46:41.713
Probably caused by : ntkrpamp.exe ( nt!PoIdle+239 )
BugCheck A, {43a83584, ff, 0, 82acc4fd}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments: 
Arg1: 43a83584, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82acc4fd, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xA_nt!PoIdle+239
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Oct 13 05:36:01.129 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\101313-20716-01.dmp]
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 0:27:00.375
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::RecordPagingOperation+dc )
BugCheck 50, {8cde5770, 1, 931571fc, 0}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: 8cde5770, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 931571fc, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x50_dxgmms1!VIDMM_GLOBAL::RecordPagingOperation+dc
MaxSpeed:     2200
CurrentSpeed: 2194
BiosVersion = A12
BiosReleaseDate = 11/19/2008
SystemManufacturer = Dell Inc.
SystemProductName = XPS M1530                       
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Hi,

Win 7 might have been installed in Sep 2012, as I bought it in Oct, but crashes have definitely started soon after that and not only from Feb. Or did you mean Feb 12?? Also reading back communication with previous owner, Vista was installed at one point, but he preferrred Win7 to run high demand software. He also said Vista is recommended on this machine. Should I try that?

I will have a go at driver verifier later today.

Your help is very much appreciated.
Thanks

Wrench97 · Oct 28, 2013

Vista is what it would have come with, Win7 runs fine on that model.
The biggest issue with them was the high failure rate of the 8600M GT Video chip, which is what finally did mine in.

pannonia909 · Oct 28, 2013

That sounds ominous. If mine has same problem does that mean that is the end of it??

Wrench97 · Oct 28, 2013

Yours does not sound like the typical video failure, usually they get a pixilated or black screen, the motherboard can be changed. but all you can buy are refurbished oem boards for $150 at the time, I just decided to bite the bullet use the hard drive(recently replaced at the time), CPU and Ram(also upgraded to 8gig) in other laptops, I also sold the screen and upgraded to a i5 :)

pannonia909 · Oct 28, 2013

You are very helpful Wrench, thank you. Just to add as well, when I purchased laptop, it had brand new video card and motherboard installed. If that makes any difference?

muhahaa · Oct 28, 2013

Looks like a bad processor.

Code:

FAULTING_IP: 
dxgmms1!VidSchSubmitCommand+23f
931534b1 8b4634          mov     eax,dword ptr [esi+34h]

EXCEPTION_RECORD:  9a394f20 -- (.exr 0xffffffff9a394f20)
ExceptionAddress: 931534b1 (dxgmms1!VidSchSubmitCommand+0x0000023f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 3472a21b
Attempt to read from address 3472a21b

CONTEXT:  9a394b00 -- (.cxr 0xffffffff9a394b00)
eax=00000000 ebx=85b79160 ecx=00020203 edx=00000000 esi=9a3952a8 edi=85b31ae8
eip=931534b1 esp=9a394fe8 ebp=9a395000 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
dxgmms1!VidSchSubmitCommand+0x23f:
931534b1 8b4634          mov     eax,dword ptr [esi+34h] ds:0023:9a3952dc=00000000

What else could cause a read from 9a3952a8 to be reported as read from 3472a21b?

Wrench97 · Oct 28, 2013

The video card so to speak is not a separate card but rather a chip on the motherboard, there are several ways of repairing them from reflowing(heaing it up to the melting point) the solder to replacing the 8600m chip, but there was a high failure rate on refurbished boards from Dell(I used to do some Dell service work) when they were under warranty not just for this model but for many different ones the desktop XPS 700 series was probably the worst..................

Wrench97 · Oct 28, 2013

muhahaa said:

Looks like a bad processor.

Code:

FAULTING_IP: 
dxgmms1!VidSchSubmitCommand+23f
931534b1 8b4634          mov     eax,dword ptr [esi+34h]

EXCEPTION_RECORD:  9a394f20 -- (.exr 0xffffffff9a394f20)
ExceptionAddress: 931534b1 (dxgmms1!VidSchSubmitCommand+0x0000023f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 3472a21b
Attempt to read from address 3472a21b

CONTEXT:  9a394b00 -- (.cxr 0xffffffff9a394b00)
eax=00000000 ebx=85b79160 ecx=00020203 edx=00000000 esi=9a3952a8 edi=85b31ae8
eip=931534b1 esp=9a394fe8 ebp=9a395000 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
dxgmms1!VidSchSubmitCommand+0x23f:
931534b1 8b4634          mov     eax,dword ptr [esi+34h] ds:0023:9a3952dc=00000000

What else could cause a read from 9a3952a8 to be reported as read from 3472a21b?

Maybe, lets see what the temps look like.

D/L and run Hardware Monitor use the win 7 snipping tool to grab a screen shot of the HWM window with all the trees expanded.

pannonia909 · Oct 28, 2013

Ok, I attempted to run driver verifier and I'm kind of lost after re-booting stage as nothing seem to happen. I mean it boots up fine as before, no BSOD, and looking at your instructions, I never saw this either: VERIFIER_ENABLED BSOD.

Also do I have to start in safe mode to get to "verifier /query"? Tried doing this in normal windows after start up, but all I get is a quick flash and then (what I assume) verifier screen disappears.
Or do I only need to do that if I get BSOD at re-boot?

pannonia909 · Oct 28, 2013

Screen shots...

Wrench97 · Oct 28, 2013

The temps look good.

It's not unusual for Windows to start normally after verifier is enabled.
All verifier does is put the drivers in a box so to speak, so that if one of them overwrites it's address space into another drivers space verifier will catch it and name the driver in the .dmp file.
Use the PC normally if/when it bsod's again zip(compress) up the .dmp file and attach it to your post.

pannonia909 · Oct 30, 2013

Latest crash this morning...

Can you please instruct how to upload the actual dump file?

Thanks

Wrench97 · Oct 30, 2013

The .dmp files are located in the C:\Windows\Minidump directory, or just rerun the collection app.

pannonia909 · Oct 30, 2013

Collection rerun and attached...

Wrench97 · Oct 30, 2013

It's a verifier enabled dump naming a Windows file virtualization process driver luafv.sys.

That is pointing toward a hardware issue, I think it's going to be a motherboard or CPU issue but lets run Memtest86+ just to rule out the ram.
D/L Memtest+ > How to perform a MemTest86+ Test | Tech Support Forum

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00005003, The subtype of the bugcheck.
Arg2: 86600000
Arg3: 00000359
Arg4: 0035b6b6

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  87d749a0 -- (.trap 0xffffffff87d749a0)
.trap 0xffffffff87d749a0
ErrCode = 00000000
eax=9f13f0f8 ebx=00000000 ecx=87d74a44 edx=00007666 esi=95399508 edi=8b4f7068
eip=9792a02d esp=87d74a14 ebp=87d74a24 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
luafv+0x102d:
9792a02d 663910          cmp     word ptr [eax],dx        ds:0023:9f13f0f8=????
.trap
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82a7da97 to 82af8bfc

STACK_TEXT:  
87d747ec 82a7da97 0000001a 00005003 86600000 nt!KeBugCheckEx+0x1e
87d74824 82abe0e4 c04f89f8 84696a38 00000000 nt!MiAllocateWsle+0x6f
87d74884 82aab1b8 00000000 9f13f0f8 c04f89f8 nt!MiResolveTransitionFault+0x7d2
87d74908 82aa8c48 9f13f0f8 00000000 82b84280 nt!MiDispatchFault+0x61d
87d74988 82a5aaa8 00000000 9f13f0f8 00000000 nt!MmAccessFault+0x14d6
87d74988 9792a02d 00000000 9f13f0f8 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
87d74a24 855cbaeb 8b4f7068 87d74a44 87d74a70 luafv+0x102d
87d74a90 855cec77 87d74aa8 87d74b38 87d74b04 fltmgr!FltpPerformPreCallbacks+0x34d
87d74ac0 82aac273 87d74b04 87d74b40 89ff2f08 fltmgr!FltpPreFsFilterOperation+0xab
87d74ae4 82aab807 00000001 00000001 87d74c43 nt!FsFilterPerformCallbacks+0xa4
87d74c44 82a8ecb9 8d937d30 87d74c68 8ad1039c nt!FsRtlAcquireFileForModWriteEx+0xbd
87d74cec 82a8ef74 8d937d30 00000000 8534b4b8 nt!MiGatherMappedPages+0x96e
87d74d50 82c2313d 00000000 a86a0bd2 00000000 nt!MiMappedPageWriter+0x13d
87d74d90 82aca559 82a8ee37 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
luafv+102d
9792a02d 663910          cmp     word ptr [eax],dx

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  luafv+102d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: luafv

IMAGE_NAME:  luafv.sys

pannonia909 · Nov 5, 2013

Hi,

I'm struggling to perform the memtest you recommended.
1. Not sure if diskimager is writing to USB as it seems to be done very quickly. Tried it several times and when I look on USB properties, it's showing empty.
2. When I repeatedly press either F8 or F12, I do not get blue screen with option to choose bootable device. This might be consequence of above - i.e. USB not written in the first place.

Do you have any suggestions what else I could try to do this test? Is there a different memory testing tool available?

Thanks

Dell XPS fairly frequent BSOD

Member

Attachments

Sysnative Staff

Administrator, Hardware Expert

Sysnative Staff

Member

Administrator, Hardware Expert

Member

Administrator, Hardware Expert

Member

Windows Specialist

Administrator, Hardware Expert

Administrator, Hardware Expert

Member

Member

Administrator, Hardware Expert

Member

Attachments

Administrator, Hardware Expert

Member

Administrator, Hardware Expert

Member