RANDOM BSODs with different codes

[vekexasia]

I'm sorry i wasn't much specific in the title but i really don't have any other option to write here and hope for some kindness from you guys.

History of the problem.
It’s been more than a year that I continue experiencing random BSOD’s. In first place I decided to ignore them but with time they became more frequent and, of course, annoying.

So i started searching for a solution but I noticed that they were really random ( infact bugcheckcode changes ).

While searching I found some guys who suggested to replace some piece of hardware so in total I changed:

• 1x PSU
• 3x Video cards
• 1x RAM memory
• 2x Primary Hard Drives
• 1x Motherboard
• Almost every cable in the motherboard

I spent a lot of money trying to isolate this problem that i think I could have bought another pc with less money.

With the last change ( Video card - from ATI to NVIDIA 560 ) I also tried to re-install windows 7 x64 ultimate hoping that, finally, I solved the issue.

Unfortunately, since I’m asking for your help, I’m still experiencing bsods.

In these months I didn’t find any valuable pattern for them. It could happen i stay bsod-free for 1 or 2 days and the 3rd day I get 4+ bsods in a row. As I said, they seem to be completely random to me.

I also left my pc for 3 days doing Memtest on the current ram and the result was successful.

I followed the “How to post a bsod form” but I didn’t manage to use the “BSOD Dump & System File Collection app” which doesn’t create any folder for me.

As attachment you’ll be able to find the zip containing the last 3 minidumps and the “perfmon /report” output.

 

[zigzag3143]

These crashes were caused by memory corruption possibly caused by your AVG.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[vekexasia]

Hello,

As you probably saw I already changed my RAM and tested it with memtest. I also changed the motherboard recently.

EDIT:

I just had a crash. with driver verifier procedure. Should I try to replicate now?
PS: you'll find the compressed minidump as attachment

 

[zigzag3143]

Hello,

As you probably saw I already changed my RAM and tested it with memtest. I also changed the motherboard recently.

EDIT:

I just had a crash. with driver verifier procedure. Should I try to replicate now?
PS: you'll find the compressed minidump as attachment

This one related to memory corruption but not driver verified. Please double check your settings.

 

[vekexasia]

Hi, thank for your kind reply.

What do you mean with "Check your settings" ?

Edit: I updated the "My System Specs" stuff ( bottom left of my posts ). Hopefully that would give you more infos.

 

[zigzag3143]

Hi, thank for your kind reply.

What do you mean with "Check your settings" ?

Edit: I updated the "My System Specs" stuff ( bottom left of my posts ). Hopefully that would give you more infos.

First can we assume you arent overclocking?



By check your settings I meant to double check the driver verifier settings after enabling it to ensure it is running. You can do that by typing verifier /query it will give you a list of the drivers being verified.

It should not say no drivers are being verified. You can actually check verify all drivers but it may slow you down a bit.

 

[vekexasia]

Hi, thank you again.

verifier /query was returning too fast so I launched verifier and choose the last option .

As attachment you'll be able to see the result.

Since the last bsod i'm still running ( I think ) the verifier. But I did not receive any other bsods.

I'm not overclocking anything. I want my system to be "stable".

What do you think? Would you propose to run memtest again? Or there are other options that could be checked?

I don't know if you read the list of hardware I replaced to try to patch the issue... The only hardware that I didn't change so far is:

• The case
• The CPU

Would it be possible that one of them is causing the issue?

 

[zigzag3143]

Hi, thank you again.

verifier /query was returning too fast so I launched verifier and choose the last option .

As attachment you'll be able to see the result.

Since the last bsod i'm still running ( I think ) the verifier. But I did not receive any other bsods.

I'm not overclocking anything. I want my system to be "stable".

What do you think? Would you propose to run memtest again? Or there are other options that could be checked?

I don't know if you read the list of hardware I replaced to try to patch the issue... The only hardware that I didn't change so far is:

• The case
• The CPU

Would it be possible that one of them is causing the issue?

It is highly unlikely that the case would be the issue and to have 2 psu's be the problem are just as unlikely

More likely is software. You may be installing the very thing that makes it crash. Since all BSOD's are a combination of things it could be your malware app, video driver, etc.

If you re-installed and nothing that wasnt on the win 7 Install disk then I would start thinking hardware.

 

[vekexasia]

Still bsods

Hello, i need to reopen this topic because i just experienced 3 bsods in the last 2 hours.

It was 4 or 5 days that I wasn't experiencing any bsod so I thought it was somehow solved. Suddenly, after a system reboot today, I started getting bsods again.

In order to let you see how strange it is this behaviour i'll attach:

• The event viewer snapshot
• the minidump zip file containin the 3 minidumps of today.

 

[writhziden]

Do you have a 3rd party remote control program (i.e. Teamviewer, LogMeIn, etc.)? If so, remove it. If not proceed to the next step.

Your crashes indicate a corrupted Windows file. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems. It could also be a third party remote control program.

• 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 http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  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.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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 http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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 http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 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. :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.

To get more specific help, please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with your crashes and event viewer logs.