P
Phoenix B Meadows
So, ever since I got the laptop it hasn't been the most stable, something went wrong when it was upgraded from windows 8 to 10. However, when I reinstalled windows, I assumed that would fix it, boy was I wrong.
For the past several months I've been getting lots of bluescreens, sometimes I can get them to stop for several weeks (sometimes being the key word) by reinstalling my intel graphics driver, and then they just come back. Originally I thought the issue was because for some reason my Acer was refusing to update the intel driver off an old 2015 driver, however eventually I was able to make it, and things have not improved enough to be considered stable (not to mention a few updates ago I lost the ability to control brightness on my screen, and my art tablet now doesn't detect its in extend mode even though it is, which means I'm locked out of settings)
However as annoying as no brightness controls are and not being able to tweak the colors on my display the BSOD are way worse. I've been getting them almost daily (or several times a day) this weeks and I've tried everything I can think of and googled everything I can think of, and the only thing left I haven't tried is driver Verifier because it seems.... sketchy is the wrong word, but with my luck my laptop would simply never turn on again, honestly. I'm fairly sure the issue is a driver that's broken, or needs to be run in compatibility mode or something, but I have no idea which driver.
I don't know how to read crash dumps beyond what a program I have tells me from them, so if somebody could help me out that would be amazing, I am wildly frustrated at this point, but I can't afford a new laptop.
These are the most frequent errors, I always get both, or almost always I'd have to double check for certain (as copied from WhoCrashed)
On Thu 7/30/2020 4:39:30 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073020-6734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0xA (0xFFFFF8078338BF70, 0xFF, 0x0, 0xFFFFF804266CE7BA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 7/30/2020 4:39:30 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8179)
Bugcheck code: 0xA (0xFFFFF8078338BF70, 0xFF, 0x0, 0xFFFFF804266CE7BA)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
And here's some basic info on my laptop:
Computer name: DESKTOP-UJGA89V
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\WINDOWS
Hardware: Aspire V3-772G, Acer, VA70_HW
CPU: GenuineIntel Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 12759445504 bytes (11.9GB)
Continue reading...
For the past several months I've been getting lots of bluescreens, sometimes I can get them to stop for several weeks (sometimes being the key word) by reinstalling my intel graphics driver, and then they just come back. Originally I thought the issue was because for some reason my Acer was refusing to update the intel driver off an old 2015 driver, however eventually I was able to make it, and things have not improved enough to be considered stable (not to mention a few updates ago I lost the ability to control brightness on my screen, and my art tablet now doesn't detect its in extend mode even though it is, which means I'm locked out of settings)
However as annoying as no brightness controls are and not being able to tweak the colors on my display the BSOD are way worse. I've been getting them almost daily (or several times a day) this weeks and I've tried everything I can think of and googled everything I can think of, and the only thing left I haven't tried is driver Verifier because it seems.... sketchy is the wrong word, but with my luck my laptop would simply never turn on again, honestly. I'm fairly sure the issue is a driver that's broken, or needs to be run in compatibility mode or something, but I have no idea which driver.
I don't know how to read crash dumps beyond what a program I have tells me from them, so if somebody could help me out that would be amazing, I am wildly frustrated at this point, but I can't afford a new laptop.
These are the most frequent errors, I always get both, or almost always I'd have to double check for certain (as copied from WhoCrashed)
On Thu 7/30/2020 4:39:30 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073020-6734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0xA (0xFFFFF8078338BF70, 0xFF, 0x0, 0xFFFFF804266CE7BA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 7/30/2020 4:39:30 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8179)
Bugcheck code: 0xA (0xFFFFF8078338BF70, 0xFF, 0x0, 0xFFFFF804266CE7BA)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
And here's some basic info on my laptop:
Computer name: DESKTOP-UJGA89V
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\WINDOWS
Hardware: Aspire V3-772G, Acer, VA70_HW
CPU: GenuineIntel Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 12759445504 bytes (11.9GB)
Continue reading...