Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Randomly occurring, no longer creating dump files. 0x000000d1c5

02 Jan 2015   #1
Andeh

Windows 7 Home Prem x64
 
 
BSOD Randomly occurring, no longer creating dump files. 0x000000d1c5

Hello all,

I've just rebuilt my computer with a new Mobo, CPU and GPU. The specs are in my profile. I've used my existing drives, PSU and some RAM from another project, along with a clean install of x64 7 Home Prem.

I've had intermittent bluescreens from day one (three days ago), and reinstalled the drivers many times. Each bluescreen error is different, but only the first couple actually created dump files, now they're not any more. I've included the two dump files my PC has created.

The bluescreens occur randomly, and I've stress tested the computer and GPU many times, and all seems fine under load. I've gamed on it and used it normally, and the screens can occur doing either. If I leave the computer turned on other night, I'll probably come back to a BSOD. Each time the error name is different.

Any help would really be appreciated, I've never had such a frustrating problem.

I should add I've just gone from a single monitor, back to two after buying the correct HDMI to DVI cable, and now the BSODs are much more frequent, so gone back to one for now.


My System SpecsSystem Spec
.
07 Jan 2015   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Hello Andeh,

Is the firmware for your SSD up to date?

Code:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\LIONEL_HUTZ-02_01_2015_193237_73\123014-7956-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`03043890
Debug session time: Tue Dec 30 18:41:16.962 2014 (UTC + 6:00)
System Uptime: 0 days 0:04:15.117
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff88034203bb0, 2, 1, fffff88011202753}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+145753 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88034203bb0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88011202753, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ad100
GetUlongFromAddress: unable to read from fffff800030ad1c0
 fffff88034203bb0 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
atikmdag+145753
fffff880`11202753 001d57140023    add     byte ptr [fffff880`34203bb0],bl

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

TRAP_FRAME:  fffff880020ccbb0 -- (.trap 0xfffff880020ccbb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa8008c78000
rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88011202753 rsp=fffff880020ccd48 rbp=0000000000000000
 r8=fffff8801120273b  r9=fffff880110bd000 r10=fffff8801130c9a0
r11=fffff880112a90d3 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
atikmdag+0x145753:
fffff880`11202753 001d57140023    add     byte ptr [fffff880`34203bb0],bl ds:fffff880`34203bb0=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e75169 to fffff80002e75bc0

STACK_TEXT:  
fffff880`020cca68 fffff800`02e75169 : 00000000`0000000a fffff880`34203bb0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`020cca70 fffff800`02e73de0 : 00000000`00004b11 00000000`00000000 00000000`00000000 fffffa80`08c78000 : nt!KiBugCheckDispatch+0x69
fffff880`020ccbb0 fffff880`11202753 : fffff880`1123738c fffff880`020ccdc8 fffff880`111bf4a5 fffff880`020ccff0 : nt!KiPageFault+0x260
fffff880`020ccd48 fffff880`1123738c : fffff880`020ccdc8 fffff880`111bf4a5 fffff880`020ccff0 fffff880`04785c00 : atikmdag+0x145753
fffff880`020ccd50 fffff880`020ccdc8 : fffff880`111bf4a5 fffff880`020ccff0 fffff880`04785c00 fffffa80`088a7a20 : atikmdag+0x17a38c
fffff880`020ccd58 fffff880`111bf4a5 : fffff880`020ccff0 fffff880`04785c00 fffffa80`088a7a20 fffff880`020ccff0 : 0xfffff880`020ccdc8
fffff880`020ccd60 fffff880`020ccff0 : fffff880`04785c00 fffffa80`088a7a20 fffff880`020ccff0 fffff880`04785c00 : atikmdag+0x1024a5
fffff880`020ccd68 fffff880`04785c00 : fffffa80`088a7a20 fffff880`020ccff0 fffff880`04785c00 fffff880`111bd255 : 0xfffff880`020ccff0
fffff880`020ccd70 fffffa80`088a7a20 : fffff880`020ccff0 fffff880`04785c00 fffff880`111bd255 fffff880`020ccff0 : 0xfffff880`04785c00
fffff880`020ccd78 fffff880`020ccff0 : fffff880`04785c00 fffff880`111bd255 fffff880`020ccff0 00000000`00000000 : 0xfffffa80`088a7a20
fffff880`020ccd80 fffff880`04785c00 : fffff880`111bd255 fffff880`020ccff0 00000000`00000000 fffff880`020ccff0 : 0xfffff880`020ccff0
fffff880`020ccd88 fffff880`111bd255 : fffff880`020ccff0 00000000`00000000 fffff880`020ccff0 00000000`00000000 : 0xfffff880`04785c00
fffff880`020ccd90 fffff880`020ccff0 : 00000000`00000000 fffff880`020ccff0 00000000`00000000 00000002`00000010 : atikmdag+0x100255
fffff880`020ccd98 00000000`00000000 : fffff880`020ccff0 00000000`00000000 00000002`00000010 00000000`00000000 : 0xfffff880`020ccff0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+145753
fffff880`11202753 001d57140023    add     byte ptr [fffff880`34203bb0],bl

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+145753

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  546ea3c3

FAILURE_BUCKET_ID:  X64_0xD1_atikmdag+145753

BUCKET_ID:  X64_0xD1_atikmdag+145753

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_atikmdag+145753

FAILURE_ID_HASH:  {b512b5be-24ea-cefc-2f6e-4ef80b5d9b7a}

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

2: kd> lmvm atikmdag
start             end                 module name
fffff880`110bd000 fffff880`12341000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Nov 21 08:30:27 2014 (546EA3C3)
    CheckSum:         0121F198
    ImageSize:        01284000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\LIONEL_HUTZ-02_01_2015_193237_73\123014-12620-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309d890
Debug session time: Tue Dec 30 23:32:38.362 2014 (UTC + 6:00)
System Uptime: 0 days 4:08:08.517
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {fffffffffffffff2, 2, 0, fffff80003003123}

Probably caused by : NETIO.SYS ( NETIO!FreeConditions+92 )

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

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: fffffffffffffff2, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80003003123, address which referenced memory

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


BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExFreePoolWithTag+43
fffff800`03003123 418b45f0        mov     eax,dword ptr [r13-10h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

TRAP_FRAME:  fffff88007c4d470 -- (.trap 0xfffff88007c4d470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003003123 rsp=fffff88007c4d600 rbp=fffffa8007157cd0
 r8=fffffa800bb08c90  r9=0000000000000020 r10=fffff88002f65a60
r11=fffffa80075a0ef0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!ExFreePoolWithTag+0x43:
fffff800`03003123 418b45f0        mov     eax,dword ptr [r13-10h] ds:ffffffff`fffffff0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ecf169 to fffff80002ecfbc0

STACK_TEXT:  
fffff880`07c4d328 fffff800`02ecf169 : 00000000`0000000a ffffffff`fffffff2 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07c4d330 fffff800`02ecdde0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`071626c0 : nt!KiBugCheckDispatch+0x69
fffff880`07c4d470 fffff800`03003123 : fffffa80`0b2ac2e0 00000000`00000070 00000000`00000000 00000000`000007ff : nt!KiPageFault+0x260
fffff880`07c4d600 fffff880`01588ea1 : badbadfa`badbadfa fffffa80`06c81b98 00000000`48706657 fffffa80`06c81b98 : nt!ExFreePoolWithTag+0x43
fffff880`07c4d6b0 fffff880`015910e5 : fffffa80`09fa06d0 fffffa80`06c81b98 00000000`0000000b fffffa80`06c81b98 : NETIO!FreeConditions+0x92
fffff880`07c4d6e0 fffff880`0158ff9d : fffffa80`09fa06f0 00000000`00000000 fffff880`07c4d7c0 fffff880`07c4d7c0 : NETIO!FreeCacheEntry+0x95
fffff880`07c4d720 fffff880`01591176 : fffff880`07c4d7c0 00000000`00000000 00000000`00000000 fffffa80`06c81b98 : NETIO!FreeSomeCacheBucketEntries+0x6d
fffff880`07c4d770 fffff880`0158362e : fffffa80`06c81b98 00000000`00000000 00000000`00020004 00000000`00000000 : NETIO!FreeSomeCacheEntries+0x36
fffff880`07c4d7a0 fffff880`0158fc19 : 00000000`00000000 fffff880`01000003 00000000`00000009 00000000`00000010 : NETIO!UpdateCacheLruBucket+0x1de
fffff880`07c4d7e0 fffff880`01590a5e : 00000000`00000000 00000000`00000012 fffffa80`07dda660 00000000`00000090 : NETIO!WfpActivateCaches+0x52
fffff880`07c4d820 fffff880`01591274 : fffffa80`080000ff fffffa80`0853d180 fffffa80`07951628 00000000`00000000 : NETIO!KfdCommitTransaction+0x197
fffff880`07c4d860 fffff880`016100bb : fffffa80`079515f0 fffffa80`0853d180 fffffa80`0949f2c0 00000000`00000001 : NETIO!IoctlKfdCommitTransaction+0x54
fffff880`07c4d890 fffff800`031ece67 : fffffa80`0949f2c0 fffff880`07c4db60 fffffa80`0949f2c0 fffffa80`079515f0 : tcpip!KfdDispatchDevCtl+0x6b
fffff880`07c4d8d0 fffff800`031ed6c6 : fffff880`07c4dab8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`07c4da00 fffff800`02ecee53 : fffff880`07c4db60 fffffa80`08cce120 fffff880`07c4dab8 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`07c4da70 00000000`77b7132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`009ae878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b7132a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!FreeConditions+92
fffff880`01588ea1 4c8923          mov     qword ptr [rbx],r12

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NETIO!FreeConditions+92

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  5294760d

IMAGE_VERSION:  6.1.7601.18327

FAILURE_BUCKET_ID:  X64_0xC5_2_NETIO!FreeConditions+92

BUCKET_ID:  X64_0xC5_2_NETIO!FreeConditions+92

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc5_2_netio!freeconditions+92

FAILURE_ID_HASH:  {e8a84e23-940e-5eea-53da-242d14948bbe}

Followup: MachineOwner
---------
My System SpecsSystem Spec
07 Jan 2015   #3
Andeh

Windows 7 Home Prem x64
 
 

koolkat77,

It wasn't but I have now updated it. Thank you. I also discovered from my Mobo manual that the RAM I was using wasn't officially supported, (despite it being just one letter different to a model that was), and as such I've swapped it out for 2x4GB sticks of some supported Corsair RAM.

Will see how stable this new configuration is.
My System SpecsSystem Spec
.

12 Jan 2015   #4
Andeh

Windows 7 Home Prem x64
 
 

For future reference, (since I hate googling problems and not finding an answer!) the computer has now been stable for six days using the new compatible RAM. No BSODs or other errors, so I think it's sorted.
My System SpecsSystem Spec
Reply

 BSOD Randomly occurring, no longer creating dump files. 0x000000d1c5




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Randomly for over a year, recently starting getting dump files
Hello, I have just returned home to my desktop (Used my laptop at school) and it is still having blue screen problems. I have had this computer for over a year, and ever since I built it, it randomly blue screened. I have changed the memory and ran memtest(Like a year ago but i did it), I...
BSOD Help and Support
BSODs but no longer seem to create dump files
First, let me say that the info on this site is a tremendous resource. You guys are great to run this. I started getting kernal_data_inpage_error BSODs about a month ago. I found your site and found minidumps were being created in c:\windows\minidump\ just like the site indicated. For the...
BSOD Help and Support
Random BSOD, no pattern and not creating dump files.
Hi all, I wonder if someone can help? My PC crashes quite randomly, it doesn't seem to be when I'm doing anything specific or with any particular app or task. Thanks in advance for any help.
BSOD Help and Support
Event ID 41 Randomly Reboots without BSOD or Dump files
Hi eveyone! This is my first post here due to the fact that I recently registered. I've noticed alot of posts regarding event ID 41 issues and I am posting here because I am going crazy trying to figure out why the computer randomly reboots and the community here seems very helpful. I...
BSOD Help and Support
BSOD, seems to be occurring randomly.
Hi everyone, recently upgraded my hard drive to an SSD and added a new graphics card. Did a fresh windows 7 install and seem to be getting an occasional BSOD. Have attached zipped diagnostics file. Cheers, Allan
BSOD Help and Support
BSOD occurring randomly
Ran Memtest86+ but no errors were detected; I've also tried updating a few drivers but so far nothing's worked. Sometimes I get the BSOD; other times my computer just restarts randomly. I don't remember installing anything recently that could be the cause of this. I run Windows 7 Home Premium...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:41.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App