BSOD error A, 3b, 19, 10e frequently.

Hi Sukichan.

I have checked most of your BSODs, but not all of these. Diffesret bugcheck codes, but all of them are indicating to display malfunction somehow, specially the stop 0x19 BSODs.

Code:

fffff880`0b339288 fffff800`02c644ce nt!KeBugCheckEx
fffff880`0b339290 fffff800`02e0454a nt! ?? ::FNODOBFM::`string'+0x72e6
fffff880`0b339320 fffff800`02cade10 nt!ExFreePoolWithTag+0x46a
fffff880`0b3393d0 fffff960`001ec618 nt!ExDeleteResourceLite+0x190
fffff880`0b339430 fffff960`0022f551 win32k!GreDeleteSemaphore+0x24
fffff880`0b339460 fffff960`0022f8e3 win32k!PDEVOBJ::vDisableSurface+0x151
fffff880`0b3394b0 fffff960`001297a8 win32k!vUnreferencePdevWorker+0x2db
fffff880`0b339550 fffff960`0022878e win32k!PDEVOBJ::vUnreferencePdev+0xd0
fffff880`0b339590 fffff960`0022ab5c win32k!DrvDestroyMDEV+0xb2
fffff880`0b3395d0 fffff960`0006b83d win32k!DrvInternalChangeDisplaySettings+0x179c
fffff880`0b339810 fffff960`00155255 win32k!DrvChangeDisplaySettings+0x13a1
fffff880`0b3399f0 fffff960`001554b2 win32k!xxxInternalUserChangeDisplaySettings+0x329
fffff880`0b339ab0 fffff960`00142b78 win32k!xxxUserChangeDisplaySettings+0x92
fffff880`0b339ba0 fffff800`02ccfe53 win32k!NtUserChangeDisplaySettings+0x98
fffff880`0b339be0 00000000`752e265a nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2e8 00000000`00000000 0x752e265a

Before doing anything further, we need to see the situation with a known stable version of display driver installed.

Install the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Also, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Let us know the results. We will decide about our further steps depending on these information.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest results no errors, enable Driver Verifier to monitor the drivers.
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.

One red line is enough to consider the RAM as failing, and filing RAM can cause any issue.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.
It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.
It is a motherboard issue. The particular slot is bad.

If the computer BSODs when both the RAM slots are occupied, I would suggest you to run with only one RAM stick, in any of the slots, on a test basis, for a few days.

Sukichan said:

Have had all working RAM in each RAMslot and the computer works fine as long as there's only one RAM active. Straight after I once again used both working RAM, stressed my computer and managed to BSOD 0xA within 5 minutes. New zip-file added.

In this situation, it is the fault with your motherboard that it cannot handle both the RAM slots occupied.