V Vir Gnarus BSOD Kernel Dump Analyst Joined Mar 2, 2012 Posts 469 Jun 1, 2012 #41 Yes, you'll need to install the ATI APP SDK as ATI drivers do not come with OpenCL, unlike Nvidia. You'll have to get it through installing the SDK. Anyways, how many passes did you run of Memtest86+? I ask because I looked back on the kernel dump you provided and noticed this: Code: 0: kd> !memusage 0x8 loading PFN database loading (100% complete) Compiling memory usage data (99% Complete). Zeroed: 1777 ( 7108 kb) Free: 5 ( 20 kb) Standby: 580316 (2321264 kb) Modified: 15540 ( 62160 kb) ModifiedNoWrite: 0 ( 0 kb) Active/Valid: 442508 (1770032 kb) Transition: 2 ( 8 kb) Bad: 13 ( 52 kb) Unknown: 0 ( 0 kb) TOTAL: 1040148 (4160592 kb) That shouldn't happen. It means Windows detected failed RAM when attempting to allocate, and therefore marked them as bad, much like CHKDSK when it marks hard drive sectors as bad to prevent further attempts at using them. I'd personally like to see one more kernel dump from you to correlate this discovery, but for now it looks like we're dealing with memory issues. However, this can also be attributed to motherboard problems or PSU issues. Windows cannot discern the cause for why the RAM failed during allocation attempt, only that it did. There is a very slim chance that a program called MmMarkPhysicalMemoryAsBad in order to restrain other threads from looking at the allocations while it fiddles with em, but I doubt it, especially given that I looked through all running processes (using !stacks 0 MmMarkPhysicalMemoryAsBad) and no threads came up showing that they have that function in their callstack, so nothing appears to have called it on purpose. I am most certain we're dealing with hardware malfunctioning now.