Blue screen of death

[bunchy]

I have been having BSOD errors for the last 3 months or so . first problem was memory mangment after upgrading my ram, I ended up runining memtest and replacing the bad stick, while I was waiting for a new stick I ran only 4gig ram and my pc had no bsod for 2 full weeks. after getting the new ram my pc worked fine for 2 days then new BSOD this time with page fault in nonpaged area errors. it happned while trying to install Utorrent. I didnt think much of it at that time, but it kept hapning each 2/3 days. I contacted microsoft support and they susspected ANOTHER RAM issue. I ran memtest and no errors were found. then I started using BlueScreenView as well as whocrashed. and by googling the causes that BSV showed I susspected that my hard drive was going bad. so I ran Seatools for windows and it failed the first short test but then passed everysingle test I did which made it even more diffcult to understand if the hard drive was 100% the problem. I then contacted Seagate support and they informed me that my hard drive was going bad. and asked me to preform Seatools for DOS which also passed without errors. heard back from support and thay said this : As the issue still persists even after the drive passed the SeaTools tests, we conclude that the issue might be due to any mechanical failure..

"Might" is the main thing thats stopping me from going on and buying a new harddrive. . also I ran Gsmartcontrol and right before the short test was done I had bsod . however after retrying the test for 20 times it passed without anyproblems! I am really running out of ideas and this is my last resort. iam attatching the .rar file with 15 dumps
http://www.mediafire.com/file/7i9whjd4q2jw8kg/New%20folder%20%283%29.zip

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/86A7.html

Spoiler

File: 050118-15506-01.dmp (May 1 2018 - 19:58:40)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: taskeng.exe)
Uptime: 0 Day(s), 0 Hour(s), 13 Min(s), and 21 Sec(s)

File: 043018-19936-01.dmp (Apr 30 2018 - 17:34:16)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 16 Min(s), and 27 Sec(s)

File: 042918-26800-01.dmp (Apr 29 2018 - 22:16:02)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: opera.exe)
Uptime: 0 Day(s), 0 Hour(s), 15 Min(s), and 28 Sec(s)

File: 042918-17706-01.dmp (Apr 28 2018 - 03:20:45)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: opera.exe)
Uptime: 0 Day(s), 1 Hour(s), 40 Min(s), and 56 Sec(s)

File: 042518-17862-01.dmp (Apr 25 2018 - 14:53:09)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 21 Min(s), and 57 Sec(s)

File: 032118-16458-01.dmp (Mar 21 2018 - 17:52:34)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 1 Hour(s), 48 Min(s), and 19 Sec(s)

File: 031818-17004-01.dmp (Mar 18 2018 - 20:20:01)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: chrome.exe)
Uptime: 0 Day(s), 2 Hour(s), 57 Min(s), and 44 Sec(s)

File: 031718-25225-01.dmp (Mar 18 2018 - 00:40:17)
BugCheck: [SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (C1)]
Probably caused by: dxgmms1.sys (Process: csrss.exe)
Uptime: 0 Day(s), 0 Hour(s), 35 Min(s), and 38 Sec(s)

File: 031718-19812-01.dmp (Mar 18 2018 - 03:41:28)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: DSAService.exe)
Uptime: 0 Day(s), 0 Hour(s), 14 Min(s), and 03 Sec(s)

File: 031718-18673-01.dmp (Mar 18 2018 - 00:03:18)
BugCheck: [SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (C1)]
Probably caused by: memory_corruption (Process: NVIDIA Web Hel)
Uptime: 0 Day(s), 1 Hour(s), 21 Min(s), and 28 Sec(s)

File: 030718-22261-01.dmp (Mar 7 2018 - 20:09:35)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 30 Min(s), and 45 Sec(s)

File: 030518-19250-01.dmp (Mar 5 2018 - 18:13:54)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: ntkrnlmp.exe (Process: services.exe)
Uptime: 0 Day(s), 1 Hour(s), 11 Min(s), and 59 Sec(s)

File: 030218-20436-01.dmp (Mar 2 2018 - 04:49:05)
BugCheck: [CRITICAL_OBJECT_TERMINATION (F4)]
Probably caused by: 8c84f46a4ba5bd (Process: 8c84f46a4ba5bd)
Uptime: 0 Day(s), 2 Hour(s), 16 Min(s), and 22 Sec(s)

File: 021018-16411-01.dmp (Feb 10 2018 - 16:45:00)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: chrome.exe)
Uptime: 0 Day(s), 1 Hour(s), 17 Min(s), and 50 Sec(s)

File: 020718-15646-01.dmp (Feb 8 2018 - 00:08:48)
BugCheck: [NTFS_FILE_SYSTEM (24)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 00 Min(s), and 25 Sec(s)

Motherboard: Dell 0GDG8Y
BIOS Info: Ver: A10 - Date: 02/22/2013

While you wait for additional answers, see if you can find an update for your Ralink Wireless Adapter driver, and see if there are any BIOS updates. Note: Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Wait for additional replies. Good luck.

 

[bunchy]

I did try to update Ralink Wireless Adapter driver, for like 20 times. But it wont work regardless of it being via windows or manually
And there is no bios update since the last one was 2013 (it is a pretty old pc)

 

[Colif]

8c84f46a4ba5bd is random, actual thing that crashed here was csrss.exe which is your user client on windows.

Is this win 7 or 10? the OS is saying its win 7 SP1?

I could understand why the Railink drivers might not work with win 10 as they likely just rebadged win 8 drivers, but they should work with 7

https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices/having-trouble-with-ralink-wifi-adapter-after-the/d8923d60-f32b-4655-90f8-59885c0c6b61?auth=1

many of crashes seem web related so its a good place to start with the Railink driver.
I assume you have A Asus GPU given ASio.sys is on PC and is out of place on a Dell. Its part of GPU Tweak 2

 

[Colif]

might also be fact the 2 sticks speeds don't match

4096MB 1600MHz
4096MB 1333MHz

I expect if they in the same channel it would help if they both same speeds. See if removing stick stops the errors since they only appeared after you put 2nd stick in. run memtest again and maybe even check the 2nd slot out with a stick you know works, just to make sure its not the slot itself.