Windows 10: Acer Aspire BSOD every other day at various times, no dump log

System is an Upgraded (8.1 to 10) Acer ACT-105-UR11.
10G on a 64-bit AMD A10-6700, with a single 1TB drive 25% used.

In an office network, 8 computers connect to it for the ACT and QBooks software. Application event viewer is spammed with MSSQL$ACT7 errors - I upgraded ACT to solve other problems, but this persists.

Changed swap file from managed to single size, currently back to managed. Changed dump location from managed to set location, currently back to managed with a small dump (just today, after reading the forums).

All drivers show updated, even checked on AMD's site to verify video and HDD drivers. Ran a disk scan and sfc/scannow, both returned no errors.

I can find no consistent problems in the App and Sys event viewers that correspond with the BSOD's. They do occur at almost set times - between 8:00-8:45am and 12:00-12:45pm, but on odd days and not consistently. I considered that the computer is coming out of some sort of sleep, but every item I can find is set to not sleep or minimal down time.

Any help would be appreciated.

Victor.

:)

 

Acer Aspire shows blank screen following windows 10 download

Acer Aspire E15 purchased June 2015 with integral Windows 10 upgrade ready to download on windows notification.

Download completed 2 days ago and left with blank screen after the Acer logo screen drops out.

Waited for 10 minutes but still blank.

Shutdown and restarted couple of times and eventually got to log in screen.

Took 35 seconds from log in to homepage. Whats going on. This happens every time. Thinking of going back to 8.1.

 

BSOD crashes and intel hd crashes on brand new acer 592g

Hey there,

so i bought my new acer aspire vn7-592g (awesoem laptop) 3 days ago and recently i have been having bsod crashes like Page Fault in Nonpaged Area, video Scheduler internal error and kmode exception not handeled

and intel graphics crashes while surfing on the web on firefox

here are some dump files CrashDumps.rar

 

Hi vmanuel,

Welcome to the 10forums.

Please configure the recovery settings of the dumps to not automatically restart, I'll need at least picture of the BSOD.
Attachment 66712
Just to check, please make sure your pc is configured for small dump files with no location change How to configure minidump | Windows 10 tutorial

Please run CPU-Z | Softwares | CPUID, open it and make screenshots of the following tabs

• CPU
• Mainboard
• Memory
• SPD*
• Graphics

*SPD shows the details of each module, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each module.

Please post each screenshot in your next reply/replies.

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

Axe0 I apologize for the delay - I don't have constant access to the system in question.

I went through the tutorial for minidumps, and set it to all defaults. Screenshot of the dump settings is attached in a Word file.

I ran CPU-Z (neat tool btw) and attached screen shots as well.

I also added a screenshot of the error message that my client sent me via cell.

 

Also I forgot to mention that the system has blue screened twice since I updated the minidump settings without creating a dump.

However, after a close look at the screenshot, I did see that it's complaining about a IRQL_NOT_LESS_OR_EQUAL error. I'm going to surf for that one presently.

Thanks very much for your time and support on this. Win10 errors are still new for me.

Victor.

 

Surfing would lead to standard things that might not be useful at all.

If you have configured Windows to not restart, take a pic and post it.

 

Attachment 67643Here's the blue screen itself. Even though the system is set to reboot, it does not.

Attachment 67645

 

Please search "services.msc" (without quotes) and press enter, scroll down until you see the service 'Windows Error Reporting Service', check the startup type that should be manual, if the startup type is not manual change it by right clicking the service > properties.

Please check your page file Virtual Memory Paging File - Change, the tutorial is for Windows Vista but it is the same for Windows 10.
Please make a screenshot of the settings of the page file and post it.






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.


If all above fails to create a crash dump, it is possible that your memory is corrupted, too much to create a dump from that contains data that isn't corrupted, in case all above fails please test your memory using MemTest86+





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

Thank you, I didn't think about the Error Reporting Service, I'll check that.

The Paging File is set to defaults, didn't grab a picture though.

I'll run the other two tests on Sunday night and Tuesday, and let you know.

Thank you immensely for your time and energy on this!

Victor.

 

Attachment 69163The virtual memory settings are all defaults. Windows is definitely managing them dynamically, since it's starting at 640mb and growing as the day progresses. Ran Driver Verifier per the recommendations for 48 hours, no difference. I'm going to run Mem Tester this coming Monday, and I'm hoping to find the culprit.

One note - where does Driver Verifier log its results if you don't force it to create a log? I ended up creating one, but I'm curious to know if it logs anything without doing that. Also, the log I created was just a listing of the settings.

 

The only thing driver verifier will log is a crash dump when a driver is violating.