BSOD and Display Driver crash playing Dota 2

soulspirit · 20 Mar 2015

Okay,I appreciate all the help you have given me,I will carry out the steps and see how it goes.
Again,thank you for the help.

soulspirit · 24 Mar 2015

Sorry for the late reply,but I sent my computer to a PC repair store for 3 days to fix the problem.They had the PC for 3 days,and said that there were no problems,or BSODs when they checked.So I got my PC today and I tried to play Dota,I was able to play 3 matches straight,and then just as I enter the next match,another BSOD.So I re seated the GPU as you said and when I booted up my PC CHKDSK ran(It ran automatically just after I re seated the GPU) and found no errors.I don't think I can change the GPU slot as it doesn't fit to the other 2 slots.But I've re seated it and I'll see if any moer BSODs occur.

EDIT:Also I'd like to add that,once I got the BSOD and the computer restarts,i keep on getting more and more,and it won't stop unless I leave it shut down for a few hours.So now I'm getting more frequent BSODs.

Boozad · 24 Mar 2015

Can you upload logs including the latest dump file please mate.

soulspirit · 25 Mar 2015

Attachment 353739

Boozad · 25 Mar 2015

All of the latest dumps are indicating hardware problems and/or blaming your nVidia drivers so it has to be the card. Have you had any BSODs since reseating it?

soulspirit · 25 Mar 2015

Yes,I've had BSODs,and it's more frequent,one after another.I've never had a problem with the nvidia driver before,and since I'm having too many BSODs,and barely being able to use the computer,I was thinking of reformatting windows.Do you think that should solve it?

Boozad · 25 Mar 2015

It may do, it may not. What I'd suggest if you do go that route is removing the card prior to the clean install and run the system without it in first to see if everything is stable, then when you're happy all's good install the card and test. If you want to upload any new logs feel free and I'll take a look at them later for you.

soulspirit · 26 Mar 2015

Before I reformat my computer I just wanted to do some more tests,so I uninstalled nVidia to see if I get any BSODs,which I did,about after 5 matches in Dota today,and I ran Driver Verifier and got a BSOD,so I was hoping you could look into the recent logs.These are all dump files created today,and the most recent one is when I was running driver verifier.Also I will run memtest86+ tonight to see if anything might be wrong with my RAM.
Attachment 353887

Boozad · 26 Mar 2015

Go ahead and run MemTest86+, it certainly won't hurt but I don't think your RAM is the issue.

Looking at the DV enable BSOD it gives the following readout:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 000000000000000f, DMA map register corruption.
Arg2: 0000000000000003, Free map register was overwritten.
Arg3: fffff880033e4288, Corruption address. Expected fill pattern is 0x0F.
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xE6

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE:  FFFFF88002F22FB0

LAST_CONTROL_TRANSFER:  from fffff8000455e4ec to fffff800040ceec0

STACK_TEXT:  
fffff880`02f1b8d8 fffff800`0455e4ec : 00000000`000000e6 00000000`0000000f 00000000`00000003 fffff880`033e4288 : nt!KeBugCheckEx
fffff880`02f1b8e0 fffff800`045687d2 : fffff800`0455c960 00000000`00000004 00000000`00000065 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`02f1b920 fffff800`045698e4 : 00000000`00000000 00000000`0000a974 00000000`00000001 00000000`00000000 : nt!ViHalReportIssueWithOptions+0x1a2
fffff880`02f1b970 fffff800`0457af30 : 00000000`00000000 00000000`00000001 fffffa80`051aebd8 fffffa80`051aebb8 : nt!ViCheckPadding+0x124
fffff880`02f1b9c0 fffff800`0457b8b8 : fffffa80`051e8b70 00000000`00000002 fffffa80`0666ba00 fffff880`02f1bb60 : nt!ViFreeMapRegisterFile+0x190
fffff880`02f1ba30 fffff880`00fd4199 : fffffa80`051e7e60 fffff980`64ba8b80 fffffa80`00000000 00000000`00000004 : nt!VfPutScatterGatherList+0x208
fffff880`02f1bab0 fffff880`00ddb46f : fffffa80`0396e8e0 00000000`00000006 fffffa80`049f93f0 00000000`00000000 : PCIIDEX!BmFlush+0x25
fffff880`02f1bae0 fffff880`00ddb120 : fffffa80`049f81a0 00000000`00000000 fffffa80`049f81a0 fffff980`64ba8b80 : ataport!IdeProcessCompletedRequests+0x123
fffff880`02f1bc10 fffff800`040da7ac : fffff880`009ea180 00000000`4344f9b3 fffffa80`049f8050 fffffa80`049f8118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02f1bcd0 fffff800`040c6bca : fffff880`009ea180 fffff880`009f4f40 00000000`00000000 fffff880`00ddaf78 : nt!KiRetireDpcList+0x1bc
fffff880`02f1bd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
PCIIDEX!BmFlush+25
fffff880`00fd4199 4883a3e003000000 and     qword ptr [rbx+3E0h],0

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  PCIIDEX!BmFlush+25

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PCIIDEX

IMAGE_NAME:  PCIIDEX.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc114

IMAGE_VERSION:  6.1.7600.16385

FAILURE_BUCKET_ID:  X64_0xE6_VRF_PCIIDEX!BmFlush+25

BUCKET_ID:  X64_0xE6_VRF_PCIIDEX!BmFlush+25

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xe6_vrf_pciidex!bmflush+25

FAILURE_ID_HASH:  {f4c18766-a5b0-3e18-b73c-212ed4d12db1}

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

1: kd> lmvm PCIIDEX
start             end                 module name
fffff880`00fd3000 fffff880`00fe3000   PCIIDEX    (pdb symbols)          c:\symbols\pciidex.pdb\2C4F146DA2774ACEA1D5499284DDDB271\pciidex.pdb
    Loaded symbol image file: PCIIDEX.SYS
    Mapped memory image file: c:\symbols\PCIIDEX.SYS\4A5BC11410000\PCIIDEX.SYS
    Image path: \SystemRoot\system32\drivers\PCIIDEX.SYS
    Image name: PCIIDEX.SYS
    Timestamp:        Tue Jul 14 00:19:48 2009 (4A5BC114)
    CheckSum:         00019CC5
    ImageSize:        00010000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     pciidex.sys
    OriginalFilename: pciidex.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  PCI IDE Bus Driver Extension
    LegalCopyright:   © Microsoft Corporation. All rights reserved

Do you have onboard graphics you can use? If so, can you uninstall the nVidia GPU and physically remove it from your PC and test the system. I'm of the opinion that it may be your PCI-e slot on your motherboard that's causing the issue.

soulspirit · 27 Mar 2015

I ran memtest and got 11 passes with no errors.If I remove my GPU,where would I connect my monitor cable?Sorry but I'm not really good at computing.
Although you said something might be wrong with the GPU,I thought it was something related to a driver/software that I might have installed before the BSOD started to occur.So I downloaded CCleaner today,not something that I like to use because it might permanently delete important registry files,but since I'm already having the thought of reformatting my PC I thought I'd give it a go.
So I ran CCleaner,and scanned for registry issues,just as I clicked scan a lot of them were directed at nVidia PhysX software,so I cleaned all registry issues,I was not sure it was gonna solve my problem.I started Dota right after,and I was able to play it the whole day without any BSODs.