Solved Frequent BSOD while browsing web, specific error varies

[AlphaWhelp]

edit: problem not fixed, scroll to bottom for update

Is Windows 7 Pro x64
This is the original OS
I obtained this copy of Windows 7 through my college
System is brand new, only a few weeks old
The OS installation is as old as the system, although I have reformatted/reinstalled Windows the computer once after an SSD Caching mishap

Specs
Mobo: Asus P8Z77 Deluxe
i7-3770k
GPU: EVGA GTX 680 (not superclocked)
16 gigs of 1333 mhz RAM
Vertex 128 Gig SSD and WD Caviar Black 2TB HDD configured in RAID using Asus' SSD Caching.

I've gotten a few BSOD randomly while browsing the web, and once when I wasn't doing anything at all (went to sleep with computer on, woke up, system had restarted from BSOD)

Also got one BSOD while playing Diablo 3, played through all of Act 1 normally, got BSOD act 2, restarted played for a few more minutes, but haven't gone back to it.

one BSOD error was "page_fault_in_nonpaged_area" or something like that, and another BSOD error was "memory_management"

I don't remember what the other errors were.

the warning signs, I've noticed, are when Firefox begins crashing repeatedly, and in Chrome, I get "Oops, something went wrong trying to display this page" messages a few minutes/seconds before a BSOD.

 

[writhziden]

You have a very old driver from 2005 for your Samsung printer. I would recommend updating if possible. If not, try uninstalling the software and driver and see if Windows 7 will install a generic driver. If you need help with steps to do so, let us know.


Crashes are pointing to memory problems or driver conflicts.

• If you are overclocking any hardware, please stop.
  
  
• 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. :warn: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.
  
  
• 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
    View attachment 214611
  • 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 http://www.sevenforums.com/tutorials/700-system-restore.html 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.​
  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.

 

[robotriot]

Hello,
I'm getting the exact same crashes and symptoms as you have (I posted about it here: http://www.sevenforums.com/crashes-...us-bsods-during-file-copying.html#post1948123) including random Firefox/Thunderbird crashes and other weird Windows behavior.

Since we both have the same CPU, motherboard and GFX card (well, I've got an ASUS, but that shouldn't really matter) I'm guessing that the problem is one of those components. Also, all of these are pretty new, is there anything known about manufacturing problems? Did you find out anything new with your problem?

 

[AlphaWhelp]

Actually, allow me to throw in a little update as to my problem.

I ran the suggested Memtest86+ and it threw me an error almost immediately which I recorded on some paper:
Test: 5, Pass: 1, Failing Address: 001a5b409a0 - 6747.2MB, Good: 00000040, Bad: 00000000, Errbits: 00000040, Count: 1, Chan: (blank)

So, I shut down the computer, pulled out all the RAM, and began testing the sticks one at a time for 7-8 passes each, all tested no errors, so then I began testing the motherboard slots one at a time, using the same stick on all motherboard slots, all motherboard slots tested no errors for 7-10 passes. Then I put all four sticks back in and tested one more time again for 7 passes and no errors.

So, I have a bit of a question. Is it possible that my RAM was not inserted properly? I thought that if RAM was not inserted properly, the computer would simply fail to boot, but maybe I hit some kind of weird in between position where the computer would boot but would crash frequently? I have been trying to make my PC crash again by vigorous internet browsing but nothing seems to be happening.

 

[James7679]

Actually, allow me to throw in a little update as to my problem.

I ran the suggested Memtest86+ and it threw me an error almost immediately which I recorded on some paper:
Test: 5, Pass: 1, Failing Address: 001a5b409a0 - 6747.2MB, Good: 00000040, Bad: 00000000, Errbits: 00000040, Count: 1, Chan: (blank)

So, I shut down the computer, pulled out all the RAM, and began testing the sticks one at a time for 7-8 passes each, all tested no errors, so then I began testing the motherboard slots one at a time, using the same stick on all motherboard slots, all motherboard slots tested no errors for 7-10 passes. Then I put all four sticks back in and tested one more time again for 7 passes and no errors.

So, I have a bit of a question. Is it possible that my RAM was not inserted properly? I thought that if RAM was not inserted properly, the computer would simply fail to boot, but maybe I hit some kind of weird in between position where the computer would boot but would crash frequently? I have been trying to make my PC crash again by vigorous internet browsing but nothing seems to be happening.

It is possible that the RAM was not inserted properly. But, generally, any errors Memtest86 shows, signifies bad memory. It is possible for the slots to be bad as well, but not as common. Memtest86 can run for days and not flag, then, POOF, an error. Did you happen to mark the stick as bad?

Keep running it, stressing it, doing your normal routines. If nothing comes back up, then it might just be that you didn't have the RAM locked in tight. Keep your fingers crossed, that's the best case scenario.

 

[AlphaWhelp]

It is possible that the RAM was not inserted properly. But, generally, any errors Memtest86 shows, signifies bad memory. It is possible for the slots to be bad as well, but not as common. Memtest86 can run for days and not flag, then, POOF, an error. Did you happen to mark the stick as bad?

Keep running it, stressing it, doing your normal routines. If nothing comes back up, then it might just be that you didn't have the RAM locked in tight. Keep your fingers crossed, that's the best case scenario.

Well I couldn't mark the "bad stick" because when Memtest86+ threw an error, it was while I was testing all 4 sticks at the same time. All sticks tested good when I tested them individually, as well as the motherboard slots. However, so far, while using all 4 sticks at the same time, everything is good, so I am not sure what to think. I am still worried that I may actually have bad ram, but so far, I've been unable to reproduce a BSOD. So that's why I think the problem may have been improperly inserted RAM.

 

[James7679]

Well, if you are currently stable, it is possible.
Did you perform the other steps writhziden had previously laid out for you?

 

[AlphaWhelp]

Well, if you are currently stable, it is possible.
Did you perform the other steps writhziden had previously laid out for you?

Well, no. I am currently going under the assumption that the problem was that the RAM was loose in the socket, and the problem is thus, fixed, but if I do get another BSOD, I will proceed with the driver verifier steps. So far, the system has been pretty solid. No browser crashes, either, which is something that usually happened right before a BSOD.

 

[James7679]

Sounds good. Let us know how things progress.

 

[AlphaWhelp]

Ok, so, everything was fine for a while then crashes started coming back, so I turned on driver verifier and I am getting crashes now very quickly. How do I collect the data gathered by the verifier program? Do I just run the stuff in the BSOD posting instructions again, or does verifier dump its own data somewhere else?

 

[AlphaWhelp]

I am not sure if this is what I needed to do, but I've uploaded more crash reports this time with Driver Verifier running.

 

[James7679]

Still points to memory. Please upload screens for the tabs on CPUz.

 

[writhziden]

To supplement what James is asking for so that we can get all relevant information possible:

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.
  
  Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)
  
  Thanks to Dave76 for help learning RAM Stability

 

[scanboostar]

I have exact the same problems and I did not find the cause yet. It started one week after the system was installed with the original BIOS.

I get random BSOD's

After I upgraded the BIOS the problem was gone fore some period of time (several weeks) but it came back. My BIOS is now at 1709 but the problem returned. If I flash the BIOS with the same firmware version, the system is stable for a number of days and then the problems come back. I use all the default BIOS settings. If I don't reflash the system the problem occurs several times within one hour just doing regular stuff without overloading the system.

I upgraded all the ASUS drivers, I changed the lithium battery but witout any improvement.

I get the idea that the BIOS memory gets corrupted . . . . .