lots of BSOD's

I have noticed a small pattern of individuals reporting and asking questions about the same bsod's, and every forum and support page I've read hasn't had a solution as of yet. This has been recurring ever since I purchased my laptop last December.

It is an Acer V3 772G

Intel® Core™ i7-4702MQ processor

NVIDIA® GeForce GT 760M


256 GB SSD


Here is the link for my DMP and Info files


I would very much appreciate any assistance in this matter.

Thank you in advance.



We have various bug checks:


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.

-- FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+601e1

^^ nVidia video driver.


This indicates that a severe memory management error occurred.

BugCheck 1A, {3470, ffffd000234ea000, 16ff24a308d3d75b, 36ff24a308d3d75b}

- The 1st parameter of the bug check is 3470 which indicates an unknown memory management error occurred.


This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
BugCheck 3B, {c0000005, fffff8022732fe76, ffffd0003689df00, 0}

7: kd> ln fffff8022732fe76
(fffff802`2732fdd0)   nt!KiInsertTimerTable+0xa6   |  (fffff802`27330080)   nt!KiDeliverApc

^^ The exception occurred in nt!KiInsertTimerTable.


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.


This indicates that a driver has overrun a stack-based buffer.

A driver overran a stack-based buffer (or local variable) in a way that would have overwritten the function's return address and jumped back to an arbitrary address when the function returned.


1. 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.

2. Remove and replace Kaspersky with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's very likely causing conflicts:

Kaspersky removal - http://support.kaspersky.com/common/service.aspx?el=1464

Windows Defender (how to turn on after removal) - http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html

3. SSPORT.sys is listed and loaded which is the Samsung printer driver (dated from 2005). This device driver is far too old to work with Windows 8, so please look for an update, and if not available, you'll need to remove the printer and uninstall the software.




Debugger/Reverse Engineer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated February 12, 2018 Views 250 Applies to: