Random BSODs in Windows 8 (Acer v3-772g)

IcEmAn34 · Mar 30, 2014

Hello.

I have bought my Acer laptop about 6 weeks ago and immediately updated to windows 8.1 (it had preinstalled windows 8). So after doing that I got first BSOD in two or three days. Because I thought I did something wrong during the update or when installing some of my applications, I decided to refresh my computer to factory settings after getting a couple of more BSOD's. So I did a factory reset and updated to windows 8.1 according to the instructions by Acer. Everything went great except for one thing. After a couple of days, BSOD's began repeating again. So I decided to update all of my drivers and uninstall McAfee internet suite. Nothing helped.

I finally decided to do another factory reset, but this time to stay on Windows 8 and run only basic software for couple of days and then begin to install some of additional applications. Everything went fine, but after two weeks without crash, it happened again. And it happened random, so I didn't keep in mind which software was last installed. So that first one on Windows 8 happened on March 19th, and second one happened today.

Both of them were driver_irql_not_less_or_equal with ntoskrnl.exe

I don't know anymore what to do... I'm including .zip file in attachments for further analysis.

IcEmAn34 · Mar 31, 2014

I forgot to mention, that I have done all the memtests, chkdsks and everything while on Windows 8.1

lifetec · Mar 31, 2014

Only 126 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

<Device><![CDATA[Bluetooth USB Module]]></Device>
<PNP_Device_ID><![CDATA[USB\VID_0489&PID_E04E\5&D5F8AC9&0&10]]></PNP_Device_ID>
<Error_Code><![CDATA[This device is disabled.]]></Error_Code>
</Data>

Please enable and update the driver to the latest driver

Both dumpfiles are BugCheck D1, {ca32b7d72b, 2, 8, ca32b7d72b}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260

When a Windows/system driver like ntkrnlmp.exe is blamed when experiencing a BSOD
it's most likely not the problem. Most of the time further analysis is needed to determine the actual cause.

Code:

BugCheck D1, {ca32b7d72b, 2, 8, ca32b7d72b}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000ca32b7d72b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 000000ca32b7d72b, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80311b6d168
GetUlongFromAddress: unable to read from fffff80311b6d1f8
 000000ca32b7d72b Nonpaged pool
CURRENT_IRQL:  2
FAULTING_IP: 
+59f6000ff9
000000ca`32b7d72b ??              ???
PROCESS_NAME:  System
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  AV
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE:  FFFFF880009F3FB0
TRAP_FRAME:  fffff880009f3ca0 -- (.trap 0xfffff880009f3ca0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=1db04f3acaed0000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=000000ca32b7d72b rsp=fffff880009f3e38 rbp=0000000000000008
 r8=000000000000082f  r9=000000000000002f r10=00000000000000ff
r11=fffff880009c3180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
000000ca`32b7d72b ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff8031186e769 to fffff8031186f440
FAILED_INSTRUCTION_ADDRESS: 
+59f6000ff9
000000ca`32b7d72b ??              ???
STACK_TEXT:  
fffff880`009f3b58 fffff803`1186e769 : 00000000`0000000a 000000ca`32b7d72b 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`009f3b60 fffff803`1186cfe0 : 00000000`00000008 fffff880`009c3180 00000000`00000000 fffff880`009f3ca0 : nt!KiBugCheckDispatch+0x69
fffff880`009f3ca0 000000ca`32b7d72b : fffff803`11897a06 fffff880`009c3180 fffff880`04747a50 fffffa80`10bfb040 : nt!KiPageFault+0x260
fffff880`009f3e38 fffff803`11897a06 : fffff880`009c3180 fffff880`04747a50 fffffa80`10bfb040 00000000`00000004 : 0x000000ca`32b7d72b
fffff880`009f3e40 fffff803`118693a5 : 055dc471`0e50cd7f fffff880`009c3180 fffff880`06e24ac0 fffffa80`0d600210 : nt!KiRetireDpcList+0x1f6
fffff880`009f3fb0 fffff803`118691a9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`06e24a00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiPageFault+260
fffff803`1186cfe0 440f20c0        mov     rax,cr8
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!KiPageFault+260
FOLLOWUP_NAME:  MachineOwner
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff87fe1cbeac2, 2, 8, fffff87fe1cbeac2}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff87fe1cbeac2, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff87fe1cbeac2, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80057dd1168
GetUlongFromAddress: unable to read from fffff80057dd11f8
 fffff87fe1cbeac2 Nonpaged pool
CURRENT_IRQL:  2
FAULTING_IP: 
+57f6000ff9
fffff87f`e1cbeac2 ??              ???
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  AV
PROCESS_NAME:  System
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE:  FFFFF80056667FB0
TRAP_FRAME:  fffff80056661720 -- (.trap 0xfffff80056661720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff80057d71180
rdx=fffffa8014d27c20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff87fe1cbeac2 rsp=fffff800566618b0 rbp=0000000000000000
 r8=00000134f88f82ed  r9=0000000000000023 r10=fffff80057a79000
r11=fffff80056661818 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff87f`e1cbeac2 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80057ad2769 to fffff80057ad3440
FAILED_INSTRUCTION_ADDRESS: 
+57f6000ff9
fffff87f`e1cbeac2 ??              ???
STACK_TEXT:  
fffff800`566615d8 fffff800`57ad2769 : 00000000`0000000a fffff87f`e1cbeac2 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`566615e0 fffff800`57ad0fe0 : 00000000`00000008 fffffa80`0ef67d78 00000000`00000000 fffff800`56661720 : nt!KiBugCheckDispatch+0x69
fffff800`56661720 fffff87f`e1cbeac2 : fffffa80`00000001 00000000`00000000 fffffa80`0ee22100 fffffa80`0ef67d78 : nt!KiPageFault+0x260
fffff800`566618b0 fffffa80`00000001 : 00000000`00000000 fffffa80`0ee22100 fffffa80`0ef67d78 00000000`00000000 : 0xfffff87f`e1cbeac2
fffff800`566618b8 00000000`00000000 : fffffa80`0ee22100 fffffa80`0ef67d78 00000000`00000000 00000000`00000000 : 0xfffffa80`00000001

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`57ad0fe0 440f20c0        mov     rax,cr8
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!KiPageFault+260
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  51a966cd
IMAGE_VERSION:  6.2.9200.16628
BUCKET_ID_FUNC_OFFSET:  260
FAILURE_BUCKET_ID:  AV_CODE_AV_BAD_IP_nt!KiPageFault
BUCKET_ID:  AV_CODE_AV_BAD_IP_nt!KiPageFault
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:av_code_av_bad_ip_nt!kipagefault
FAILURE_ID_HASH:  {73cd60cc-83fa-6b76-df08-1961c31d7403}
Followup: MachineOwner

In your WER(=Windows Error Report)

+++ WER2 +++:
Fault bucket AV_CODE_AV_BAD_IP_athw8x!ath_intr, type 0
Event Name: BlueScreen

Athw8xath refers to your Atheros Wireless networkadapter.
Please update to the latest windows 8/8.1 compatible drivers.
The latest windows 8/ 8.1 drivers for your Aspire V3-772G you can download from Acer | Download

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

wdcsam64 Wed Apr 16 10:39:08 2008 (4805bb2c) 0000d887 wdcsam64.sys
Driver Description: Western Digital External Drive RAID Manager
2008 driver version has known BSOD issues in WindowsDriver Update Site: WD Support / Downloads / Select Product

fltsrv Thu Jul 14 11:50:57 2011 (4e1ebc01) 000268a6 fltsrv.sys
Driver Description: Acronis Storage Filter Management Driver
Driver Update Site: Support: Backup software for data backup and disaster recovery in Windows and Linux - Acronis
Download: Backup software for data backup and disaster recovery in Windows and Linux - Acronis

k57nd60a Wed Oct 19 22:17:36 2011 (4e9f3060) 00072893 k57nd60a.sys
Driver Description: Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver
Driver Update Site: Ethernet NIC Driver Downloads | Broadcom

If all of this doesn't stop the BSOD's, please runDriver Verifier according to these instructions: Driver Verifier Settings

IcEmAn34 · Mar 31, 2014

Updating drivers in process...

Windows update says, that no updates are available.

IcEmAn34 · Apr 1, 2014

New BSOD happened minutes ago.

KMODE_EXCEPTION_NOT_HANDLED

IcEmAn34 · Apr 1, 2014

I remembered that I have removed some of Acer bloatware just couple of hours before getting first BSOD now on Windows 8. Could this be the reason? I removed this bloatware on W8.1 immediately after installation, so the BSOD's came earlier...

IcEmAn34 · Apr 1, 2014

lol, here it is... Again. But new one:
unexpected_kernel_mode_trap with athw8x.sys
http://1drv.ms/1lkWRF6
Could this mean, that atheros drivers are to blame for BSOD's, because I was (and still am) running driver verifier???

lifetec · Apr 1, 2014

lol, here it is... Again. But new one:
unexpected_kernel_mode_trap with athw8x.sys
http://1drv.ms/1lkWRF6
Could this mean, that atheros drivers are to blame for BSOD's, because I was (and still am) running driver verifier???

Yes, the atheros drivers are to blame that is what i said in my analyze.
That is why you need to update your drivers to the latest windows 8.1. compatible driver on the Acersite(see my post above)
Your atheros driver in your latest dump is still the old driver from 2013, you need this one

Wireless LAN

Atheros

Wireless LAN Driver

10.0.276

251.7 MB

2014/03/17

You can stop driver verifier now, you only need to run driver verifier, if after updating all the mentioned drivers you still getting BSOD.

IcEmAn34 · Apr 1, 2014

I updated atheros driver right after I got tgat BSOD, but 2 hours later another one happened.

This is getting ridiculous

http://1drv.ms/PeoJzG

i'm sick and tired of acer and windows. Bought new computer for 1200€ and got problems all the time. Did 3 factory resets and nothing helps.

IcEmAn34 · Apr 1, 2014

lol
did another factory reset
installed windows 8, uninstalled mcafee, updated windows 8, installed windows 8.1, updated windows 8.1 to latest, installed latest drivers AND ANOTHER DAMN CRASH
http://1drv.ms/1dLcwh4
this time I have completely nothing on my system and crash occured.
I can't even read it, because I don't have any tool. What does it say?

lifetec · Apr 1, 2014

Your latest uploaded dumpfile is another type of BSOD BugCheck A, {18, 2, 0, fffff803b2305a5d}
Probably caused by : ntkrnlmp.exe ( nt!SepNormalAccessCheck+bd )

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {18, 2, 0, fffff803b2305a5d}
Probably caused by : ntkrnlmp.exe ( nt!SepNormalAccessCheck+bd )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803b2305a5d, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff803b25c8168
GetUlongFromAddress: unable to read from fffff803b25c81f8
 0000000000000018 Nonpaged pool
CURRENT_IRQL:  2
FAULTING_IP: 
nt!SepNormalAccessCheck+bd
fffff803`b2305a5d 8b5f18          mov     ebx,dword ptr [rdi+18h]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  AV
PROCESS_NAME:  System
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME:  fffff880009fa630 -- (.trap 0xfffff880009fa630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000c0d4 rbx=0000000000000000 rcx=fffff88002fdb180
rdx=0000000000000080 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803b2305a5d rsp=fffff880009fa7c8 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=00000000000000c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!SepNormalAccessCheck+0xbd:
fffff803`b2305a5d 8b5f18          mov     ebx,dword ptr [rdi+18h] ds:00000000`00000018=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff803b22c9769 to fffff803b22ca440
STACK_TEXT:  
fffff880`009fa4e8 fffff803`b22c9769 : 00000000`0000000a 00000000`00000018 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009fa4f0 fffff803`b22c7fe0 : 00000000`00000000 fffffa80`1186f2c0 fffff980`243b8e00 fffff880`009fa630 : nt!KiBugCheckDispatch+0x69
fffff880`009fa630 fffff803`b2305a5d : fffff803`b22f22f7 fffff880`02fdb180 fffff803`b24f6000 fffff880`02fdb180 : nt!KiPageFault+0x260
fffff880`009fa7c8 fffff880`02fdb180 : ffff354f`0e1ea778 fffff880`009fa900 fffff803`b256af80 00000000`02fdb180 : nt!SepNormalAccessCheck+0xbd
fffff880`009fa898 ffff354f`0e1ea778 : fffff880`009fa900 fffff803`b256af80 00000000`02fdb180 fffff803`00000001 : 0xfffff880`02fdb180
fffff880`009fa8a0 fffff880`009fa900 : fffff803`b256af80 00000000`02fdb180 fffff803`00000001 fffff880`02fe05c8 : 0xffff354f`0e1ea778
fffff880`009fa8a8 fffff803`b256af80 : 00000000`02fdb180 fffff803`00000001 fffff880`02fe05c8 fffff880`009fab10 : 0xfffff880`009fa900
fffff880`009fa8b0 00000000`02fdb180 : fffff803`00000001 fffff880`02fe05c8 fffff880`009fab10 fffff880`009fa9c0 : nt!KiInitialPCR+0x2f80
fffff880`009fa8b8 fffff803`00000001 : fffff880`02fe05c8 fffff880`009fab10 fffff880`009fa9c0 fffff880`02fe6f40 : 0x2fdb180
fffff880`009fa8c0 fffff880`02fe05c8 : fffff880`009fab10 fffff880`009fa9c0 fffff880`02fe6f40 00000000`00000000 : 0xfffff803`00000001
fffff880`009fa8c8 fffff880`009fab10 : fffff880`009fa9c0 fffff880`02fe6f40 00000000`00000000 fffff880`02fdb180 : 0xfffff880`02fe05c8
fffff880`009fa8d0 fffff880`009fa9c0 : fffff880`02fe6f40 00000000`00000000 fffff880`02fdb180 00000000`00045302 : 0xfffff880`009fab10
fffff880`009fa8d8 fffff880`02fe6f40 : 00000000`00000000 fffff880`02fdb180 00000000`00045302 fffff880`009faad0 : 0xfffff880`009fa9c0
fffff880`009fa8e0 00000000`00000000 : fffff880`02fdb180 00000000`00045302 fffff880`009faad0 00000000`00140001 : 0xfffff880`02fe6f40

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!SepNormalAccessCheck+bd
fffff803`b2305a5d 8b5f18          mov     ebx,dword ptr [rdi+18h]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!SepNormalAccessCheck+bd
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  51a966cd
IMAGE_VERSION:  6.2.9200.16628
BUCKET_ID_FUNC_OFFSET:  bd
FAILURE_BUCKET_ID:  AV_VRF_nt!SepNormalAccessCheck
BUCKET_ID:  AV_VRF_nt!SepNormalAccessCheck
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:av_vrf_nt!sepnormalaccesscheck
FAILURE_ID_HASH:  {d6151822-d95f-ba30-af1e-fa1915ee7ebb}
Followup: MachineOwner

Info on bsod taken from John Carrona BSOD Index

Cause
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 you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.

Try disabling memory caching of the BIOS.

Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.

With a single BSOD, this is difficult to diagnose

Please do the following:.(credit to Usasma)
- open Event Viewer (run eventvwr.mscfrom the "Run" dialog))
- expand the Custom Views category (leftclick on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in CustomView as..."
- save the file as Admin.evtx
- zip up the file (right click on it,select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it'stoo big, then upload it to a free file-hosting service and post a link here).

You mentioned you still can not get updates from windows update.
Check your system with SFC/Scannow (3 x) and DISM see this tutorial http://www.eightforums.com/tutorials/3047-sfc-scannow-command-run-windows-8-a.html

IcEmAn34 · Apr 1, 2014

It says:"The system cannot find the file specified," when I try to save all events in customview... :\

About updates... I ran factory reset couple of hours ago, did all the updates, updated to windows 8.1, also updated everything and first thing it did: BSOD whic I pasted in previous post. SFS/scannow never showed any problems (and I did it more than 10 times until now)

lifetec · Apr 1, 2014

http://1drv.ms/1dLcwh4

i can not download this file.

usasma · Apr 2, 2014

In most cases like this, repeated BSOD's after reinstalling the OS are primarily due to hardware issues.
You stated previously that you've run all the hardware diagnostics - which one's have you run?
I maintain a list of free diagnostics here: Hardware Diagnostics

As this system is still under warranty, I'd suggest that you return it for service.
Be sure to specify the exact steps that it takes to make the system BSOD (that way the tech's at the service center can verify it).

Additionally, this latest memory dump blames hardware. Include that in the information that you send to the service center.

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Tue Apr  1 16:56:50.408 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\040114-5062-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].16452.amd64fre.winblue_gdr.131030-1505
System Uptime:[B]0 days 0:04:16.231[/B]
Probably caused by :[B]hardware ( nt!KiCallInterruptServiceRoutine+116 )[/B]
BugCheck [B]3D, {ffffd0002099b540, 0, 0, fffff803638a03b6}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003D]INTERRUPT_EXCEPTION_NOT_HANDLED (3d)[/url]
Arguments: 
Arg1: ffffd0002099b540
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff803638a03b6
BUGCHECK_STR:  0x3D
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]IP_MISALIGNED[/B]
CPUID:        "Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: [B]2195[/B]
  BIOS Version                  V1.13
  BIOS Release Date             10/11/2013
  Manufacturer                  Acer
  Product Name                  Aspire V3-772
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Tue Apr  1 16:56:50.408 2014 (UTC - 4:00)**************************
btath_lwflt.sys             Fri Nov  2 01:35:44 2012 (50935BB0)
btath_hcrp.sys              Tue Dec 18 04:54:54 2012 (50D03D6E)
RadioShim.sys               Wed Jan  9 06:23:09 2013 (50ED531D)
LMDriver.sys                Wed Jan  9 06:23:09 2013 (50ED531D)
btath_bus.sys               Mon Jan 21 04:18:42 2013 (50FD07F2)
ETD.sys                     Fri May 17 06:36:39 2013 (51960837)
btath_rcp.sys               Fri Jun 21 05:11:54 2013 (51C418DA)
iaStorA.sys                 Thu Aug  1 21:39:52 2013 (51FB0DE8)
dump_iaStorA.sys            Thu Aug  1 21:39:52 2013 (51FB0DE8)
TeeDriverx64.sys            Mon Aug 19 13:23:31 2013 (52125493)
intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
btath_flt.sys               Thu Aug 22 23:46:29 2013 (5216DB15)
RTKVHD64.sys                Tue Aug 27 08:31:56 2013 (521C9C3C)
nvlddmkm.sys                Mon Oct 28 17:38:03 2013 (526ED93B)
nvpciflt.sys                Mon Oct 28 17:38:28 2013 (526ED954)
k57nd60a.sys                Wed Oct 30 03:14:03 2013 (5270B1BB)
btath_avdt.sys              Fri Nov 22 02:15:28 2013 (528F0490)
btath_a2dp.sys              Fri Nov 22 02:17:31 2013 (528F050B)
athw8x.sys                  Mon Dec  2 03:17:07 2013 (529C4203)
iwdbus.sys                  Tue Dec 17 17:47:38 2013 (52B0D48A)
btfilter.sys                Fri Dec 20 02:42:05 2013 (52B3F4CD)
igdkmd64.sys                Wed Jan 22 17:42:16 2014 (52E04948)
[/font]

boss580 · Apr 2, 2014

multipl BSODs

Dear sir;
I use lenovo z510i i7 4702QM 8gb laptop.Nearly everyday i'm getting a bsod while working.I only use my laptop for my job,never play games or make hard use.I belive that bsods are from device drivers of microsoft.All intel and nvidia drivers are updated from their own sites and other from lenovos site.*.zip file attached to this message contains the dump file of last crash.if you can help me to identify the reason of BSODs I'll be very glad.Thanks for all

lifetec · Apr 2, 2014

Hi Boss580,

First could you start a new post/ thread for yourself

And could you run the SF tool again and use grab all.

boss580 · Apr 2, 2014

Sorry but I didn't understand.Which tool ı have to run again?

boss580 · Apr 2, 2014

Now I send the *.docx file attached that created by "whocrashed" which contains the summary of dump files,maybe it can be helpfull
[FONT=&quot]On Sun 30.03.2014 16:36:50 GMT your computer crashed[/FONT][FONT=&quot]
crash dump file: C:\WINDOWS\Minidump\033014-19000-01.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]ntoskrnl.exe[/FONT][FONT=&quot] (nt+0x14DCA0)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF8020A6B297F)
Error: [/FONT][FONT=&quot]IRQL_NOT_LESS_OR_EQUAL[/FONT][FONT=&quot]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [/FONT][FONT=&quot]Microsoft® Windows® Operating System[/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Microsoft Corporation[/FONT][FONT=&quot]
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]
[FONT=&quot]On Fri 28.03.2014 09:47:50 GMT your computer crashed[/FONT][FONT=&quot]
crash dump file: C:\WINDOWS\Minidump\032814-20250-01.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]ntoskrnl.exe[/FONT][FONT=&quot] (nt+0x14DCA0)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF803E344697F)
Error: [/FONT][FONT=&quot]IRQL_NOT_LESS_OR_EQUAL[/FONT][FONT=&quot]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [/FONT][FONT=&quot]Microsoft® Windows® Operating System[/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Microsoft Corporation[/FONT][FONT=&quot]
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]
[FONT=&quot]On Thu 27.03.2014 09:53:59 GMT your computer crashed[/FONT][FONT=&quot]
crash dump file: C:\WINDOWS\Minidump\032714-19734-01.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]ntoskrnl.exe[/FONT][FONT=&quot] (nt+0x14DCA0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: [/FONT][FONT=&quot]DPC_WATCHDOG_VIOLATION[/FONT][FONT=&quot]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [/FONT][FONT=&quot]Microsoft® Windows® Operating System[/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Microsoft Corporation[/FONT][FONT=&quot]
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]
[FONT=&quot]On Sun 23.03.2014 22:19:11 GMT your computer crashed[/FONT][FONT=&quot]
crash dump file: C:\WINDOWS\Minidump\032414-14156-01.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]ntoskrnl.exe[/FONT][FONT=&quot] (nt+0x14DCA0)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF8020F45797F)
Error: [/FONT][FONT=&quot]IRQL_NOT_LESS_OR_EQUAL[/FONT][FONT=&quot]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [/FONT][FONT=&quot]Microsoft® Windows® Operating System[/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Microsoft Corporation[/FONT][FONT=&quot]
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]
[FONT=&quot]On Sat 22.03.2014 18:56:55 GMT your computer crashed[/FONT][FONT=&quot]
crash dump file: C:\WINDOWS\Minidump\032214-9375-01.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]ntoskrnl.exe[/FONT][FONT=&quot] (nt+0x14DCA0)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF802CB83A97F)
Error: [/FONT][FONT=&quot]IRQL_NOT_LESS_OR_EQUAL[/FONT][FONT=&quot]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [/FONT][FONT=&quot]Microsoft® Windows® Operating System[/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Microsoft Corporation[/FONT][FONT=&quot]
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]
[FONT=&quot]On Thu 20.03.2014 14:29:51 GMT your computer crashed[/FONT][FONT=&quot]
crash dump file: C:\WINDOWS\Minidump\032014-13296-01.dmp
This was probably caused by the following module: [/FONT][FONT=&quot]ntoskrnl.exe[/FONT][FONT=&quot] (nt+0x14DCA0)
Bugcheck code: 0xC4 (0x62, 0xFFFFE000060F5AB8, 0xFFFFE00006199530, 0x1)
Error: [/FONT][FONT=&quot]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT][FONT=&quot]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [/FONT][FONT=&quot]Microsoft® Windows® Operating System[/FONT][FONT=&quot]
company: [/FONT][FONT=&quot]Microsoft Corporation[/FONT][FONT=&quot]
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.[/FONT]

usasma · Apr 3, 2014

boss580 - please start your own topic.

That way your issues will receive the individual attention that they deserve.
And we can continue to give individual attention to IcEmAn34 , who originally started this topic.

Random BSODs in Windows 8 (Acer v3-772g)

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer