BSOD randomly, often while playing Witcher 2 or Skyrim

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 Home Premium 64bit
       #1

    BSOD randomly, often while playing Witcher 2 or Skyrim


    Hi! I got a new tower a few days ago, had no issue with it for a few days, then spontaneously I started getting BSOD. It started while playing Skyrim, but now they can happen as frequently as five minutes of use or several hours of use.

    WhoCrashed only recorded one, even though i've had multiple.


    On Wed 7/4/2012 2:44:53 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: Unknown ()
    Bugcheck code: 0xC1 (0xFFFFF9805B698F50, 0xFFFFF9805B698886, 0x940B0, 0x32)
    Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
    Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
    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: Unknown .
    Google query: Unknown SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

    Attached is my msinfo and minidump logs. Any help is appreciated. Thank you!
      My Computer


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

    We would prefer that you follow the https://www.sevenforums.com/crashes-d...tructions.html to help us help you.
      My Computer


  3. Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Sorry about that, here are the files as requested.

    Specs:
    OS: Windows 7 Home Premium 64bit
    CPU: AMD Phenom II six core
    RAM: 8gb DDR3
    Graphics card: ATI Radeon HD 6700
    1 TB HD
      My Computer


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

    Device Concerns:
    Code:
    Ethernet Controller	PCI\VEN_10EC&DEV_8136&SUBSYS_2AB1103C&REV_05\4&C011167&0&0050	The drivers for this device are not installed.
    Please install the drivers for the device above. You can find the drivers on the HP support site: HP Support & Drivers | United States


    Analysis:
    Why did you enable Verifier? Please disable it; it can cause false positives if not setup properly or even if there is nothing wrong with your drivers.
    Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
    verifier /reset
    -> Restart your computer.

    The only driver I am concerned about and would recommend updating is netr28x.sys which is your Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer). You should also be able to find it on the HP support site: HP Support & Drivers | United States
      My Computer


  5. Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    Thank you for your help. I replaced the drivers you mentioned. I was originally running driververifier in hopes I could figure out the problem.. but my buddy never told me to reset so that's my own fault. When I went to reboot after fixing the drivers I had a few problems with windows actually starting. Once I got the computer to actually start windows it seems fine. Hoping it was a hiccup, but i'll keep you posted. Thanks again.

    EDIT: Got another BSOD. Problem seems to stem from the wireless driver I installed. Once I rolled back the driver my booting problems disappeared. I double checked to make sure it was the proper driver, and it was. Any ideas? Thanks.
    Last edited by lcenci; 04 Jul 2012 at 15:20. Reason: Update
      My Computer


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

    Analysis:
    Your latest crashes primarily indicate hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.
    • If you are overclocking any hardware, please stop.

    • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
      For any drives that do not give the message:
      Windows has checked the file system and found no problems
      run disk check again as above. In other words, if it says:
      Windows has made corrections to the file system
      after running the disk check, run the disk check again.

    • Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
    • If you have an SSD, make sure the following are up to date:
      • SSD firmware
      • BIOS Version
      • Chipset Drivers
      • Hard disk controller drivers/SATA drivers
      • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.


    • Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.

    • Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.

    • 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 (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
         Warning
      Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

      For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
      1. Shut down and turn off your computer.
      2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
      3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
      4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

      Once these steps have been followed, it is safe to remove and replace components within your computer.


    Wireless Driver:
      My Computer


  7. Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    I ran Check Disk, everything turned out okay. SeaTools checked out clear. Windows Memory Diagnostic found a hardware error, but would not specify what and told me to contact HP directly. I had a friend bring over 4 gigs of DDR3 RAM to test with the system and still had the same problems (BSOD while playing The Witcher 2 and Skyrim). While he was looking at the computer we realized that for some reason programs like Everest and PerformanceTest are recognizing the video card as an ATI Radeon 5700 even though device manager recognizes the device as the ATI Radeon HD 6700 series that it truly is. Drivers reflect this as well. Attempted to delete and reinstall the drivers, but have the same problem. Removed the graphics card entirely and let the system run with onboard graphics, then reattempted installing the graphics card with the same issue. My only thought is to attempt a complete reformat, but I wanted your opinion first if there is something else I am missing. Thank you for the help!
      My Computer


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

    Everything does check out and looks good. A format and re-install is not a bad option, and a clean re-install is always a good troubleshooting step. I do a clean re-install a few times a year to keep my system running well and make sure clutter does not accumulate in my data drive.

    Clean Reinstall - Factory OEM Windows 7
      My Computer


  9. Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    Had another friend take a look and we found while stress testing the CPU that it was actually causing the crashes. Apparently the new power supply that was put into the tower is raising the Core V to almost double the standard. Thanks to this being a frankenstein HP, I can't just change it in bios. I'm going to swap my 600w PSU with a 460w this afternoon and see if that fares better. Otherwise even a reformat won't repair this and i'll be looking at a new motherboard. Thanks for everything.
      My Computer


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

    Agreed; if it is hardware related, all the clean re-installs in your lifetime would not resolve it.

    Let us know how things go with a different power supply. Also, make sure all the power plugs are properly plugged in and in the right places. It is not that I believe you made a mistake doing so the first time, but I have made that mistake myself twice before, so it is worth checking.


    I really wish OEM BIOS was easier to access voltage and thermal changes... Unfortunately, they keep us out to prevent less experienced users from frying components.
      My Computer


 
Page 1 of 2 12 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 23:43.
Find Us