Unexpected reboots on Dell XPS 8700 - Minidump attached

Requesting assistance with reboots on my new Dell XPS 8700 - Error log shows "The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffff8038a3b4680, 0x0000000000000000, 0xfffff8036a38a9e3, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071513-24500-01."

I'm also getting periodic "A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SftService service." messages, and periodic "Virtual Disk Service - Unexpected provider failure. Restarting the service may fix the problem. Error code: 8007001F@02000014"

Windows 8 64 bit

Minidump here:

https://skydrive.live.com/redir?resid=121C25913A6E3B54!2619&authkey=!AOa-cSt7v4PVe4Q

Any assistance would be greatly appreciated!

July 15th, 2013 6:56pm

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8038a3b4680, 0, fffff8036a38a9e3, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33e2a )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8038a3b4680, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8036a38a9e3, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80369f77168
GetUlongFromAddress: unable to read from fffff80369f771f8
 fffff8038a3b4680 Nonpaged pool

FAULTING_IP: 
hal!HalpTimerPrepareProcessorForIdle+193
fffff803`6a38a9e3 ff15979c0200    call    qword ptr [hal!_imp_KeQueryInterruptTimePrecise (fffff803`6a3b4680)]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  0

TAG_NOT_DEFINED_c000000f:  FFFFF88002E32FB0

TRAP_FRAME:  fffff88002e2b690 -- (.trap 0xfffff88002e2b690)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000863 rbx=0000000000000000 rcx=fffff88002e2b870
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8036a38a9e3 rsp=fffff88002e2b820 rbp=fffff88002e2b880
 r8=0000000000000041  r9=00000063ad064c08 r10=fffff88002e02180
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz ac po cy
hal!HalpTimerPrepareProcessorForIdle+0x193:
fffff803`6a38a9e3 ff15979c0200    call    qword ptr [hal!_imp_KeQueryInterruptTimePrecise (fffff803`6a3b4680)] ds:fffff803`6a3b4680=e0b2040000000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80369d3a5a0 to fffff80369c79440

STACK_TEXT:  
fffff880`02e2b4a8 fffff803`69d3a5a0 : 00000000`00000050 fffff803`8a3b4680 00000000`00000000 fffff880`02e2b690 : nt!KeBugCheckEx
fffff880`02e2b4b0 fffff803`69cb3acb : 00000000`00000000 fffff803`8a3b4680 fffff880`02e0df40 00000063`ad026f22 : nt! ?? ::FNODOBFM::`string'+0x33e2a
fffff880`02e2b550 fffff803`69c76eee : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`02e2b690 : nt!MmAccessFault+0x55b
fffff880`02e2b690 fffff803`6a38a9e3 : fffff803`69f72d98 fffff803`6a38ad01 00000063`ad05b1a0 fffff803`00000000 : nt!KiPageFault+0x16e
fffff880`02e2b820 fffff803`69ccc177 : fffff880`00000001 fffffa80`18da6828 fffffa80`18da6550 00000000`00000000 : hal!HalpTimerPrepareProcessorForIdle+0x193
fffff880`02e2b8c0 fffff803`69ccbbe0 : 00000021`04f2ba68 fffffa80`18da6550 fffffa80`18da6550 fffff880`02e02180 : nt!PpmIdleExecuteTransition+0x306
fffff880`02e2bae0 fffff803`69ca298c : fffff880`02e02180 fffff880`02e02180 00000000`00000000 fffff880`02e0df40 : nt!PoIdle+0x460
fffff880`02e2bc60 00000000`00000000 : fffff880`02e2c000 fffff880`02e26000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33e2a
fffff803`69d3a5a0 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33e2a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51a966cd

BUCKET_ID_FUNC_OFFSET:  33e2a

FAILURE_BUCKET_ID:  AV_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  AV_nt!_??_::FNODOBFM::_string_

Followup: MachineOwner
---------
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2013 8:36pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics