BSOD by nvidia driver?

Hi,

Okay, latest DMP file attached is of the KMODE_EXCEPTION_NOT_HANDLED (1e) bugcheck and is faulting dxgkrnl.sys (DirectX kernel). The previous dump is a MEMORY_MANAGEMENT (1a) bugcheck. You mentioned this was the crash that happened during P95? Well, the process name that crashed (never really the answer, however process names help give clues) is FlashPlayerPlu, so during the P95 test you were watching some sort of flash related content?

Have you ever run Memtest at all stock settings (right after clearing the CMOS)? If so, and if it passed, your video card is most likely the issue here given all of the nVidia video driver culprits, Direct X faults, etc. Since it's so brand new, contact the manufacturer for a replacement. I figured CPU earlier as you were crashing during P95 tests, however after seeing all of the DirectX and nVidia video driver culprits and putting it together, it makes sense.

Regards,

Patrick
 
Actually yes, I was watching Youtube video's during the test. So that was probably the cause of that one.

I have resorted to a complete fresh install of Windows right now. This is actually what I am typing to you from.
Odly enough wich seems pretty big to me.

DURING the INSTALLATION of windows, right after windows finishes isntalling the files and reboots to complete install (not even at the desktop part yet) I got a Page fault in non paged area BSOD. So early in the install infact that there wasen't even a minidump created cause it wasen't even at the point yet.

Do you think that both of my video cards are defective aswell seeing as it seemed to do it with both?
Ill give it a try again here with the other card to test it out.

Also with this install of windows, I removed the samsung SSD's completly so I am only runing 1 drive at everything complete stock settings with no OC and only 1 of the 780GTX.

I will need to install the drivers and such all over again here, so it might take awhile here to get back to you.
 
That's fine, and good work. The more troubleshooting we do the better. Both video cards being the culprit are possible, however, it'd be extremely unlikely. Keep running with one at a time. If you happen to BSOD after the install and updates are said and done, swap the card to the other one... and if possible, change PCI-e slots too.

Regards,

Patrick
 
Alright, so right after having installed the nvidia driver, and having clicked "Restart computer", the computer restarted, got to the windows logo and the BSOD. There seemed to have no error code and no dump was created for it, since the dump folder is empty.

I'm gonna go ahead and swap that card out for the other one and continue installing updates, I think I only have the windows updates left.
 
Alright well, while trying to install the windows update I got a BSOD for Memory Management, then after recovering from that I got another BSOD for Driver SQL mentioning the NVIDIA driver again, note this is after changing the card to the second one. I can always swap it back to the other one, but it's pretty clear both are doing it now.

Ill attach the dumps here.

Now assuming that this memtest is still correct:

(I can and will probably run in overnight again here to make doubly sure, also ill only run 1 stick instead of two)

Its plainly obvious now that it is a hardware problem, however I still can't make it what is the culprit. Is it the motherboard? The cpu? The last thing I want to do in to RMA or go out and buy another one to replace what I think might be defective and end up with the same problem. The wort case scenario is that sevral of the parts are defective, which would make it doubly a pain to narrow down.

This is by far the worst problem I have ever had in any build I have ever made.
 

Attachments

I believe we can rule out CPU being the issue. Given that both cards are causing crashes, I am inclined to believe that this is a motherboard issue (unless you are the world's unluckiest individual and both cards happen to be faulty). If Memtest comes up clean running 1 stick at a time for no less than ~8 passes, I'd contact Asus and RMA the motherboard. Since it's so new (and don't quote me on this) I am pretty sure Asus will set up and advanced RMA as long as your board qualifies for it, and they will send you a brand new one before you even have to send yours out.

Now here's the choice you can make to go a step further:

1. Asus advanced RMA sends out a brand new replacement board, and you don't have to send your old board in for ~3 weeks from what I recall. So what you can do is you can wait for the board replacement to come, see if the issues stop all together, and then send out the board. You'll be able to use your computer how you are now, but with obvious crashes here & there.

2. You setup an RMA with Asus just like you would in choice #1, however, rather than being able to use the computer with frequent crashes, you can also go a step further and contact EVGA for a possible RMA on both cards as well just in case. That way, you'll have a new replacement board and two new video cards.. so if you crash again, well... it really narrows it down quite a bit.

Regards,

Patrick
 
Alright, im going to just try runing the sticks of ram seperatly and then if that doesen't resolve the problem I will try to RMA the board.
Thanks alot for the help and I'll keep you updated
 
Got a couple more BSOD's. Mind checking them out? I don't have bluescreen viewer install to check it out.
Also, my window's update can't even complete cause it BSOD during installation, so don't mind those not being updated.
 

Attachments

Two dumps attached, one of the SYSTEM_SERVICE_EXCEPTION (3b) bugcheck and the other of the PAGE_FAULT_IN_NONPAGED_AREA (50) bugcheck.

The 3B is faulting dxgmms1.sys and the the *50 is mentioning memory corruption with dxgmms1 on the stack:

Code: 
fffff880`089c6478 fffff800`02d4bbe0 : 00000000`00000050 ffffffff`ffffff95 00000000`00000001 fffff880`089c65e0 : nt!KeBugCheckEx
fffff880`089c6480 fffff800`02ccbd2e : 00000000`00000001 ffffffff`ffffff95 00000000`00000000 fffffa80`111a1250 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`089c65e0 fffff880`0420fa8e : 00000000`00000000 fffff880`03502180 00000000`00000001 fffff880`0422102a : nt!KiPageFault+0x16e
fffff880`089c6770 fffff880`04207549 : fffffa80`111d1000 00000000`00000000 00000000`00000000 00000000`00000000 : [B]dxgmms1!VidSchiCaptureProcessName+0x1e[/B]
fffff880`089c67a0 fffff880`04239e65 : fffffa80`111a1000 fffffa80`00000000 00000000`00000000 fffffa80`111a1000 : [B]dxgmms1!VidSchiSendToExecutionQueue+0x55[/B]
fffff880`089c68a0 fffff880`04238d3c : 00000000`00000004 00000000`00000024 fffffa80`116505a0 fffffa80`11149410 : [B]dxgmms1!VidSchiSendToExecutionQueueWithWait+0x179[/B]
fffff880`089c69a0 fffff880`04238398 : fffff880`03579000 fffff880`04237d00 fffffa80`00000000 fffffa80`000000a4 : [B]dxgmms1!VidSchiSubmitRenderCommand+0x920[/B]
fffff880`089c6b90 fffff880`04237e96 : 00000000`00000000 fffffa80`11707200 00000000`00000080 fffffa80`11149410 : [B]dxgmms1!VidSchiSubmitQueueCommand+0x50[/B]
fffff880`089c6bc0 fffff800`02f6bede : 00000000`01edd69d fffffa80`111684c0 fffffa80`0c748040 fffffa80`111684c0 : [B]dxgmms1!VidSchiWorkerThread+0xd6[/B]
fffff880`089c6c00 fffff800`02cbe906 : fffff880`03574180 fffffa80`111684c0 fffff880`0357f0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`089c6c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

Again, likely motherboard / video related if the RAM turns out okay with the Memtest.

Regards,

Patrick
 
Alright, so I took out 1 of the two sticks of ram so that I am only runing 1 8gb stick, then I ran memtest86+ for 14 hours where it passed 14 tests and got no errors. Ill run prime95 again here and see if it crashes again knowing for sure that it's not the ram.
 
Okay, so I ran a couple more tests including the Intel processor diagnostic about 4 or 5 times and it passed each time. However, I also ran right after the Intel CPU burn test, where that failed almost immediatly at 33.62 seconds with a critical error, no BSOD but a similar error to what prime95 is. Do you still think it's the mobo causing because the diagnostic passes, or do you think it's the cpu. Either way, im gonna start the motherboard RMA here, but I would want to know if the cpu is fried too.
 
Hi,

If your CPU was actually the issue here, we'd be seeing more consistent problems, and more than likely in a different fashion. Get the motherboard sorted~

Regards,

Patrick
 
Alright, submitted the RMA for the motherboard and I already removed it from the computer and everything.
So for now, I can't use that computer and ill be using my gaming laptop.

However I might reply with other updates in the mean time as I will install at least one of the 780gtx's in my brothers computer that is currently running a 670GTX and see if the cards make his completely stable computer crash so I can be sure that the cards are fine.
 
However I might reply with other updates in the mean time as I will install at least one of the 780gtx's in my brothers computer that is currently running a 670GTX and see if the cards make his completely stable computer crash so I can be sure that the cards are fine.
Click to expand...

Very good idea! I'll be looking forward to the updates.

Regards,

Patrick
 
Sorry about the wait for the update.

So I'm still waiting on the RMA for the Motherboard, however I have put my 780's into my brothers gaming computer, replacing his 670GTX. And low and behold they run with no problems what so ever in his system, no crashing, no bugs, no visual artifacts and so on.

So with that out of the way, it at least makes it more clear, because we know for a fact that the RAM and the Graphic cards are stable.
 
Hi,

Thanks a lot for the update! So yes, now we can surely rule it down to the motherboard being the issue (unless it's your PSU, but I doubt it).

Regards,

Patrick
 
Last edited:
Alright good and bad news.

The good news is I got my new board and this one is actually able to use RAID, where as the other wouldn't even post when I would switch the Sata setting from AHCI to RAID.

The bad news is it's still blue screening alot, to the point where it's hard to get this message posted with out it going out on me.
Ill post the dumps and see what we get.



EDIT, upon closer personal review using Bluescreen viewer, it seems that each one is caused by the exact same driver and exact same address each time.
 

Attachments

Hi,

Interesting, all attached dumps are of the IRQL_NOT_LESS_OR_EQUAL (a) bugcheck.

In the stacks, we are always seeing multiple page faults~ These cannot be handled when the IRQL is 2 or higher.

Code: 
Arg2: 0000000000000002, IRQL

Code: 
4: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`14f61518 fffff800`02c751a9 : 00000000`0000000a fffffa80`751bfe20 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`14f61520 fffff800`02c73e20 : fffff700`01080000 00000000`00000001 00000000`00105200 fffffa80`751bfe10 : nt!KiBugCheckDispatch+0x69
fffff880`14f61660 fffff800`02c9b150 : 00000000`00000000 fffffa80`18cb3ec8 fffff700`01080000 fffff880`14f61ae0 : nt![COLOR=#ff0000][U][B]KiPageFault+0x260[/B][/U][/COLOR] (TrapFrame @ fffff880`14f61660)
fffff880`14f617f0 fffff800`02c9990f : fffffa80`188d0bb8 00000000`0000004b fffffa80`151c4610 00000000`0000004b : nt!MiReplenishPageSlist+0xc0
fffff880`14f61860 fffff800`02c83044 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
fffff880`14f61980 fffff800`02c73d2e : 00000000`00000001 00000000`07196000 00000000`00001901 00000000`06ff309c : nt!MmAccessFault+0x1224
fffff880`14f61ae0 00000000`658429ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt![COLOR=#ff0000][U][B]KiPageFault+0x16e[/B][/U][/COLOR] (TrapFrame @ fffff880`14f61ae0)
00000000`003ce500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x658429ed

This may indicate a faulty hard disk, and since we haven't done disk diagnostics yet, let's get to it:

1. check physical connections to the drive (sata cables, etc).

2. chkdsk:

start>search bar>type cmd right click and select run as admin

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.
Click to expand...

3. seatools - SeaTools | Seagate

run everything aside from Fix all and Long Generic.

Regards,

Patrick
 
Alright well we might be on to something.

I had ran chckdsk before and had no problems, but now it did the test, then on the reboot from it as it's loading up windows it blue screened on me there. Then I went and installed the SeaTools and ran that, the short generic worked fine, but about half way through the long generic (I know you said not to run it, but theres was really nothing else, but short and drive information which it said was unavailable for RAID) I blue screened again with a System_service_exception this time, however still referencing the exact same driver and location.

Then I decided to run it again, and right at the end of the test I got a Memory Management BSOD again, referecing the same driver and location.
Here are the dumps.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top