[NINJAsnowman]

Hi,

I have an ASUS N73SV laptop running Windows 7 64bit premium. For the last several months I've been having regular blue screens. I can't seem to pinpoint exactly when they're happening but its 1 of the following 3 errors:

Driver IQRL not less or equal
Page Fault in nonpaged area
system service exception

I ran memtest86 the other day to check the RAM and it seemed far so that isn't the problem as far as I know... I'll list my hardware specs below and attach my minidump files. Any help would be greatly appreciated!


Intel Core i7-2670QM, 2.2GHz
6GB memory
750gb HDD
Nvidia Geforce 540m Cuda 1GB

Attached Files

•  Minidump.zip   994.3KB   121 downloads

[Advertisements]

Hi NINJAsnowman ... ..


download and install WhoCrashed from http://www.softpedia...oCrashed.shtml' class='bbc_url' title='External link' rel='nofollow external'>here..
This program checks for any drivers which may have been causing your computer to crash....

click on it...then run...then next...put a tick in accept...then next..put a tick in the don't create a start menu folder..then next...put a tick in create a desktop icon..then install.. then make sure there is a tick in launch whocrashed...then finish...then click Analyze ...

if you get a message
This software requires the right version of Windows Debugging Tools for your type of computer. Because this is not normally installed and is not redistributable, we suggest you select the download option from below. Then the right package will be downloaded to a temporary folder and the required files will be extracted from the package automatically. You only need to do this once
click on download then try running it again

WhoCrashed will create report...you have to scroll down to see it
Copy and paste it into your next reply...

[happyrock]

Hi NINJAsnowman ... ..


download and install WhoCrashed from http://www.softpedia...oCrashed.shtml' class='bbc_url' title='External link' rel='nofollow external'>here..
This program checks for any drivers which may have been causing your computer to crash....

click on it...then run...then next...put a tick in accept...then next..put a tick in the don't create a start menu folder..then next...put a tick in create a desktop icon..then install.. then make sure there is a tick in launch whocrashed...then finish...then click Analyze ...

if you get a message
This software requires the right version of Windows Debugging Tools for your type of computer. Because this is not normally installed and is not redistributable, we suggest you select the download option from below. Then the right package will be downloaded to a temporary folder and the required files will be extracted from the package automatically. You only need to do this once
click on download then try running it again

WhoCrashed will create report...you have to scroll down to see it
Copy and paste it into your next reply...

[NINJAsnowman]

Here's the report:


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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 29/03/2012 12:32:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032812-35131-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xAF3E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000DBEF3E, 0xFFFFF880064D9570, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


On Thu 29/03/2012 12:32:52 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltDeleteInstanceContext+0x314E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000DBEF3E, 0xFFFFF880064D9570, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


On Wed 28/03/2012 6:14:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032812-25194-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5ED0A)
Bugcheck code: 0xD1 (0xFFFFF30012078068, 0x2, 0x1, 0xFFFFF880018B9D0A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.


On Wed 28/03/2012 5:52:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032812-23010-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF88003826100, 0x0, 0xFFFFF880014B9787, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.


On Sat 24/03/2012 7:58:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032412-21200-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF10011CE9300, 0x0, 0xFFFFF88002EDEDCA, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.


On Sat 24/03/2012 6:27:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032312-26676-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xC0000221 (0xFFFFF8A0002440C0, 0x0, 0x0, 0x0)
Error: STATUS_IMAGE_CHECKSUM_MISMATCH
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 driver or a system DLL has been corrupted.
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. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 23/03/2012 3:52:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032212-29608-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035A7380, 0xFFFFF880092A9E10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


On Thu 22/03/2012 1:42:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032112-21590-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF100125595B8, 0x1, 0xFFFFF800032CE055, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.


On Tue 20/03/2012 1:44:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031912-19484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xD1 (0x3D, 0x2, 0x0, 0xFFFFF880051C9C1A)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.


On Mon 19/03/2012 9:54:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031912-22136-01.dmp
This was probably caused by the following module: athrx.sys (athrx+0x29F000)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88000F6E90D, 0xFFFFF8800357DD78, 0xFFFFF8800357D5D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
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.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athrx.sys Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Mon 19/03/2012 3:18:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031812-19032-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x18 (0xFFFFFA8005814570, 0xFFFFFA8009981730, 0x1, 0x80000000000)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
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 which cannot be identified at this time.


On Sun 18/03/2012 8:43:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031812-21434-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF880009E4910, 0x1, 0xFFFFF88004AD958A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.


On Sun 18/03/2012 2:05:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031712-20030-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF687FF7E68B8, 0x0, 0xFFFFF80003393947, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.


On Sat 17/03/2012 11:52:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031712-20935-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2EFA00)
Bugcheck code: 0xD3 (0xFFFFF960002FFA00, 0x2, 0x0, 0xFFFFF800032F6E89)
Error: DRIVER_PORTION_MUST_BE_NONPAGED
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that the system attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.


On Fri 16/03/2012 10:59:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031612-19515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF3000BCC7820, 0x0, 0xFFFFF88000F6324A, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.



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

51 crash dumps have been found and analyzed. Only 15 are included in this report. 4 third party drivers have 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:

igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 295.73 , NVIDIA Corporation)

athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

unknown

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

[happyrock]

first run...chkdsk /r
then go here...click on the model automatic detection start button...
I suggest you download all the drivers just in case you need them down the road...burn them to a cd or dvd
install chipset drivers first...reboot...then install the video driver...reboot...install the wireless driver...reboot

[NINJAsnowman]

What is the purpose of "chkdsk /r"? I ran it but it only came up briefly. I updated the drivers the best I could and I'll update in the next few days whether or not this has helped. Thanks!

[happyrock]

What is the purpose of "chkdsk /r"? I ran it but it only came up briefly.

It checks the disk for corrupted files, bad file indexes and other possible causes of program and data failures. It also checks the disk for damaged sectors, and attempts to move data from these to clean sectors...then marks the bad sectors so they will not be used again

type cmd in the search box.....select it from above by right clicking cmd.exe and select
run as administrator to get the cmd prompt to open ...say continue if the UAC challenge pops up
once your at the prompt
type chkdsk /r and press enter...
Chkdsk will display the specific stage it is checking as well as the percentage of completion of the stage. You cannot do anything else on your computer while chkdsk is running. When chkdsk is finished, it will automatically reboot your computer.
NOTE this can take a long time to complete..it may even appear to hang or get stuck at a certain % for a couple of hours...then complete...it may even back up and go over the same area...this is normal...let it run...