BSOD occurring constantly and randomly!

[wrdmrn]

New dongle bought and installed. There is no apple device plugged into the PC, occasionally my Ipad but i always disconnect the cable and take it with me as it's also my charger!

Files are backed up, so will attempt the driver verifer now.

 

[wrdmrn]

I think that I have it enabled now, no way that I can really tell though?? I followed the settings tutorial on the previous page, it asked me to restart, I clicked yes and it didn't do anything. I restarted manually but still don't know what the craic is

I read another thread and done the cmd prompt - verifier /query ..... it returned some results but I don't know if it is running or not!

 

[Arc]

As you are using a new dongle, dont need verifier right now. Disable verifier. Run the computer normally. Hopefully there will be no more BSODs. Even if there is any, that will be troubleshooted accordingly.

You please let us know after a reasonable time that how the PC is working with the new dongle, unless there is any more BSOD in the mean time.

 

[wrdmrn]

Perfect, I have just been using the computer for 3 hours without any issues, even edited a whole shoot

I'm going to walk away now and switch the screen off and see what's what in the morning!

 

[wrdmrn]

So over the last few weeks with the new dongle there was a massive reduction of blue screens, 1 in a 2 week period until 3 days ago, i've had 13 in that space of time!

Here is the latest files attached. I've also posted a screen print of the errors over the last few days with blue screen view too

 

[Arc]

The latest version of nvidia display driver causes some issues lately. Can you try to roll it back?
Device Manager - Roll Back Driver

Also, there are four BSODs in a single day, with three different bugchecks, which is a bit odd. Let us first apply the Driver Verifier.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[wrdmrn]

Rolled the driver back for graphics and ran verifier, had no sign of any blue screens for 3 days. Then today, 2 in the space of 5 mins, I couldn't get the logs for the first but here is the 2nd

 

[Arc]

Your total memory is 11.0 GB. I have suggested you even earlier to test using one set of RAM. Asking for it again. Remove the extra RAM. Run the computer with the original RAM and observe if it causes BSODs or not.

Update realtek network driver. It's very old.

fffff880`0f400000 fffff880`0f457000   Rt64win7   (deferred)             
    Image path: Rt64win7.sys
[COLOR=Red]    Image name: Rt64win7.sys
    Timestamp:        Thu Mar 04 19:12:52 2010 [/COLOR](4B8FB8DC)
    CheckSum:         000611C5
    ImageSize:        00057000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek take the Win7 and WinServer 2008 R2 Auto Installation Program (SID:1581786), dated 2013/5/22.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

___________________________________________________________________________________
BSOD ANALYSIS:

BugCheck A, {0, e, 1, fffff800030fa9f5}

Probably caused by : memory_corruption

Followup: memory_corruption
-------------------------------------------------------------------------------------------
BugCheck 3B, {c000001d, fffff800033e7ca3, fffff8800a5fd030, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

 

[wrdmrn]

Sorry been away on holiday, since i got back opened up the machine and removed all the ram, results interesting inserting 1 stick and rebooting and everyone has given a bsod error caused by ntoskrnl.exe

Each stick tets fine with both windows memory test and memtest86

This leads me to believe that there is actually no way to fix computers with bsod errors.

I'm thinking of trying a windows reset, or failing that throwing it in the bin as I can't use it anyways its effectively just scrap metal

 

[NoelDP]

At least one of the sticks of RAM must be faulty - 11GB is an impossible configuration, so far as I know.
What does each stick show as being when installed individually?

 

[Arc]

At least one of the sticks of RAM must be faulty - 11GB is an impossible configuration, so far as I know.
What does each stick show as being when installed individually?

Noel I tried to make him understand over a long long time, but I failed always.

 

[bobafetthotmail]

Wait! Did you follow this tutorial when testing RAM? Each stick must pass at least 7-8 times before it can be declared ok.

Then you need to check the RAM slots on the motherboard, placing a single RAM stick you know that works into a slot with the others empty and running the test again.

Another thing to check is the temps. I had quite a few PCs that reported hardware errors simply because they were running hot. Try running without a case panel and use CPUID HWMonitor to check the temperature

If you are still bent on trashing it, sell it as used, with that hardware is worth at least 150 $, or give it for free to a charity that accepts PCs, they will have techs that will scavenge everything useful before trashing it.