BSOD every few hours


  1. tr1x
    Posts : 12
    Windows 7 Ultimate x64
       New #1

    BSOD every few hours


    I'm getting blue screens every few hours, whether I am playing a game, surfing the web, or not even sitting at my computer (I'll come back and it'll be restarted).

    Lately the screen just flashes blue for a split second and the computer restarts, not even enough time to read anything. And those events don't seem to be saved to the minidump.

    Things I've done so far:
    Swap out all the RAM
    Run chkdsk on OS drive
    Reinstall Windows
    Disable paging file (had quite a few blue screens saying something about "paged area" so figured it was worth a shot)
    Take out any removable PCI card (RAID and wifi card)

    I built this PC back in 2010, and only started having any sort of problems about two weeks ago. It's worth noting that I have eight hard drives in it, but they all seem to be working fine, SMART data checks out, etc. OS drive is an SSD - OCZ Vertex 2

    For quick reference, here's the information that BlueScreenViewer gave me:

    ==================================================
    Dump File : 101213-16317-01.dmp
    Crash Time : 10/12/2013 5:10:43 PM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 00000000`00000003
    Parameter 2 : fffff8a0`0fce94e0
    Parameter 3 : fffff8a0`0f479590
    Parameter 4 : fffff8a0`0fce94e0
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\101213-16317-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 287,576
    Dump File Time : 10/12/2013 5:12:11 PM
    ==================================================

    ==================================================
    Dump File : 101213-14211-01.dmp
    Crash Time : 10/12/2013 2:07:11 PM
    Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
    Bug Check Code : 0x00000050
    Parameter 1 : fffff800`02307aa0
    Parameter 2 : 00000000`00000008
    Parameter 3 : fffff800`02307aa0
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\101213-14211-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 285,192
    Dump File Time : 10/12/2013 2:08:17 PM
    ==================================================

    ==================================================
    Dump File : 101213-17690-01.dmp
    Crash Time : 10/12/2013 2:03:51 PM
    Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
    Bug Check Code : 0x00000050
    Parameter 1 : fffff8a0`10c00004
    Parameter 2 : 00000000`00000000
    Parameter 3 : fffff880`043391b6
    Parameter 4 : 00000000`00000002
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\101213-17690-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 268,808
    Dump File Time : 10/12/2013 2:06:58 PM
    ==================================================

    ==================================================
    Dump File : 100913-25568-01.dmp
    Crash Time : 10/9/2013 1:03:08 AM
    Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
    Bug Check Code : 0x00000050
    Parameter 1 : fffff8a0`0f9f4000
    Parameter 2 : 00000000`00000000
    Parameter 3 : fffff800`02f7805f
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75b80
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75b80
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\100913-25568-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 286,768
    Dump File Time : 10/9/2013 1:04:42 AM
    ==================================================

    ==================================================
    Dump File : 100713-16551-01.dmp
    Crash Time : 10/7/2013 12:56:04 PM
    Bug Check String :
    Bug Check Code : 0x00000124
    Parameter 1 : 00000000`00000000
    Parameter 2 : fffffa80`043df8f8
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4ade7c
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+4ade7c
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\100713-16551-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 262,144
    Dump File Time : 10/7/2013 12:56:13 PM
    ==================================================
      My Computer
    Quote Quote

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

    AVG is the cause of your BSOD's. Please remove it.
    Code:
    Probably caused by : avgldx64.sys ( avgldx64+a1b6 )
    Based on the bugchecks, I would recommend you follow and complete the steps given below:
    1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

    2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

    3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

    4. Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

    5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

    6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

    7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

    8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

    9. Test and Diagnose RAM issues with RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

    10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try
      My Computer
    Quote Quote

  4. tr1x
    Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       New #3

    Alright, uninstalling AVG now. I should know if that fixes it within the next 24 hours. Thanks!
      My Computer
    Quote Quote

  6. tr1x
    Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       New #4

    Just got another BSOD, 12 hours after I uninstalled AVG. This one was like I was describing before, just a flash of blue followed by a system restart. Any other suggestions? Reinstalling AVG now.
      My Computer
    Quote Quote

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

    Have you looked at the 124 thread? what about the rest of the steps?

    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try
      My Computer
    Quote Quote

  8. tr1x
    Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       New #6

    I just took the overclock off my hardware a few hours ago. I would find it hard to believe that OC is the culprit though because it has been OC since I built it, all those years ago, and had no problems until now. I also ran prime95 for a few hours and everything is still stable.

    Other than that, I've reseated my graphics card and updated the drivers (forgot to update them when I reinstalled Windows, but they were up to date on my last Windows installation, which had the sames BSOD's).

    So yes, as of right now, I've completed all the steps on that page. I'll report back if I get another BSOD. Thanks for your help.
      My Computer
    Quote Quote

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

    Okay no problem
      My Computer
    Quote Quote

  11. mariorules
    Posts : 4
    Windows 7 64bit
       New #8

    Just check it out


    Hi guys, i have the same problem but check something :
    Google phrase :" ntoskrnl.exe+75bc0 " and you will see that all threads about this problem are only from this mounth. Strange, isn't it? I think it can be a bug with some of Windows update. Hope you guys will figure it out.
      My Computer
    Quote Quote

  12. realtanu
    Posts : 1
    Windows 7 6
       New #9

    mariorules said:
    Hi guys, i have the same problem but check something :
    Google phrase :" ntoskrnl.exe+75bc0 " and you will see that all threads about this problem are only from this mounth. Strange, isn't it? I think it can be a bug with some of Windows update. Hope you guys will figure it out.
    my computer was running fine for 1YR. Starting mid-October I started receiving my first BSOD (on Internet Explorer). Have had trouble running Kaspersky anti-virus as well. Ended up updating all drivers etc. and shifting my power usage to "maximum performance" (to avoid some odd setting limiting my CPU or something). Got a BSOD yesterday. EventViewer showed the ntoskrnl.exe+75bc0 failure. Started having CHKDSK orphaned segments show up on C: and D:. was able to get Kaspersky antivirus to run two full scans and showed up nothing. Interestingly Kaspersky told me uninstall AVG, but i never had it installed -- and the removal tool failed. I ran memtest86+ last night and it was a MASSIVE FAIL. ordered new Crucial RAM to replace existing RAM. I was surprised RAM failed, but I thought memtest solved the problem. However, if others also only started getting this problem triggered in October as well, this suggests something software related. Whether virus or windows update, I don't know.
      My Computer
    Quote Quote

 

  Related Discussions
BSOD after 7-9 Hours
in BSOD Help and Support

I am consistently getting a BSOD after about 7-9 hours from startup on my Windows 7 Home Premium, 64 bit, ZT brand PC with 16GB memory and 2TB HD. When I reboot it runs fine without problems or symptoms for another 7-9 hours and then I get the BSOD again. EDIT: I am getting this info on my...
BSOD Every 4 hours or so
in BSOD Help and Support

I have actually been getting these BSODs for probably more than 6 months. However usually they only happen every 4-5 days and they would occur overnight so I could live with it. However just recently this past week, the BSODs started getting more and more frequent, usually happening every 4 hours...
BSOD Every 1-2 Hours
in BSOD Help and Support

I seem to be getting blue screens of death every 1 to 2 hours. I thought it might have been because my old HDD was dying, but having just replaced it and the BSOD continue to happen. I've attached my .dmp file.
BSOD every 1.2 hours
in BSOD Help and Support

Windows 7 64 bit Full retail Custom build July 2011 Started happening a 3/6/2012. Checked RAM
6 hours of Prime95 and 2.5 hours of OCCT.
in PC Custom Builds and Overclocking

Is this enough to say my processor is stable? Temperatures stopped increasing loooooooooooong ago. I accidentally messed up the Prime95 test - I was going to run it for a day, but needed access to my computer. Using my computer forced two of the workers to stop due to insufficient swap space/RAM. ...
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:54.
Find Us