BSOD mostly while gaming (has been in to Asus twice for repair)

Can you do what Asus techs have been so far unable to do?

I have been suffering from sporadic BSOD mostly while gaming for some time. My computer has a terrible gpu so I thought that was the cause and it was getting up to some very high temperatures, but I sent the computer in to Asus and they replaced the fan and some cooling parts and the computer doesnt run hot any more but then I started to get Bad Pool Caller and page fault BSODs. I sent it in again and they replaced the hard drive. I have had it back for less than a week and the BSODs are back. Help me SevenForums you are my only hope.

system specs

Brand: Asus
Model: U30JC-X2C
Screen: 13.3" HD (1366 x768) (LED)
Processor: Intel i5-430M (2.26GHz)
Chipset: Intel HM55
RAM: 4GB DDR3 1066 DRAM; 2 x SODIMM socket
Hard Disk: 320GB 5400RPM
Video Card: NV G310M 512MB DDR3 VRAM
Network: 10/100/1000 802.11 BGN
Operating System: Windows 7 Home Premium

Let me know if there is any other information required.

Security Software: ???

Make sure to install security software. I recommend either of these:

• Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.
  
  
• Good and Free system security combination.

After installing your security software, update it, and then run full scans today with each program. Report back the results of the scans.


One of your crashes indicates 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 the short and long tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• 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, uninstall it in device manager and see if the system performs better.
  
  
  
• 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.

The other crash points to your graphics card drivers. This could indicate a possible problem with your graphics card drivers or DirectX. DirectX comes installed with Windows, so this may mean you have Windows corruption. It may also mean that you have corrupted drivers or a graphics card hardware problem.

• If you are overclocking any hardware, please stop.
  
  
• 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.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the drivers you want for your display card(s)
2. Click Start Menu
3. Click Control Panel
4. Click Uninstall a program
5. For NVIDIA:
   • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
   • Restart your computer
   • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
   • If any remain of the above, uninstall one at a time
   • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
6. Restart your computer after uninstalling drivers for all display cards
7. Install the driver you selected for the display cards once Windows starts

Remember to try multiple versions of the graphics drivers, download them fresh, and install the freshly downloaded drivers.


I also wonder if this might be related to your old Webcam. The drivers are pre-Windows 7, and if it is running during these crashes, it may be worth investigating whether removing it provides more stability.

Hey, sorry for taking so long to get back it took me a while to run all the tests you recommended. All the tests were clean , should I send it back to Asus?

No worries on taking time to get back. Please provide any new crash reports to determine the best steps going forward.

https://www.sevenforums.com/crashes-d...tructions.html

this one was a bad pool header. Could being too aggressive with revo uninstaller cause these problems?

here is what windows 7 had to say about it. standard dump files are attached


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 19
BCP1: 0000000000000020
BCP2: FFFFFA800460C700
BCP3: FFFFFA800460D290
BCP4: 000000000CB92980
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\061812-22058-01.dmp
C:\Users\Clayton Catching\AppData\Local\Temp\WER-45037-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Crash still points to memory. It may be a driver conflict causing the memory_corruption, though.

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any 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. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 217021
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  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.
  
  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.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.

I really appreciate your help, It seemed to indicate that the driver for my memory stick reader was to blame so I reinstalled it. I have attached the crash logs.

Alright, use my previous post for instructions to disable Verifier and disable it to see if the system is now stable.