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)

03 Nov 2012   #1
Shotthebunny

Windows 7 Home Premium 64 bit
 
 
Random BSOD (IRQL_NOT_LESS_OR_EQUAL)

I've been getting random BSOD all the time, but it only happens every month or so, so I ignored it. But these few BSOD happened often and recently when I was gaming with Skype on. It doesn't happen when I don't have Skype on. But I don't think that's the case. I'm wondering how to fix this.

My Specs are:

Windows 7 Home Premium 64 BIT
Intel i5 2500K
4 GB PNY ram x2
EVGA 560Ti 1GB
750W Coolmaster

Recent mini dumps via WhoCrashed:

On Sun 11/4/2012 2:34:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110312-28922-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x7D70)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF800032E5468)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 Sun 11/4/2012 12:57:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110312-29374-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC2 (0xB, 0xFFFFFA8008A20A40, 0x5480003, 0xFFFFFA8008A20E50)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 Sun 11/4/2012 12:57:16 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avgidsdrivera.sys (avgidsdrivera+0x1567C)
Bugcheck code: 0xC2 (0xB, 0xFFFFFA8008A20A40, 0x5480003, 0xFFFFFA8008A20E50)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\avgidsdrivera.sys
product: AVG IDS
company: AVG Technologies CZ, s.r.o.
description: IDS Application Activity Monitor Driver.
Bug check description: This indicates that the current thread is making a bad pool request.
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: avgidsdrivera.sys (IDS Application Activity Monitor Driver., AVG Technologies CZ, s.r.o. ).
Google query: AVG Technologies CZ, s.r.o. BAD_POOL_CALLER



On Sun 11/4/2012 12:51:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110312-31839-01.dmp
This was probably caused by the following module: volsnap.sys (volsnap+0x176A2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFF8800377F8D8, 0xFFFFF8800377F130)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\volsnap.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Shadow Copy 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.
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 11/3/2012 8:43:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110312-30591-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800032D3242)
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 Fri 11/2/2012 4:13:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110212-37502-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x99, 0x1BD763, 0x0, 0x1BD7E3)
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.

Any help is greatly appreciated.


My System SpecsSystem Spec
.
03 Nov 2012   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

My System SpecsSystem Spec
04 Nov 2012   #3
Shotthebunny

Windows 7 Home Premium 64 bit
 
 

Sorry, here is the dump files.
My System SpecsSystem Spec
.

04 Nov 2012   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Quote   Quote: Originally Posted by Shotthebunny View Post
Sorry, here is the dump files.
The .nfo file does not seem to load:

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.
My System SpecsSystem Spec
04 Nov 2012   #5
Shotthebunny

Windows 7 Home Premium 64 bit
 
 

Here are the msinfo32.nfo files
My System SpecsSystem Spec
04 Nov 2012   #6
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

OK it loaded.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {b, fffffa8008a20a40, 5480003, fffffa8008a20e50}

Unable to load image \SystemRoot\system32\DRIVERS\avgidsdrivera.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgidsdrivera.sys
*** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
Probably caused by : avgidsdrivera.sys ( avgidsdrivera+1567c )

Followup: MachineOwner
---------
Please uninstall AVG antivirus, its causing BSOD-s for you. Uninstall using the free version Revo Uninstallers Advanced Mode.REBOOT
Recommended antivirus program for Windows 7 based on stability compared to others:-
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Look for possible driver update on Etron USB 3.0 Extensible Host Controller Drivers.
Driver Reference Table
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:Run Disk Check on your hard disk for file system errors and bad sectors on it:Let us know if the system is more stable, will do more troubleshooting if needed.
My System SpecsSystem Spec
04 Nov 2012   #7
Shotthebunny

Windows 7 Home Premium 64 bit
 
 

Unfortunately, I'm still getting the IRQL_NOT_LESS_OR_EQUAL BSOD. I've done everything you said to do. Here are the files again.
My System SpecsSystem Spec
04 Nov 2012   #8
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

You need to update the drivers of your video card. The latest drivers for NVIDIA are a little problematic as I've heard. Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; NVIDIA Reboot the system. Now delete remnants of its drivers using Driver Fusion/Sweeper. Reboot if required

Download and install the drivers from the link of Filehippo bellow:Run Disk Check on your hard disk for file system errors and bad sectors on it:For monitoring the heat/celsius of the system, use Speccy or HWinfo:
My System SpecsSystem Spec
04 Nov 2012   #9
Shotthebunny

Windows 7 Home Premium 64 bit
 
 

I'm don't think it's the driver's problem. The BSOD stated that it was caused by volsnap.sys but the System File Checker didn't find anything wrong. Is there a way to replace the volsnap.sys? And this certain BSOD only seem to appear when I game and Skype at the same time.
My System SpecsSystem Spec
04 Nov 2012   #10
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

This is what shows up on the .dmp file of 04-11-2012\110412-22230-01.dmp hence my suggestion on updating the driver.

Quote:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
Source: Carrona.org
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {3, 2, 1, fffff8800f15b78e}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+8578e )

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: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800f15b78e, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c4100
 0000000000000003 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+8578e
fffff880`0f15b78e 488919          mov     qword ptr [rcx],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Gw2.exe

TRAP_FRAME:  fffff8800ec43ec0 -- (.trap 0xfffff8800ec43ec0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8009a305c8 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f15b78e rsp=fffff8800ec44050 rbp=fffff8800ec440a0
 r8=fffff8800ec44080  r9=0000000000000000 r10=0000000000000000
r11=fffff88002f65180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nvlddmkm+0x8578e:
fffff880`0f15b78e 488919          mov     qword ptr [rcx],rbx ds:c750:00000000`00000003=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003294569 to fffff80003294fc0

STACK_TEXT:  
fffff880`0ec43d78 fffff800`03294569 : 00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0ec43d80 fffff800`032931e0 : 00000000`00152c48 00000000`00000000 fffff880`02f65180 fffffa80`0a369418 : nt!KiBugCheckDispatch+0x69
fffff880`0ec43ec0 fffff880`0f15b78e : fffffa80`0a369600 fffffa80`0a3693d0 fffffa80`0a369610 fffff880`0ec44100 : nt!KiPageFault+0x260
fffff880`0ec44050 fffffa80`0a369600 : fffffa80`0a3693d0 fffffa80`0a369610 fffff880`0ec44100 fffff880`02f65180 : nvlddmkm+0x8578e
fffff880`0ec44058 fffffa80`0a3693d0 : fffffa80`0a369610 fffff880`0ec44100 fffff880`02f65180 fffff880`0f15b72f : 0xfffffa80`0a369600
fffff880`0ec44060 fffffa80`0a369610 : fffff880`0ec44100 fffff880`02f65180 fffff880`0f15b72f 00000000`00000000 : 0xfffffa80`0a3693d0
fffff880`0ec44068 fffff880`0ec44100 : fffff880`02f65180 fffff880`0f15b72f 00000000`00000000 fffffa80`09a30560 : 0xfffffa80`0a369610
fffff880`0ec44070 fffff880`02f65180 : fffff880`0f15b72f 00000000`00000000 fffffa80`09a30560 fffff880`0ec44000 : 0xfffff880`0ec44100
fffff880`0ec44078 fffff880`0f15b72f : 00000000`00000000 fffffa80`09a30560 fffff880`0ec44000 00000000`00000018 : 0xfffff880`02f65180
fffff880`0ec44080 00000000`00000000 : fffffa80`09a30560 fffff880`0ec44000 00000000`00000018 fffff880`0ec441f0 : nvlddmkm+0x8572f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+8578e
fffff880`0f15b78e 488919          mov     qword ptr [rcx],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+8578e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fece178

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+8578e

BUCKET_ID:  X64_0xD1_nvlddmkm+8578e

Followup: MachineOwner
---------
2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f0d6000 fffff880`0fdb7000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 29 04:58:00 2012 (4FECE178)
    CheckSum:         00CC42A5
    ImageSize:        00CE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Quote:
STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
Source: Carrona.org
Other .dmp of 04-11-2012\110412-28766-01 so I suggested Disk Check again.

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

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800ac14828, fffff8800ac14080, fffff8000353d96a}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+1fe0 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800ac14828
Arg3: fffff8800ac14080
Arg4: fffff8000353d96a

Debugging Details:
------------------


EXCEPTION_RECORD:  fffff8800ac14828 -- (.exr 0xfffff8800ac14828)
ExceptionAddress: fffff8000353d96a (nt!FsRtlNotifyCompleteIrpList+0x000000000000004a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000008
Attempt to write to address 0000000000000008

CONTEXT:  fffff8800ac14080 -- (.cxr 0xfffff8800ac14080)
rax=fffffa800765d0b8 rbx=fffff8a00e9fab80 rcx=fffffa800765d010
rdx=0000000000000000 rsi=000000000000010b rdi=fffff8a00e9fabc0
rip=fffff8000353d96a rsp=fffff8800ac14a60 rbp=0000000000000000
 r8=0000000000000000  r9=000000000000010b r10=fffff8000325e000
r11=0000000000000000 r12=fffff8a00bfaaaf0 r13=fffffa8007ab06a8
r14=fffff8800a5c15f0 r15=fffff8a00bfaaaf0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!FsRtlNotifyCompleteIrpList+0x4a:
fffff800`0353d96a 48897a08        mov     qword ptr [rdx+8],rdi ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  avgcmgr.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000008

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350c100
 0000000000000008 

FOLLOWUP_IP: 
Ntfs!NtfsCommonCleanup+1fe0
fffff880`012bba52 41816704ffff7fff and     dword ptr [r15+4],0FF7FFFFFh

FAULTING_IP: 
nt!FsRtlNotifyCompleteIrpList+4a
fffff800`0353d96a 48897a08        mov     qword ptr [rdx+8],rdi

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff8000352aa3c to fffff8000353d96a

STACK_TEXT:  
fffff880`0ac14a60 fffff800`0352aa3c : fffff8a0`0e9fab80 fffff880`0a5c1840 fffffa80`07570060 00000000`00000008 : nt!FsRtlNotifyCompleteIrpList+0x4a
fffff880`0ac14aa0 fffff800`0352a9cb : fffffa80`07924820 fffff8a0`00133a90 fffff880`0a5c15f0 fffff880`0ac14b60 : nt!FsRtlNotifyCleanupOneEntry+0x28
fffff880`0ac14ad0 fffff880`012bba52 : fffffa80`07924820 fffffa80`07ab0180 fffff8a0`00133bc0 00000000`00000000 : nt!FsRtlNotifyCleanup+0x7b
fffff880`0ac14b20 fffff880`01229c99 : 00000000`00000000 00000000`00000000 fffff880`0a5c1550 fffffa80`07570060 : Ntfs!NtfsCommonCleanup+0x1fe0
fffff880`0ac14f30 fffff800`032d4ab7 : fffff880`0a5c1550 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`0ac14f60 fffff800`032d4a78 : 00000000`00000000 00000000`00000000 fffff880`0ac15000 fffff800`032e8e12 : nt!KySwitchKernelStackCallout+0x27
fffff880`0a5c1420 fffff800`032e8e12 : fffffa80`08757010 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
fffff880`0a5c1440 fffff880`01229d12 : fffff880`01229c80 fffffa80`08dda5d0 fffff880`0a5c1800 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x2a2
fffff880`0a5c1520 fffff880`012c8a94 : fffff880`0a5c15f0 fffff880`0a5c15f0 fffff880`0a5c15f0 4e725346`032eccde : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`0a5c1590 fffff880`01056bcf : fffff880`0a5c15f0 fffffa80`075b0010 fffffa80`075b03b0 fffffa80`089dc010 : Ntfs!NtfsFsdCleanup+0x144
fffff880`0a5c1800 fffff880`010556df : fffffa80`079ac8e0 00000000`00000000 fffffa80`077e7000 fffffa80`075b0010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0a5c1890 fffff800`035e05ef : fffffa80`075b0010 fffffa80`0b582060 00000000`00000000 fffffa80`08dda5d0 : fltmgr!FltpDispatch+0xcf
fffff880`0a5c18f0 fffff800`035cfd14 : 00000000`00000000 fffffa80`0b582060 00000000`00000000 fffff800`032e61dc : nt!IopCloseFile+0x11f
fffff880`0a5c1980 fffff800`035cfad1 : fffffa80`0b582060 fffffa80`00000001 fffff8a0`0c6fca30 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`0a5c1a00 fffff800`035d0094 : 00000000`0000014c fffffa80`0b582060 fffff8a0`0c6fca30 00000000`0000014c : nt!ObpCloseHandleTableEntry+0xb1
fffff880`0a5c1a90 fffff800`032dc253 : fffffa80`07570060 fffff880`0a5c1b60 00000000`7efd5000 fffffa80`076dd270 : nt!ObpCloseHandle+0x94
fffff880`0a5c1ae0 00000000`77a7140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c0e488 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a7140a


SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Ntfs!NtfsCommonCleanup+1fe0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5040d4c6

STACK_COMMAND:  .cxr 0xfffff8800ac14080 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonCleanup+1fe0

BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonCleanup+1fe0

Followup: MachineOwner
---------
Did you remove everything related to AVG?
My System SpecsSystem Spec
Reply

 Random BSOD (IRQL_NOT_LESS_OR_EQUAL)




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD IRQL_NOT_LESS_OR_EQUAL (a)
I get random BSOD. I did try to analyze the dump and got the following output. I am also attaching the minidump as zip file. Thanks ******************************************************************************* * *...
BSOD Help and Support
Random BSOD - IRQL_NOT_LESS_OR_EQUAL
Good Afternoon! Having some trouble with bsod with a laptop with windows 8 preinstalled , so i installed windows 7 instead and im still having randomly bsod commonly irql_not_less_or_equal but sometimes i get Page Fault Found In A Non Paged Area . Attached are the documents requested by the...
BSOD Help and Support
Random BSOD IRQL_NOT_LESS_OR_EQUAL.. Help
Having trouble with random BSOD and shut downs, please help. Thanks in advance.
BSOD Help and Support
Random BSOD: IRQL_NOT_LESS_OR_EQUAL
I'm getting a BSOD randomly. The machine will run flawlessly for a few weeks, and then crash 3 times in a single day. I haven't been able to associate it with any program, event, or activity. Whether I have a hundred programs running in the background, or I keep the number of programs running to...
BSOD Help and Support
Random BSOD , IRQL_NOT_LESS_OR_EQUAL (a)
Hi! I got some BSOD now every day when i play or just watching movies or internet. I have 2 ssd hardrives in raid 0 mode .I need help and i have trayed to read the minidump files. HERE IS THE FIRST ONE: ******************************************************************************* * * *...
BSOD Help and Support
BSOD Random 0xA, IRQL_NOT_LESS_OR_EQUAL
Hello i have noticed Recently that i have been Getting a BSOD i had about 3 Today i have a program called Who Crashed to analyze my Dump Files i will also include BSOD Dump & System File Collection app Files etc PC is about 3 years old (so is all the hardware except the GFX card is like 1 year...
BSOD Help and Support


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 05:29.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App