Acer V3-571G with a 1.5 year BSOD problem

ZaDruglord · Dec 23, 2013

A year and a half ago I've gotten an Acer, which came with a gift Corsair 4GB DDR3 Memory which I installed. From the first day I started getting random BSODs, multiple times a day and from time to time making a chain reaction(restarting PC just to get another BSOD and so on). At that point I reinstalled windows a couple of times to no avail. Knowing Corsair, I changed it with a 4gb DDR3 Elixir. BSODs didnt disappear but they got a little rarer, still was a big nuisance though.
I've tried everything, from doing driver checks to memory stress tests and video stress tests. BSODs only seem to appear when I put stress on the PC( opening lots of apps when PC just booted or playing games). Some games give me BSOD, some dont, and some sometimes give sometimes dont. It's really random, the only time I managed to exactly pinpoint and reproduce a BSOD was when I tried setting up my PS3 controller with DS3 Tool. In DS3 Tool when I try to load a driver it gives me instant BSOD.
For the last couple of weeks I only got a BSOD once a couple of days, but since yesterday they started appearing frequently again (got about 5 yesterday)
Here are all the minidumps from yesterday. Can someone at least help me figure out what the problem is?
Thanks!
View attachment Minidump.rar

x BlueRobot · Dec 23, 2013

Please follow - https://www.sysnative.com/forums/bs...ctions-windows-8-1-8-7-and-windows-vista.html

ZaDruglord · Dec 23, 2013

Oh, I'm terribly sorry. I seemed to have missed that guideline. I'll do everything and update this post when I'm done. Thank you for your guidance !

x BlueRobot · Dec 23, 2013

It's okay, please post the folder in your next post.

ZaDruglord · Dec 23, 2013

Here are the specifications and the attachment with everything on that thread. I'll update this post with results from driver verifier, HDD diagnostics and RAM test. Thanks!

Read More:

View attachment Reports.rar

ZaDruglord · Dec 23, 2013

Hmm, can't find no edit button so I'll just make another post. I made the driver verifier, but after I rebooted it wouldn't get into windows so I had to system restore, but I can't figure out what to do in case the test fails at this point.
Regarding the HDD test, I did a benchmark and error scan and everything seemed fine. I did other memory tests before and they turned up fine, but unfortunately I don't have a blank CD or anything so I'll have to do it tomorrow morning.

Patrick · Dec 23, 2013

Hi,

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

If we take a look at the call stack:

Code:

7: kd> kb
RetAddr           : Args to Child                                                           : Call Site
fffff800`0307c169 : 00000000`0000000a fffff880`0a919638 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`0307ade0 : 00000001`00000001 fffff880`00000001 fffff880`032dd200 fffffa80`08129480 : nt!KiBugCheckDispatch+0x69
fffff880`0a919638 : fffff880`00ea3c36 fffffa80`08129480 fffffa80`08129480 fffff880`035b8c80 : nt!KiPageFault+0x260
fffff880`00ea3c36 : fffffa80`08129480 fffffa80`08129480 fffff880`035b8c80 fffff800`031b0d0e : MijXfilt+0x1b638
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x542

FAILURE_BUCKET_ID: X64_0xD1_VRF_CODE_AV_BAD_IP_MijXfilt+1b638

^^ MotioninJoy simulate Xbox 360 controller (virtual Xinput device). This is a notorious driver for causing BSOD's, remove the software for it ASAP and use the official Xbox 360 drivers instead - Software Downloads: Xbox 360 Controller for Windows

IRQL_NOT_LESS_OR_EQUAL (a)

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

Code:

STACK_TEXT:  
fffff800`00ba2238 fffff800`030cc169 : 00000000`0000000a fffff820`03304100 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba2240 fffff800`030cade0 : 3c800000`3d000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2380 fffff800`0318f56e : 00000000`0002fd48 00000000`00000000 fffff800`00ba2630 00000000`00137133 : nt!KiPageFault+0x260
fffff800`00ba2510 fffff800`0318f743 : fffffa80`0727ecf0 fffff800`00000009 fffffa80`00000000 fffff800`00000004 : nt!RtlpWalkFrameChain+0x14de
fffff800`00ba2bb0 fffff800`031905cb : 00000000`00000003 fffffa80`0727ecf0 00000000`00000000 fffffa80`0727ecb8 : nt!RtlWalkFrameChain+0x63
fffff800`00ba2be0 fffff800`035704a5 : fffffa80`0bab7602 fffff880`0f591ec1 fffffa80`0727ece0 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x4b
fffff800`00ba2c10 fffff800`0357096c : fffffa80`0bab76e8 00000000`000000e0 00000000`00000500 00000000`00000000 : nt!ViKeRaiseIrqlSanityChecks+0xa5
fffff800`00ba2c50 fffff880`0f591ec1 : 00000000`00000000 00000000`00000000 fffffa80`0cd1f000 fffffa80`0cd1f000 : nt!VerifierKeAcquireInStackQueuedSpinLock+0xac
fffff800`00ba2c90 00000000`00000000 : 00000000`00000000 fffffa80`0cd1f000 fffffa80`0cd1f000 00000000`00000000 : nvlddmkm+0xf8ec1

FAILURE_BUCKET_ID: X64_0xA_VRF_nvlddmkm+f8ec1

^^ nVidia video driver.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

-----------------------------

If you're still crashing after the above:

1. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Regards,

Patrick

ZaDruglord · Dec 23, 2013

Okay, this is weird. I've been up-to-date with video drivers for the past 1.5 years so I can say my laptops been through a couple of them and the problem still persisted. Right now there's a really small update to the drivers, and when I tried performing a clean install it gave me a BSOD. Tried again and surely enough BSOD again during installation. Here are the dumps
View attachment Dump.rar
Thanks !

Patrick · Dec 23, 2013

The latest DMP's are of the DRIVER_VERIFIER_DETECTED_VIOLATION (c4) bug check.

This is the general bug check code for fatal errors found by Driver Verifier.

They are all faulting your nVidia video driver. Go ahead and remove and replace avast!, I wonder if it's conflicting and causing display driver crashes.

If you remove it and still crash, is there a beta driver available to try?

Regards,

Patrick

ZaDruglord · Dec 24, 2013

Okay, I uninstalled Avast and retried the update, and it works. I checked the nvidia site and I couldn't find no beta driver.
But I doubt the whole BSOD problem was a graphics driver one. I mean, I've been almost up-to-date for the past 1.5 years and I've been through numerous versions and the problem still persisted.
Anyways, if I get another BSOD I'll reply with the minidump.
Also, thank you for the answers! I was surprised with how quick and helpful they were !

jcgriff2 · Dec 24, 2013

Hi -

Just listing the following as I've seen it a few times before and wonder if NVIDIA, another 3rd party driver or hardware is at fault here. It is literally unheard of for a NVIDIA driver to be flagged by Driver Verifier.

As Patrick mentioned, the dumps were VERIFIER_ENABLED and named NVIDIA video as the probable cause.

Bugcheck on both = 0xc4 (0xf6,,,)

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000001b8, Handle value being referenced.
Arg3: fffffa800a1efaa0, Address of the current process.
Arg4: fffff8800f4afce1, Address inside the driver that is performing the incorrect reference.

From post #4/8 - http://w.osronline.com/showthread.cfm?link=244003

If AccessMode is KernelMode, the handle should originate in the kernel address
space. Drivers should always specify UserMode for handles they receive from user
address space.

Starting with Windows 7, if AccessMode is KernelMode and handle is received from
user address space, Driver Verifier issues bugcheck C4, subcode F6.

Do the non-VERIFIER_ENABLED BSODs name NVIDIA? (I haven't yet gone back to run them).

Happy Holidays!

jcgriff2

ZaDruglord · Dec 24, 2013

Okay, so, with everything set I did a combo that usually resulted in BSOD (mainly youtube running with skype+steam+dota2). It took longer than usual to BSOD, but it still did, and this time it took an awful lot of time to dump memory cache, about 5% per 20-30 seconds.
Here's the View attachment Report.rar
Thanks again for doing this for me, and Merry Christmas!

Patrick · Dec 24, 2013

This DMP is of the IRQL_NOT_LESS_OR_EQUAL (a) bug check.

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If we take a look at the call stack:

Code:

1: kd> kb
RetAddr           : Args to Child                                                           : Call Site
fffff800`03088169 : 00000000`0000000a fffff820`032c0008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`03086de0 : 00000000`00000000 00000000`00000000 00000000`00000000 85900000`282d9882 : nt!KiBugCheckDispatch+0x69
fffff800`030b95d7 : 00000000`00000000 fffffa80`0b864000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`030b908e : 85900000`282d9882 fffff800`032c3600 fffffa80`007888b0 fffff800`032c3600 : nt!MiMigratePfn+0x37
fffff800`030a5c8f : 00000000`00000000 85900000`282d9882 00000000`00000000 fffff800`032c3600 : nt!MiResolveTransitionFault+0x18e
fffff800`03095c3b : fffffa80`00000081 fffff880`00000080 fffffa80`0bbf2b50 00000000`00000002 : nt!MiDispatchFault+0x95f
fffff800`03086cee : 00000000`00000000 fffff8a0`15a62510 fffffa80`0cb38000 00000000`00000000 : nt!MmAccessFault+0xe1b
fffff880`0f420e26 : 00000000`00000010 fffff880`0f41e004 00000000`00000010 00000000`00010246 : nt!KiPageFault+0x16e
fffff880`0f41dff7 : 00000000`00000000 fffffa80`103880b0 00000000`00000025 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22
fffff880`0f4387d9 : fffff6fb`00000000 fffff8a0`179f71c0 fffffa80`00000000 fffffa80`0e08b6d0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`0f438514 : 00000000`00000010 fffff880`0f437f00 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0f438012 : 00000000`00000000 fffffa80`0bc1ca70 00000000`00000080 fffffa80`0b8b2410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff800`033252ea : 00000000`02fc8a2a fffffa80`0bbf2b50 fffffa80`07316890 fffffa80`0bbf2b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff800`030798e6 : fffff800`03203e80 fffffa80`0bbf2b50 fffff800`03211cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
00000000`00000000 : fffff880`02b6a000 fffff880`02b64000 fffff880`02b69540 00000000`00000000 : nt!KiStartSystemThread+0x16

FAILURE_BUCKET_ID: X64_0xA_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22

^^ VRF in the FBID, this indicates verifier was enabled at the time of the crash, which we can also prove by running !verifier:

Code:

1: kd> !verifier

Verify Level 92b ... enabled options are:
    Special pool
    Special irql
    All pool allocations checked on unload
    Deadlock detection enabled
    Security checks enabled
    Miscellaneous checks enabled

We have various dxgmm1.sys (Direct X MMS) routine calls, and supposedly the fault of the crash here as well. With this said, it's looking like a faulty video card. I should have fully read your original post more thoroughly in the first place, because you mention this:

From the first day I started getting random BSODs

This implies faulty hardware almost to the dot. It should have been replaced immediately. Do you still qualify for a warranty replacement and/or repair?

Regards,

Patrick

ZaDruglord · Dec 24, 2013

I think so, the warranty was for 2 years if I remember correctly. At first I thought it was cause of the Corsair memory, so that's why I didn't sent it to repair. If it's still eligible for replacement will they replace my whole laptop or just video card? I've never had to send a laptop to repairs and if it replaces it as a whole I'd like to backup before.

Patrick · Dec 24, 2013

I couldn't tell you, that's up to them.

Regards,

Patrick

ZaDruglord · Dec 24, 2013

Thank you for all the help ! I've finally managed to crack down a year and a half of frustration.

Patrick · Dec 25, 2013

My pleasure, hopefully Acer will at least repair it. I am not sure if you qualify for replacement as it has been quite some time. You'll see!

For future reference, if you purchase a new system and right out of the box it's crashing (and I literally mean you plugged it in, turned it on, didn't install anything 3rd party at all and it's crashing), send it back ASAP. If you're crashing out of the box on a new system, you got a faulty system.

Regards,

Patrick

ZaDruglord · Dec 25, 2013

Will do, thanks! I checked the warranty, and I'm still eligible, but today when I turned on the PC I've been confronted with BSODs right as the PC turns on, and I can't get it to run. The shop is closed until the second of January, and I'll get it to the service then, but until then is there something I can do to temporarily fix it?
Here are the View attachment Minidumps.rar

ZaDruglord · Dec 25, 2013

Scratch that, I think I've solved it by disabling driver verifier.

Patrick · Dec 25, 2013

Yes, my apologies, I forgot to tell you to disable verifier. It was as usual detecting the display driver in violation over and over again.

To be sure, have you tried a beta version of the drivers if it's available, or a few versions behind the latest?

Regards,

Patrick

Acer V3-571G with a 1.5 year BSOD problem

Member

Administrator

Member

Administrator

Member

Member

Sysnative Staff

Member

Sysnative Staff

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Sysnative Staff

Member

Sysnative Staff

Member

Sysnative Staff

Member

Member

Sysnative Staff

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)