Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD IRQL_NOT_LESS_OR_EQUAL when using Google Earth

13 Jan 2015   #1
Newuser1234

Windows 7 Professional 64 bit
 
 
Random BSOD IRQL_NOT_LESS_OR_EQUAL when using Google Earth

Hello,

I am getting some random BSODs when browsing the internet and using google earth. Some drivers are mentioned a couple times, but it is not always the same issue. Any help would be massively appreciated.

Thanks!

See attached


My System SpecsSystem Spec
.
14 Jan 2015   #2
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff8a01be58448, 99b000012cbb5910, fffff88007c720c0, e}

*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by : aswSnx.sys ( aswSnx+298d0 )

Followup: MachineOwner
---------
Replace Avast with MSE - uninstall Avast completely first before installing MSE.

Code:
fffff880`0ff57580  fffffa80`1024ea90
fffff880`0ff57588  fffff880`0432c677 dxgmms1!VidSchiProcessIsrCompletedPacket+0x1eb
fffff880`0ff57590  00000000`00000001
fffff880`0ff57598  fffff880`0418dfbfUnable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag+0x40fbf
fffff880`0ff575a0  fffffa80`1024d000
fffff880`0ff575a8  fffffa80`0e7b9440
fffff880`0ff575b0  fffff880`0ff57680
fffff880`0ff575b8  00000000`00000000
fffff880`0ff575c0  fffff800`03243e80 nt!KiInitialPCR+0x180
fffff880`0ff575c8  fffff880`0ff58c40
fffff880`0ff575d0  00000000`00000080
fffff880`0ff575d8  fffffa80`102908b0
fffff880`0ff575e0  fffff800`03251cc0 nt!KiInitialThread
fffff880`0ff575e8  00000000`00000000
fffff880`0ff575f0  fffffa80`0e7aa040
fffff880`0ff575f8  00000000`00000001
fffff880`0ff57600  fffffa80`00000001
fffff880`0ff57608  00000000`00000000
fffff880`0ff57610  00000000`00000000
fffff880`0ff57618  fffffa80`0c742040
fffff880`0ff57620  fffff800`00b96080
fffff880`0ff57628  fffff800`030b98e6 nt!KxStartSystemThread+0x16
fffff880`0ff57630  00000003`00000018
fffff880`0ff57638  00000008`00000002
fffff880`0ff57640  fffff880`0ff57ca0
fffff880`0ff57648  00000001`00001f80
fffff880`0ff57650  00000000`00000000
fffff880`0ff57658  00000000`00000000
fffff880`0ff57660  fffff880`0ff58010
fffff880`0ff57668  fffff880`048ccee9Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0xb9ee9
fffff880`0ff57670  fffffa80`0e1bf020
fffff880`0ff57678  fffff880`0ff580b0
.
fffff880`04813000 fffff880`05384000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Thu Apr 25 06:37:05 2013 (51784979)
    CheckSum:         00B25972
    ImageSize:        00B71000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
Name	AMD Radeon HD 8450G
Check for and install the latest video drivers for the Radeon card.
My System SpecsSystem Spec
14 Jan 2015   #3
Newuser1234

Windows 7 Professional 64 bit
 
 

Thank you!! I actually uninstalled Avast and then installed MSE. I also ran the autodetect to install all of the amd drivers from Download Drivers .

I am not having any of the atikmdag.sys issues anymore. I just actually had another BSOD for the ntoskrnl.exe.

Maybe a new dump will help. Perhaps it is a memory issue?

Thanks for the help!!!
My System SpecsSystem Spec
.

14 Jan 2015   #4
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

I'll have a look at this tonight when I get home.
My System SpecsSystem Spec
15 Jan 2015   #5
Newuser1234

Windows 7 Professional 64 bit
 
 

Awesome thanks. I am also running memtest86 and am pulling up some errors on Test 7. I'll post my whocrashed analysis if it might help.

Thanks!!


System Information (local)
--------------------------------------------------------------------------------

computer name: COMPUTER
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: 20B20011US, LENOVO
CPU: AuthenticAMD AMD A6-5350M APU with Radeon(tm) HD Graphics AMD586, level: 21
2 logical processors, active mask: 3
RAM: 16266301440 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 1/15/2015 12:50:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011415-23415-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x99, 0x21E94C, 0x0, 0x291DDC)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 1/15/2015 12:50:14 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x21E94C, 0x0, 0x291DDC)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 1/12/2015 3:41:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011115-23056-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x67, 0x2, 0x0, 0xFFFFF800030BCD0C)
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 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.



On Thu 1/8/2015 11:06:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010815-23259-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4785)
Bugcheck code: 0xBE (0xFFFFF8A01BE58448, 0x99B000012CBB5910, 0xFFFFF88007C720C0, 0xE)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 1/1/2015 7:05:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010115-18813-01.dmp
This was probably caused by the following module: vwififlt.sys (vwififlt+0x6753)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\vwififlt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Virtual WiFi Filter Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 12/27/2014 8:31:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122714-29577-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78E94)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030CBE94, 0xFFFFF8800FF58308, 0xFFFFF8800FF57B60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread generated an exception which the error handler did not catch.
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.



On Tue 12/23/2014 5:24:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122314-49233-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x374FA)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF80003101622)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL



On Wed 12/3/2014 2:23:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120214-44039-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80137E7590, 0xFFFFFA80137E7670, 0x40E000F)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

8 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
My System SpecsSystem Spec
15 Jan 2015   #6
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Quote   Quote: Originally Posted by Newuser1234 View Post
Awesome thanks. I am also running memtest86 and am pulling up some errors on Test 7. I'll post my whocrashed analysis if it might help.
In this case, you need to concentrate on RAM first - all other tests can wait.

You must tests each individual stick for 8 passes using MemTest86+, then report back:

Reference:
RAM - Test with Memtest86+
My System SpecsSystem Spec
Reply

 Random BSOD IRQL_NOT_LESS_OR_EQUAL when using Google Earth




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Google Earth?
Google Earth after installation when starts, stalls and stops responding......any ideas why? Thanks.
Software
BSOD irql_not_less_or_equal while on google chrome
Hello, I'm having this issue when I browse with chrome (never use any browser, so any browser not tested yet) and when multiple tabs open in the same window that contain various videos/gifs/etc all of sudden put me on BSOD, really irritate me much. It happened since i installed new avira...
BSOD Help and Support
google earth
having trouble down loading google earth, windows 7 won't let me
Software
Google Earth - Need Help
Hi, I've recently been on a trip around america in an RV and as a school project I have to make some sort of poster out of it. I thought what I would do was show our whole trip on a map, so everyone can see what I did. So I done the whole trip in Google Earth but I have a problem, it's showing...
Chillout Room
Google Earth
Using Win7 RC, Google Earth 5.1 runs fine. Upon installing the released version of Win7 Professional, Google Earth will not run in the DirectX mode. As the program loads, the screen flashes and results in a BSOD. Anyone else having this problem? Could it be that the two versions of Win 7,...
Software
Google Earth
I have problems with installing this software, anyone know a workaround. I have tried compatablity settings and running as admin but I keep getting this error message..
Software


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 02:58.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App