Random BSOD... After installing Win 8.1

darrenwj · Sep 29, 2014

I had a stable computer running Win 8 and after the Win 8.1 update I started having random crashes. I replaced the memory because one of the error codes led me to think the memory could be bad. That didn't fix anything. It seems to occur once or twice a day randomly. It can happen in a game, on the net or when it's idle. I have done enough research to know that it is probably a driver issue and have even reinstalled Win 8.1 and all new drivers. That did help a little. Before it was crashing twice as much. But even after a clean install I still get the random BSOD. I don't know how to understand the dump files and have been watching posts in here but all to no avail. I can use any help I can get at this point.
Thanks in advance.

blueelvis · Oct 1, 2014

Hi Darrenwj & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

Code:

7: kd> k
Child-SP          RetAddr           Call Site
ffffd001`d1ba3538 fffff803`c87d67e9 nt!KeBugCheckEx
ffffd001`d1ba3540 fffff803`c87d503a nt!KiBugCheckDispatch+0x69
ffffd001`d1ba3680 fffff803`c86f9dfd nt!KiPageFault+0x23a
ffffd001`d1ba3810 fffff803`c86afca3 nt!MiUnlinkPageFromLockedList+0x1bd
ffffd001`d1ba38a0 fffff803`c8a2261f nt!MiDeleteSegmentPages+0x203
ffffd001`d1ba3950 fffff803`c86af79c nt!MiSegmentDelete+0x57
ffffd001`d1ba3990 fffff803`c8a67ec4 nt!MiCheckControlArea+0x1ac
ffffd001`d1ba39f0 fffff803`c86c691f nt!ObpRemoveObjectRoutine+0x64
ffffd001`d1ba3a50 fffff801`46a3d732 nt!ObfDereferenceObject+0x8f
ffffd001`d1ba3a90 fffff803`c86b3a2b [B][U]dxgmms1!VidMmProcessAsyncOperation+0x1a[/U][/B]
ffffd001`d1ba3ad0 fffff803`c8750514 nt!ExpWorkerThread+0x293
ffffd001`d1ba3b80 fffff803`c87d12c6 nt!PspSystemThreadStartup+0x58
ffffd001`d1ba3be0 00000000`00000000 nt!KiStartSystemThread+0x16

It seems that your Display Driver is causing problem as there is Direct X Involved. But in the rest of the dump files, there is memory corruption which has been blamed. Below is a list of 3rd party drivers present on your system :-

Code:

**************************Mon Sep 29 03:42:14.607 2014 (UTC + 5:30)**************************
[B][U]SnakeEyes.sys               Wed Sep  5 11:01:26 2012 (5046E3AE)
tib_mounter.sys             Thu Dec 27 18:55:05 2012 (50DC4C31)
[/U][/B]snapman.sys                 Wed Jan 16 19:14:06 2013 (50F6AEA6)
fltsrv.sys                  Fri Mar  1 19:23:39 2013 (5130B2E3)
ALSysIO64.sys               Wed Mar  6 03:20:34 2013 (513668AA)
tib.sys                     Wed Mar 20 14:30:38 2013 (51497AB6)
PLTGC.sys                   Fri Apr 12 14:15:13 2013 (5167C999)
Rt630x64.sys                Fri May 10 15:29:08 2013 (518CC4EC)
xhcdrv.sys                  Mon Aug 12 08:42:38 2013 (520852A6)
ViaHub3.sys                 Mon Aug 12 08:42:43 2013 (520852AB)
CM10664.sys                 Fri Jan 17 09:14:46 2014 (52D8A72E)
AODDriver2.sys              Tue Feb 11 16:36:52 2014 (52FA044C)
AMDACPKSL.SYS               Wed Mar 12 05:19:44 2014 (531FA118)
AtihdWB6.sys                Wed Mar 12 05:20:02 2014 (531FA12A)
atikmpag.sys                Fri Apr 18 06:37:07 2014 (53507ABB)
amdacpksd.sys               Fri Apr 18 07:24:17 2014 (535085C9)
atikmdag.sys                Fri Apr 18 07:43:16 2014 (53508A3C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 28 09:14:36.932 2014 (UTC + 5:30)**************************
MpKsl1ee76182.sys           Thu Aug 22 04:21:16 2013 (52154464)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 16 23:59:56.546 2014 (UTC + 5:30)**************************
agp440.sys                  Thu Aug 22 17:09:35 2013 (5215F877)
nv_agp.sys                  Thu Aug 22 17:09:38 2013 (5215F87A)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep  9 03:41:01.065 2014 (UTC + 5:30)**************************
speedfan.sys                Sun Dec 30 02:29:35 2012 (50DF59B7)

darrenwj · Oct 2, 2014

Thanks for the welcome and the help. This forum is a wealth of information.
Here is the memory dump file link:
MEMORY

You said the "It seems that your Display Driver is causing problem as there is Direct X Involved." Any suggestions on how to handle that? It is an ATI card with the Catalyst Control Center. I had the past version installed and then updated to the newest version with the same BSOD result.

blueelvis · Oct 6, 2014

Hi Darrenwj ^_^,

I apologize for the delayed response but we have been very busy

I have analysed your dump file and below has been provided an analysis of the same for informative purposes :-

Code:

7: 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: fffffc0009c1a32b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff803c86f9dfd, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 fffffc0009c1a32b 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!MiUnlinkPageFromLockedList+1bd
fffff803`c86f9dfd 0fb6461b        movzx   eax,byte ptr [rsi+1Bh]
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  AV
PROCESS_NAME:  System
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
TRAP_FRAME:  ffffd001d1ba3680 -- (.trap 0xffffd001d1ba3680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000bedc5 rbx=0000000000000000 rcx=fffff803c89c42a8
rdx=00000008003408bb rsi=0000000000000000 rdi=0000000000000000
rip=fffff803c86f9dfd rsp=ffffd001d1ba3810 rbp=ffffd001d1ba3878
 r8=00000000002b470f  r9=00000000000be5c5 r10=0000000000000005
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiUnlinkPageFromLockedList+0x1bd:
fffff803`c86f9dfd 0fb6461b        movzx   eax,byte ptr [rsi+1Bh] ds:00000000`0000001b=??
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff803c87d67e9 to fffff803c87caca0
STACK_TEXT:  
ffffd001`d1ba3538 fffff803`c87d67e9 : 00000000`0000000a fffffc00`09c1a32b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd001`d1ba3540 fffff803`c87d503a : 00000000`00000000 fffffa80`096a7340 00000000`00000000 ffffd001`d1ba3680 : nt!KiBugCheckDispatch+0x69
ffffd001`d1ba3680 fffff803`c86f9dfd : 00000000`00000000 fffffa80`0cbd09a8 00000000`00000001 fffff803`c872f1ca : nt!KiPageFault+0x23a
ffffd001`d1ba3810 fffff803`c86afca3 : fffffa80`00000005 00000000`00002001 00000000`00000000 00411b36`00000005 : nt!MiUnlinkPageFromLockedList+0x1bd
ffffd001`d1ba38a0 fffff803`c8a2261f : ffffe000`d8fa3720 00000000`00002000 ffffe000`00002001 fffffa80`093f0900 : nt!MiDeleteSegmentPages+0x203
ffffd001`d1ba3950 fffff803`c86af79c : 00000000`00000002 ffffd001`d1ba39c0 ffffe000`d7926610 fffff803`c86b6cb6 : nt!MiSegmentDelete+0x57
ffffd001`d1ba3990 fffff803`c8a67ec4 : 00000000`00000000 00000000`00000000 ffffe000`d7926610 ffffc000`d9ec1030 : nt!MiCheckControlArea+0x1ac
ffffd001`d1ba39f0 fffff803`c86c691f : 00000000`00000000 ffffd001`d1ba3b50 ffffc000`d9ec1060 ffffe000`dc47b740 : nt!ObpRemoveObjectRoutine+0x64
ffffd001`d1ba3a50 fffff801`46a3d732 : ffffe000`dc678130 ffffe000`dc678130 fffff803`c891a300 ffffe000`dc47b740 : nt!ObfDereferenceObject+0x8f
ffffd001`d1ba3a90 fffff803`c86b3a2b : fffff803`c8743610 00000000`00000000 00000000`00000000 ffffe000`dc47b740 : dxgmms1!VidMmProcessAsyncOperation+0x1a
ffffd001`d1ba3ad0 fffff803`c8750514 : 000001e2`01904404 ffffe000`dc47b740 ffffe000`dc47b740 ffffe000`d7886900 : nt!ExpWorkerThread+0x293
ffffd001`d1ba3b80 fffff803`c87d12c6 : ffffd001`c86c1180 ffffe000`dc47b740 ffffe000`d7871040 ffffd001`c8642180 : nt!PspSystemThreadStartup+0x58
ffffd001`d1ba3be0 00000000`00000000 : ffffd001`d1ba4000 ffffd001`d1b9d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb
FOLLOWUP_IP: 
dxgmms1!VidMmProcessAsyncOperation+1a
fffff801`46a3d732 8b050877feff    mov     eax,dword ptr [dxgmms1!Microsoft_Windows_DxgKrnlEnableBits (fffff801`46a24e40)]
SYMBOL_STACK_INDEX:  9
SYMBOL_NAME:  dxgmms1!VidMmProcessAsyncOperation+1a
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME:  dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  53183e46
IMAGE_VERSION:  6.3.9600.17041
BUCKET_ID_FUNC_OFFSET:  1a
FAILURE_BUCKET_ID:  AV_dxgmms1!VidMmProcessAsyncOperation
BUCKET_ID:  AV_dxgmms1!VidMmProcessAsyncOperation
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:av_dxgmms1!vidmmprocessasyncoperation
FAILURE_ID_HASH:  {b8b06ff0-882d-e744-5814-78f3632ff15e}
Followup: MachineOwner
---------

Again, in this case as well, the Direct X was blamed which means probably it is related to your ATI Driver. The bugcheck was caused while unlinking Pages from the Locked List.

Please run Display Driver Uninstaller from this **LINK** and then completely remove your ATI Driver. Once it is removed, restart your machine and see if it gives BSOD's or not. If it does not give any BSOD then install the drivers which were provided with the GPU in the Media Disc.

Let me know how it goes ^_^

darrenwj · Oct 22, 2014

I followed your instructions and had a few issues. First after I wiped the GPU driver and software, Win8.1 automatically reinstalled is so I had to do it again. At that point, having no drivers, I really couldn't do much as far as playing games which is probably 50% of my time on the PC. I let it stay on for 24hrs and then saw a new driver/ software package was just released from ATI so I downloaded and installed it with no issues. MY PC stayed up for 4 days with no issue and then BSOD. I have been leaving my PC on purposely to test how frequently this happens and so far it is about every two days. Thats an improvement from where I started but it sure would be nice if it didn't do it at all. And, it doesn't always take two days, I did see a BSOD recently after only being on for about 8 hrs. Any more thoughts?

blueelvis · Oct 25, 2014

Hi ^_^,

Glad to see that your system is improving

Let us make it like new now. I would suggest you to run the Furmark according to these instructions (make sure that this time you have your ATI Driver installed from the Manufacturer after running DDU to clean the installed driver) -
FurMark Video Stress Test - free from here: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test (Looks like it's "BURN-IN test" now)
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
If the temperature gets above 100ºC, quit the test - the video card is overheating.
- Click "Quit" to exit[/quote]
What you are looking for:
- excessive heat from the GPU (report back with anything over 90ºC)
- problems with the video display (picture is distorted or jumbled, picture turns black, etc)
- problems reported by the program (I haven't seen this, but "just in case")

Let me know the temperatures of the GPU when IDLE & When under LOAD. Let me know the results ^_^.

darrenwj · Oct 25, 2014

I ran it for an hour and half. Idle temp is 46C and it hit 85C and stayed at 84-85C. I also watch a video for about 45 of the 90 minutes I was running Furmark. There were no issues at all. I had Furmark set to 1920x1080 and it ran the GPU at 100%. I left that on my main display and watched the video on my secondary display. The video I watched was a little choppy but other than that every thing ran fine.

blueelvis · Oct 29, 2014

Hi ^_^,

I am extremely sorry for the delay. I just reached college and I have been completing assignments since 2 days now. I will reply today once I am back to my room.

-Pranav

blueelvis · Oct 29, 2014

Kindly upload a freshly generated SF Diagnostic ZIP File so that it includes the dump files from the latest crashes so that those could be analysed ^_^

darrenwj · Oct 31, 2014

I attached a new SF_Dump and uploaded a new Windows Memory Dump to MediaFire HERE. I was waiting for it to crash again to send the dump files and it crashes twice yesterday. Hopefully this can be figured out. Thanks for your help.

Random BSOD... After installing Win 8.1

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

OMG Debugger!

My Computer

New Member

My Computer