BSOD 0x109 csrss.exe

[eddie_im3000]

Any ideas pls guys .I just did a new install of win10 cause there are 2 months or so with bs .most of them were while playing f1 2017 but not all of them.
Primary Analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`706a1000 PsLoadedModuleList = 0xfffff802`70a5e2f0
Debug session time: Thu May 31 00:22:54.814 2018 (UTC - 4:00)
System Uptime: 0 days 1:37:31.553
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a025d98e236505, Reserved
Arg2: b3b7325fe0a54eb0, Reserved
Arg3: fffff78000000274, Failure type dependent information
Arg4: 0000000000000000, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

Debugging Details:
------------------


BUGCHECK_STR: 0x109

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80270838680

STACK_TEXT:
ffffe581`57171a88 00000000`00000000 : 00000000`00000109 a3a025d9`8e236505 b3b7325f`e0a54eb0 fffff780`00000274 : nt!KeBugCheckEx


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: BAD_STACK

Followup: MachineOwner
---------

 

[scout_03]

you have win 10 on the system and error report a win 8 driver issue so check this and do a full malwares scan .

 

[eddie_im3000]

i havent install any drivers by my self .its all bu the win update EXCEPT for my logitech momo.malware???i just did a clean windows install and avira works just fine.

 

[scout_03]

avira is a antivirus software not a malware scanner for the driver you should check your board maker for the win you might have some missing even the board chipset driver .

 

[eddie_im3000]

Malwares bytes says its clean.
The blue screens started without me uninstalling or installing any drivers.my last clean win install was about 12 months ago.And till 2 months ago everything was fine.
My pc IS old but I didnt change anything to make it worst.
1090T,M5A78L,gtx1060, 2gb pqi 2gb kingston 4gb patriot

 

[scout_03]

then use whocrashed it will read minidump in plain that will give us more clue .

 

[eddie_im3000]

On Wed 30-May-18 9:22:54 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\053018-29078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197680)
Bugcheck code: 0x109 (0xA3A025D98E236505, 0xB3B7325FE0A54EB0, 0xFFFFF78000000274, 0x0)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 30-May-18 9:22:54 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A025D98E236505, 0xB3B7325FE0A54EB0, 0xFFFFF78000000274, 0x0)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[scout_03]

you have to check your os files and memtest ram also scan with malwarebyes in case .

 

[eddie_im3000]

Os files are healthy.memchech after 4 long passed didnt show anything wrong with ram and i did check with Malwarebytes.everything is clean.

 

[scout_03]

use whocrashed to read minidump in plain text also did you check the f 1 game files .

 

[eddie_im3000]

https://mega.nz/#!QiInhb6K!1yyxpYe-MvGSfVuDG1vusKW_BL9ogxzojRMsVttEEyw


in case you find the time take a look im not getting anywhere

 

[scout_03]

have to create a account so made the link public so we could acces to the files without having to made a account .

 

[eddie_im3000]

I took my time to make sure that what i got is right.
Let me just tell you Thank you so mush for your time !!!
now, i tried different sata cables,psu,tool out ram,didnt connect my momo.when i would stress my pc with a game with high graphics i got the blue screen.not immediately but 5 10 15 mins into the games ,all games.
So i put 2 small coolers on top of my mainboard where are 2 sinkheaters.one over the gpu one under it .the result is that now I dont get blue screen !!!! I am not overclocking !!!!everything in bios is standard.now with momo in f1 I dont get blue screen .

 

[scout_03]

those shinkheater you refer on the motheboard are the north and south bridge cooler so if they overheath this wil made issue on system specialy if you have a overclock same position as picture here http://computerbasicforu.blogspot.com/2011/04/motherboard-north-bridge-and-south.html