New
#1
Windows 10- BSOD- CRITICAL_STRUCTURE_CORRUPTION
I am having BSOD every 40 minutes or so on Windows 10. But there seems to be no BSOD when I switch to another microsoft account.
I am having BSOD every 40 minutes or so on Windows 10. But there seems to be no BSOD when I switch to another microsoft account.
সায়ন্তন, your issue looks like to be a driver related issue. May be, this account uses any program/software that is calling it.
18 is the type of corrupted region, that is .....Code:BugCheck 109, {a3a01f5903acea67, b3b72bdf562da510, 1, 18} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner ---------
The description is ....Code:18 : Kernel notification callout modification
But we cannot find any failing driver, even in the deepest search.Code:******************************************************************************* * * * 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.
Let us enable Driver Verifier to monitor the drivers.Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy 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.
WarningBefore 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.
Let us know the results, with the subsequent crash dumps, if any.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.
P.S. Following different suggestions from multiple forums will not be a good idea. If I have been in place of you, I would have choose either place to continue with.
I am going on vacation so I will post the results as soon as I get back. Thank you for your support.
So, I ran the driver verifier and I got BSOD again. Here is the dump file:-
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Disable Driver verifier.
Update the vJoy driver from here: Download
Let us know how it goes.
_____________________________________________________________
That is a continuing issue, we failed to trace it last time.Code:BugCheck C9, {23b, fffff800977b24d0, ffffe00044570510, 0} Probably caused by : vjoy.sys Followup: MachineOwner -------------------------------------------------------------------- Image name: vjoy.sys Timestamp: Tue Mar 19 23:46:09 2013 (5148AB69)
25-02-2016 14:10 Windows Error Reporting Fault bucket , type 0
Event Name: PnPRequestAdditionalSoftware
Response: Not available
Cab Id: 0
Problem signature:
P1: x64
P2: HID\VJoy&Col01
P3: 10.0.0.0
P4: 0409
P5: input.inf
P6: *
P7:
P8:
P9:
P10:
Okay, I updated the vJoy driver and BSOD occurred immediately after the restart. But since then, no BSOD till now. It's been just over an hour since the last BSOD.
No more BSOD. I think it is solved. Thanks a lot.
Okay, thanks again.
Well I uninstalled vJoy because it wasn't working properly with the new driver. But BSOD again after 2 hours. Here's the dump file:-
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.