BSOD/crashes. IRQL_NOT_LESS_OR_EQUAL

Page 1 of 5 123 ... LastLast

  1. Posts : 24
    Windows 7, 64 bit
       #1

    BSOD/crashes. IRQL_NOT_LESS_OR_EQUAL


    Hi there Seven Forums. I have been having a lot of trouble for over a year now with a computer I put together. I have done a lot of research, tried reinstalling Windows and even tried other versions of Windows 7, but the problem still remains. I spent a lot of money at the time on the machine and I have never really gotten full use out of it as it constantly, at some point, crashes. It can go days without crashing, but it will still crash.

    I have attached the report files as a zip following the Posting Instructions page.

    Asus M4A87TD-USB3 | 4G Kit ddr3 1333 Kingston (2x2GB) | AM3 x4 955 - AMD Phenom(tm) II X4 955 Processor 3.20 GHz (stock cooler, no over clock) | 1gb GTX 460 Gigabyte (GPU) | Antec TruePower TP-550 | and a SATA DVD drive and hard drive

    It rates 5.4 on the Windows Experience Index due to Disk data transfer rate, otherwise it would be 7.3.

    I have Windows 7 64 bit on there. I have formatted the drive and reinstalled Windows 7 three times now (although it is possible, though extremely improbable, that a virus snuck in there when a USB drive was attached).
    The two most common BSOD messages have been:

    IRQL_NOT_LESS_OR_EQUAL

    STOP: 0x0000000A (0xFFFFFC0003452588, 0x0000000000000002, 0x0000000000000001, 0xFFFFF800032C89A4)

    and

    STOP: 0x0000001E (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

    I have burned Ultimate Boot CD and ran a scan on the video memory, that ran for 40 hours with no errors until I stopped it to run another test. I then ran a test on the memory, that ran fine also. I couldn't run any CPU tests from the CD, so I ran Prime95 from Windows itself, and that ran for 40 hours before the computer restarted while I was out of the room. The computer was running at 100 percent CPU according to task manager during this test. According to SpeedFan temps during this test did not go over 86 degrees, the fan would run faster to push the temps down, so that seemed to be running fine. With nothing running temps are about 36 degrees.
    I have reset the BIOS in the BIOS settings, I have reset CMOS using UBCD and I even zero formatted the hard drive on the last reinstall. I clean it for dust, but it doesn't really look like overheating is the problem.

    Nothing has driven me more crazy than this computer. I don't understand programming and bug reports, but it looks like Seven Forums is much more used to these problems than any of the other forums I've visited for help, so fingers crossed that whatever is causing these problems can be fixed or replaced!
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #2

    Your most recent dump files are nearly five months old. Please follow the steps in Dump Files - Configure Windows to Create on BSOD to create more recent .dmp files. I will attempt to analyze the old files now...

    Code:
    1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Windows7Blues\report\Windows_NT6_BSOD_jcgriff2\080911-21481-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50 Debug session time: Mon Aug 8 07:42:04.652 2011 (UTC - 7:00) System Uptime: 0 days 2:15:41.400 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff300010885c0, 0, fffff80002e9e9e3, 7} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+c3 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff300010885c0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002e9e9e3, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c10e0 fffff300010885c0 FAULTING_IP: nt!MiAgeWorkingSet+c3 fffff800`02e9e9e3 45847cc500 test byte ptr [r13+rax*8],r15b MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880033167a0 -- (.trap 0xfffff880033167a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000001027 rbx=0000000000000000 rcx=0000000000000007 rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002e9e9e3 rsp=fffff88003316930 rbp=fffff70001080000 r8=0000000000000001 r9=fffffa8005873ec8 r10=0000000000000005 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy nt!MiAgeWorkingSet+0xc3: fffff800`02e9e9e3 45847cc500 test byte ptr [r13+rax*8],r15b ds:2ec2:00000000`00008138=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002f08b19 to fffff80002e8af00 STACK_TEXT: fffff880`03316638 fffff800`02f08b19 : 00000000`00000050 fffff300`010885c0 00000000`00000000 fffff880`033167a0 : nt!KeBugCheckEx fffff880`03316640 fffff800`02e88fee : 00000000`00000000 00000000`00000022 00000000`00001000 fffff800`02fbdbfe : nt! ?? ::FNODOBFM::`string'+0x40edb fffff880`033167a0 fffff800`02e9e9e3 : 00000000`00000faf 00000000`00000001 00000000`00000000 00000000`00000fae : nt!KiPageFault+0x16e fffff880`03316930 fffff800`02f0ba0e : fffffa80`05873ec8 fffff880`00000001 00000000`00000001 fffff880`03316bb0 : nt!MiAgeWorkingSet+0xc3 fffff880`03316ae0 fffff800`02e9f6e2 : 00000000`00001fce 00000000`00000000 fffffa80`00000000 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x49926 fffff880`03316b80 fffff800`02e9f96f : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`03316bd0 fffff800`0312e166 : fffffa80`039f2680 00000000`00000080 fffffa80`03973890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3 fffff880`03316d40 fffff800`02e69486 : fffff880`02f63180 fffffa80`039f2680 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03316d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiAgeWorkingSet+c3 fffff800`02e9e9e3 45847cc500 test byte ptr [r13+rax*8],r15b SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiAgeWorkingSet+c3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+c3 BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+c3 Followup: MachineOwner ---------
    2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Windows7Blues\report\Windows_NT6_BSOD_jcgriff2\081311-19843-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03040e50 Debug session time: Sat Aug 13 03:55:43.414 2011 (UTC - 7:00) System Uptime: 0 days 0:02:57.162 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41287, 40, 0, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041287, The subtype of the bugcheck. Arg2: 0000000000000040 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41287 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800627f6c0 -- (.trap 0xfffff8800627f6c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000040 rdx=7ff0000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002e80170 rsp=fffff8800627f850 rbp=0000000000000000 r8=fffff680003bbc40 r9=fffffa8000000000 r10=0000000fffffffff r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!ObFastReferenceObject+0x10: fffff800`02e80170 4c8b01 mov r8,qword ptr [rcx] ds:0488:00000000`00000040=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e1fb6e to fffff80002e74f00 STACK_TEXT: fffff880`0627f558 fffff800`02e1fb6e : 00000000`0000001a 00000000`00041287 00000000`00000040 00000000`00000000 : nt!KeBugCheckEx fffff880`0627f560 fffff800`02e72fee : 00000000`00000000 00000000`00000044 00000000`63416d00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42c75 fffff880`0627f6c0 fffff800`02e80170 : fffff700`01080000 fffffa80`03729090 fffff680`003bbaa0 fffffa80`03b5d3f8 : nt!KiPageFault+0x16e fffff880`0627f850 fffff800`02ee4380 : 00000000`00000045 00000000`00000044 00000000`00000000 fffffa80`03c88238 : nt!ObFastReferenceObject+0x10 fffff880`0627f880 fffff800`02e9b353 : 84500001`26303025 80000001`26303121 fffff700`01080488 fffffa80`03b5d3f8 : nt! ?? ::FNODOBFM::`string'+0x298f3 fffff880`0627f910 fffff800`02e90d9e : 00000000`00000000 00000000`77754e71 fffff680`003bbaa0 fffffa80`03b5d3f8 : nt!MiResolveProtoPteFault+0x1d3 fffff880`0627f9b0 fffff800`02e8ef23 : 00000000`00000000 00000000`77754e71 00000000`00000000 fffff800`00000000 : nt!MiDispatchFault+0x1de fffff880`0627fac0 fffff800`02e72fee : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : nt!MmAccessFault+0x343 fffff880`0627fc20 00000000`7768e5dd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0011f3f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7768e5dd STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+42c75 fffff800`02e1fb6e cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+42c75 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75 BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75 Followup: MachineOwner ---------
    Those .dmp files were inconclusive and pointed to system files. This could be due to corruption, a virus, lack of Windows updates, hardware, or an underlying driver problem.

    Run the following steps and post back after doing each one.
    1. Run a Disk Check with both boxes checked.
    2. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors.
    3. Check for viruses.
      Download and install the free version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download (do not start the trial) and make sure it is updated. Do not run a scan yet.
      Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software but do not unzip it yet
      Download the Fakerean removal tool but do not run it yet.
      Start your computer in Safe Mode
      Unzip VIPRE Rescue and let it run.
      Run a full scan with Malwarebytes.
      Run the fakerean removal tool.
    4. Install all Windows Updates device drivers (see Installing and updating drivers in 7, Driver Reference and Drivers and Downloads for driver updating).
    5. Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete.
    6. Run Driver Verifier to find any underlying driver issues. To run Driver Verifier, do the following:
      a. Backup your system and user files
      b. Create a system restore point
      c. If you do not have a Windows 7 DVD, Create a system repair disc
      d. Run Driver Verifier

      If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

      Thanks to zigzag3143 for contributing to the Verifier steps.
      If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.


    You may also want to update your chipset drivers from your motherboard's support site Asus M4A87TD-USB3.
      My Computer


  3. Posts : 24
    Windows 7, 64 bit
    Thread Starter
       #3

    I have made sure that the dump settings are set correctly using option 1, nothing needed to be changed as it was set already. I'll leave the computer on in the hopes of another BSOD, it will be on in any case during these scans.

    Disk Check with both boxes checked running now. It seemed to run okay. When step five finished, it was too quick for me to read any messages that came up. I'll run the SCANNOW command now.
      My Computer


  4. Posts : 24
    Windows 7, 64 bit
    Thread Starter
       #4

    SCANNOW is complete.

    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some them.
    Details are included in the CBS.Log windir/Logs/CBS/CBS.log. For example C:/Windows/Logs/CBS/CBS.log

    I have attached that log file to this post.

    I'll now move on to step 3, check for viruses.
      My Computer


  5. Posts : 24
    Windows 7, 64 bit
    Thread Starter
       #5

    Doing the virus scans now. No threat traces detected for the VIPRER scan. Full scan for Malwarebytes complete, No malicious items were detected. Fakerean ran, it was very quick, I couldn't see any messages that came up for it. Will move on to the next step, updating Windows drivers.
      My Computer


  6. Posts : 24
    Windows 7, 64 bit
    Thread Starter
       #6

    Scan for Windows Drivers (Driver Scanner 2012). 15 devices have outdated drivers, including HID Keyboard Device, Nvidia Geforce GTX 460, Realtek PCIe GBE Family Controller, USB Input Devices, NVIDIA High Definition Audio, Standard Dual Channel PCI IDE Controller. Need to purchase to download the drivers with this utility.

    I will have to download these drivers later, the Nvidia driver alone will push me over my internet data cap.

    Moving into the Memtest86+ boot version test.
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #7

    Windows7Blues said:
    I have made sure that the dump settings are set correctly using option 1, nothing needed to be changed as it was set already. I'll leave the computer on in the hopes of another BSOD, it will be on in any case during these scans.

    Disk Check with both boxes checked running now. It seemed to run okay. When step five finished, it was too quick for me to read any messages that came up. I'll run the SCANNOW command now.
    To check log for the disk check, see Check Disk (chkdsk) - Read Event Viewer Log and post back what the log says.
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #8

    Windows7Blues said:
    SCANNOW is complete.

    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some them.
    Details are included in the CBS.Log windir/Logs/CBS/CBS.log. For example C:/Windows/Logs/CBS/CBS.log

    I have attached that log file to this post.

    I'll now move on to step 3, check for viruses.
    Below are the errors sfc found. Did you run it three times? You were not clear. If you have already run it three times and it is still unable to fix the corruptions, see Extract Files from Windows 7 Installation DVD for how to manually replace the corrupted files using the Windows 7 installation DVD.

    Code:
    2012-01-10 18:43:28, Info                  CSI    00000299 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2012-01-10 18:43:29, Info                  CSI    0000029b [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2012-01-10 18:43:29, Info                  CSI    0000029c [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
    2012-01-10 18:43:29, Info                  CSI    0000029f [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
    2012-01-10 18:44:28, Info                  CSI    000002ea [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2012-01-10 18:44:28, Info                  CSI    000002ec [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2012-01-10 18:44:28, Info                  CSI    000002ed [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
    2012-01-10 18:44:28, Info                  CSI    000002f0 [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #9

    Windows7Blues said:
    Doing the virus scans now. No threat traces detected for the VIPRER scan. Full scan for Malwarebytes complete, No malicious items were detected. Fakerean ran, it was very quick, I couldn't see any messages that came up for it. Will move on to the next step, updating Windows drivers.
    Glad it did not find any viruses/malware.

    Windows7Blues said:
    Scan for Windows Drivers (Driver Scanner 2012). 15 devices have outdated drivers, including HID Keyboard Device, Nvidia Geforce GTX 460, Realtek PCIe GBE Family Controller, USB Input Devices, NVIDIA High Definition Audio, Standard Dual Channel PCI IDE Controller. Need to purchase to download the drivers with this utility.

    I will have to download these drivers later, the Nvidia driver alone will push me over my internet data cap.

    Moving into the Memtest86+ boot version test.
    Sorry to hear you will not be able to update your drivers due to internet restrictions... I also do not recommend purchasing driver updaters since you can find the information for free using the links I gave in my first post.
      My Computer


  10. Posts : 24
    Windows 7, 64 bit
    Thread Starter
       #10

    Oh, three times, sorry I missed that. When Memtest86 is done I will report the log for Check Disk and run SCANNOW three more times. Should I save the log from each time, or is the message it gives at the end enough to know if it worked or not?
      My Computer


 
Page 1 of 5 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About 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 13:22.
Find Us