Thanks for the quick reply.
I have already completed a few of those requested task earlier.
sfc /scannow reported no issues.
chkdsk /f and /r found no issues.
Though I did not use memtest86+, the Windows 7 Memory Diagnostic Tool found no issues with the RAM after 6 passes.
I ran the Dell Hardware Diagnostic Tool that is provided when you first power on the laptop. It found no issues.
The CPU temp reports around 50-60c.
I will try to follow through with additional test as you suggested.
This is the output of the memory.dmp as provided by windbg if it helps. I didn't upload the file because of its size.
Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\System32\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: .sympath cache*;srv*
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.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e66000 PsLoadedModuleList = 0xfffff800`030aa670
Debug session time: Thu Jul 4 10:08:06.180 2013 (UTC - 4:00)
System Uptime: 0 days 0:03:41.023
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
...
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\user.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {d23b, 2, 1, fffff80002f0be45}
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000000d23b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002f0be45, address which referenced memory
Debugging Details:
------------------
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
WRITE_ADDRESS: 000000000000d23b
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeStackAttachProcess+115
fffff800`02f0be45 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880035f5770 -- (.trap 0xfffff880035f5770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=fffffa800701bbb0
rdx=fffff880035f5a58 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f0be45 rsp=fffff880035f5900 rbp=fffff880035f5a58
r8=fffffa800701bba0 r9=0000000000000130 r10=fffff880033660c0
r11=fffffa800701bb50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeStackAttachProcess+0x115:
fffff800`02f0be45 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax ds:00000000`000000dc=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002edb1e9 to fffff80002edbc40
STACK_TEXT:
fffff880`035f5628 fffff800`02edb1e9 : 00000000`0000000a 00000000`0000d23b 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`035f5630 fffff800`02ed9e60 : fffff880`035f57b0 fffff8a0`037205b0 00000000`000000c2 fffffa80`0701bb50 : nt!KiBugCheckDispatch+0x69
fffff880`035f5770 fffff800`02f0be45 : 00000000`00000000 fffffa80`0701bb50 fffffa80`0701bb50 fffff800`031b12af : nt!KiPageFault+0x260
fffff880`035f5900 fffffa80`0aa809c8 : fffff880`035f5a80 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeStackAttachProcess+0x115
fffff880`035f5980 fffff880`035f5a80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0aa809c8
fffff880`035f5988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`035f5a80
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeStackAttachProcess+115
fffff800`02f0be45 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeStackAttachProcess+115
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935
FAILURE_BUCKET_ID: X64_0xA_nt!KeStackAttachProcess+115
BUCKET_ID: X64_0xA_nt!KeStackAttachProcess+115
Followup: MachineOwner
---------
