New
#21
Okay, open the case and then check for any dust which may have build up inside the fans and heatsinks. I would also suggest removing the side panel when running the test.
Okay, open the case and then check for any dust which may have build up inside the fans and heatsinks. I would also suggest removing the side panel when running the test.
Here's the latest after installing a new video card.
Code:BugCheck C1, {fffff9803400ae10, fffff9803400a1bd, 9901f0, 32} Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )Code:Usual causes: Device driver, MemoryThis bugcheck indicates that a driver has caused a single bit form of memory corruption within the Slop Bytes region of a pool page. The Special Pool option of Driver Verifier gives each driver it's own individual pool page, which is then split into Slop Bytes and then the driver's pool allocation. The next virtual page is a Guard Page to detect Buffer Overflows, although since the problem seems to have occurred within the Slop Bytes, then the error isn't to do with a Buffer Overflow, but a different form of memory corruption. The Slop Bytes are a repeating pattern, and if this pattern is disrupted, then the system will bugcheck with the same error as you have at the moment.Code:2: kd> dt nt!_POOL_HEADER fffff9803400a000 +0x000 PreviousSize : 0y11110000 (0xf0) <-- Should have been 0 +0x000 PoolIndex : 0y00000001 (0x1) +0x000 BlockSize : 0y10011001 (0x99) +0x000 PoolType : 0y00000000 (0) <-- Non-Paged Pool +0x000 Ulong1 : 0x9901f0 +0x004 PoolTag : 0x2b707249 +0x008 ProcessBilled : (null) +0x008 AllocatorBackTraceIndex : 0 +0x00a PoolTagHash : 0
Unfortunately, the call stack doesn't reveal much and either does the dump file, but a good step to take would be to download and run Autoruns and then save the output as a .ARN file. Place this file into a zipped folder and then upload in your next post.
Got the pc back from the guys who made and 3 hours in had yet another blue screen. The techs who had it said there were some overclocks enabled in the bios (which they disabled).
Sorry for my absence, I've been ill most of this week.
Code:BugCheck D1, {fffffffffffffff8, 5, 0, fffff8800519047c} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+e947c )Do you have the latest WHQL driver installed?Code:0: kd> lmvm nvlddmkm start end module name fffff880`050a7000 fffff880`05b9e000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Thu Sep 12 06:16:00 2013 (52314E10) CheckSum: 00AC9E83 ImageSize: 00AF7000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Version: 327.23
Release Date for Desktops and Notebooks : September 19th 2013
In Device Manager: 9.18.13.2723Code:0: kd> k # Child-SP RetAddr Call Site 00 fffff800`00b9c5f8 fffff800`032c0169 nt!KeBugCheckEx 01 fffff800`00b9c600 fffff800`032bede0 nt!KiBugCheckDispatch+0x69 02 fffff800`00b9c740 fffff880`0519047c nt!KiPageFault+0x260 <-- Page Fault at IRQL Level 5? 03 fffff800`00b9c8d0 00000000`00000000 nvlddmkm+0xe947cCode:0: kd> !irql Debugger saved IRQL for processor 0x0 -- 5
I went to I nvidia and updated to the latest release. There was a beta, but thought I'd stick with the release version.
Good idea and thanks :)
The company sent me a new vid card and new memory...still getting the bsods.
Tim