Richo
These were related to hardware (probably memory) I would run memtest to test the memory and driver verifier to check for an underlying driver issue
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\071414-41968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\Users\Ken\Desktop
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*
http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Users\Ken\Desktop
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`5d674000 PsLoadedModuleList = 0xfffff802`5d93e2d0
Debug session time: Mon Jul 14 04:20:29.708 2014 (UTC - 4:00)
System Uptime: 1 days 4:23:15.380
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960001b5527, ffffd0004dc452e0, 0}
Probably caused by : hardware ( win32k!BltLnkRect+9d3 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960001b5527, Address of the instruction which caused the bugcheck
Arg3: ffffd0004dc452e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
These crashes were related to memory corruption (probably caused by a driver).
Please run these tests to verify your memory and find which driver is causing the problem.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.
Since it is more likely to be a driver please run verifier first.
1-Driver verifier (for complete directions see our wiki here)
If verifier does not find the issue we can move on to this.
2-Memtest. (You can read more about running memtest here)
If you cannot boot after enabling verifier reboot into safe mode
In Vista & win & (F8)
In win 8 http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-windows-8-the-easy-way/
Co-Authored by JMH3143
.