BSOD at Random Time


  1. tank79
    Posts : 3
    Windows 7 64bit
       New #1

    BSOD at Random Time


    First and foremost any help would be greatly appreciated. I have basically pulled my hair out here trying to fix this.

    For the past two weeks I keep getting a BSOD. At first it was very sporadic and now it is becoming very frequent.

    I get "IRQL_NOT_EQUAL_OR_LESS_"

    I have attempted the following:
    Ran virus scanner
    uninstalled all programs within the past two months
    updated all drivers
    ran CMD "SFD/scannow" (no errors)
    Ran Windows Memory Diagnostic Tool (came back as no errors)

    As per the instructions of serven form's, here is the download link to the file with the minidump.
    https://www.dropbox.com/sh/w5r5yrv02...ows%207%20Form

    Here is the scan from whocrashed:
    System Information (local)
    --------------------------------------------------------------------------------


    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Celeron(R) CPU 900 @ 2.20GHz Intel586, level: 6
    1 logical processors, active mask: 1
    RAM: 3149078528 total
    VM: 2147352576, free: 1937977344




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

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 2/17/2013 2:52:13 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-28797-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x7717138A, 0x1, 0x0, 0xFFFFF88008C73C60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    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 2/17/2013 2:52:13 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: 0x4A (0x7717138A, 0x1, 0x0, 0xFFFFF88008C73C60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    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 2/17/2013 2:38:40 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-31247-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x776D138A, 0x1, 0x0, 0xFFFFF88008AD8C60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    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 2/17/2013 2:13:34 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-27112-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x770B138A, 0x1, 0x0, 0xFFFFF88007AF7C60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    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 2/17/2013 2:04:30 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-28844-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x76F5138A, 0x1, 0x0, 0xFFFFF88002CF0C60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    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 2/17/2013 1:53:39 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-32963-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x7778138A, 0x1, 0x0, 0xFFFFF8800841EC60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    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 2/17/2013 1:27:04 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-34273-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x77C1138A, 0x1, 0x0, 0xFFFFF88007E84C60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    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 2/17/2013 1:16:09 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-26192-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x77A4138A, 0x1, 0x0, 0xFFFFF880085B9C60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 2/16/2013 11:02:47 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-37393-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x77A4138A, 0x1, 0x0, 0xFFFFF8800787CC60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 2/16/2013 10:37:37 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-77813-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x775E138A, 0x1, 0x0, 0xFFFFF8800839AC60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 2/16/2013 10:29:51 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-77423-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x76DE138A, 0x1, 0x0, 0xFFFFF88008E84C60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 2/16/2013 9:57:55 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-83585-01.dmp
    This was probably caused by the following module: ndis.sys (0xFFFFF88001CC1566)
    Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88001CC1566)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NDIS 6.20 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 that cannot be identified at this time.



    On Sat 2/16/2013 8:57:48 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-37065-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x7715138A, 0x1, 0x0, 0xFFFFF8800929DC60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 2/16/2013 5:43:54 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-65692-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x77CA138A, 0x1, 0x0, 0xFFFFF88007A0FC60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 2/16/2013 4:51:59 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021613-24492-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0x4A (0x7792138A, 0x1, 0x0, 0xFFFFF88008425C60)
    Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
      My Computer
    Quote Quote

  3. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #2

    Blue Screen of Death (BSOD) Posting Instructions
      My Computer
    Quote Quote

  4. tank79
    Posts : 3
    Windows 7 64bit
    Thread Starter
       New #3

    Zip file from instructions
      My Computer
    Quote Quote

  6. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #4

    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 Computer
    Quote Quote

  7. tank79
    Posts : 3
    Windows 7 64bit
    Thread Starter
       New #5

    Thanks Koolkat77. Please see attached.
      My Computer
    Quote Quote

  8. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #6

    Please remove this software:
    Code:
    Start Menu\Programs\DriverUpdate	Public:Start Menu\Programs\DriverUpdate	Public
    Find drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads

    Avast! sometimes contributes in BSOD-s. Please uninstall for testing purpose:
    Code:
    Start Menu\Programs\avast! Free Antivirus	Public:Start Menu\Programs\avast! Free Antivirus	Public


    Make scans with the following:

    -Kaspersky TDSSKiller

    -ESET online scanner

    Microsoft Security Essentials.

    Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

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

    I just noticed you have MSE and Avast! both installed. Keeping two antiviruses on your system can cause serious conflicts.


    Update the following drivers in the method below:

    Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:
    Code:
    CHDRT64
start             end                 module name
fffff880`05929000 fffff880`059d7000   CHDRT64  T (no symbols)           
    Loaded symbol image file: CHDRT64.sys
    Image path: \SystemRoot\system32\drivers\CHDRT64.sys
    Image name: CHDRT64.sys
    Timestamp:        Sat Feb 27 07:55:00 2010 (4B887B74)
    CheckSum:         000B2712
    ImageSize:        000AE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

athrx
start             end                 module name
fffff880`04610000 fffff880`0477f000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Thu Jul 09 06:49:13 2009 (4A553E89)
    CheckSum:         0016D79F
    ImageSize:        0016F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    or:
    If its wireless, match your device from here:

    If its not a wireless, match your device from here:
    Perform a System File Check to check the integrity of all protected Windows 7 :
    1. Click on the start
    2. Type CMD on Search
    3. Left click and Run as Administrator
    4. Type
      Code:
      SFC /scannow

    Full tutorial here:

    Disk Check on your hard drive for file system errors and bad sectors on it.

    Reduce items at start-up. Nothing except anti-virus is required.

    Let us know the results and further BSOD reports.
      My Computer
    Quote Quote

  10. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #7

    Were the steps above helpful?
    Any new blue screens?
      My Computer
    Quote Quote

 

  Related Discussions
Hey Guys, My PC has been running great for about 3years then all of a suddenly i've started getting BSOD. Only thing i can think of was on the day they started, i installed Borderlands Pre sequel to play with my girlfriend. When it happened i realised my watercooling pump had packed...
Dear 7 Master, i have an issue on my computer server. im using Windows 7 Home Professional 64 Bit. Actually i m not sure it's whether BSOD or not, because im not monitoring it 24 hours. Almost everyday...i found a notification massage : "windows has recovered from an unexpected shutdown...&...
Any Random Time BSOD
in BSOD Help and Support

This is the second time this has apprehend have now idea what the problem is.
Random BSoD at Any Time?
in BSOD Help and Support

Well, just as the title suggests, my computer gets the BSoD fairly often, almost once a day now. I could be getting ready to play a game, browsing the internet, or just have my computer on my desktop, go eat dinner, and see that it had a BSoD when I come back. My computer is around one month old,...
Hello. I have been experiencing bluee screens of death in the last 9 months. Sometime , at 3-4 days it just happens , randomly. I hope you guys can help me. System specs : Intel Quad Core 2.5 GHZ 8 GB RAM ATi RADEON 5850 HD
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 05:04.
Find Us