Hey /g/ I could really use some assistance. I've been getting random ass blue screens with absolutely no warning, and they all seem to be caused by ntoskrnl.exe. I'm aware that it's the Windows NT Kernel but I don't know what I can do about it.
They also all had different error messages except for the last 3 which all said "CRITICAL_STRUCTURE_CORRUPTION". Any advice?
>>52375798
install gentoo
>>52376331
Saw that one coming a mile away
>>52375798
Seems that NSA_cVck.exe is crashing, so Windows 10 is pretending to blue screen to prevent you from doing anything that govt entities can't monitor.
Hey buddy I'm almost 70% something is wrong with your RAM, Run memtest86 for a couple hours and see what it turns up.
>>52376371
8/10 made me chuckle
>>52376426
I'll give this a shot, much appreciated anon.
>>52375798
ntoskrnl.exe is literally the operating system kernal image for windows.
gotta be a hardware problem if that's crashing bud.
>>52376447
But how would I go about figuring out which hardware is causing the problem? That's my main issue.
it's def a hardware issue try one stick of ram see if BSOD happens, then try running with just the other stick
and btw this board isn't techsupport and most people on here will rip you to shreds for asking questions like this.
>>52375798
The annoying thing about blue screens is that they can be caused by literally anything. Because the NT kernel has no page protection (due to being the kernel, where nanoseconds count), a memory corruption in one driver (due to flaky hardware or whatever) can propagate to another driver or the kernel itself and cause it to crash.
Like >>52376371 says, I'd check your RAM, but if that's fine I'd start unplugging hardware (GPU, USB stuff, etc.) until it starts working again.
>>52376496
Makes a good point, I've had my computer BSOD from my plugging my iPhone into the USB port for whatever reason.
I've also had my computer BSOD from plugging my microphone in a few times.
These both happened on diff machines but weird shit like that can cause BSOD.
>>52376426
>>52376472
>>52376496
OP here, something I should probably mention is that I'm running on a laptop, so that makes messing with the hardware a little more difficult.
>>52376563
wellllllllll memtest86 is your best bet then,
if its a hardware issue (which it most likely is)
your gonna wanna start thinking of a replacement. unless you can find a way to repair the laptop for cheap
>>52375798
Have you made any recent hardware changes? If so, undo them. What about driver updates? Same thing, roll me back.
General troubleshooting goes from least to most involved, and you can create an even hardware/software split to trace.
Does the issue occur in all user profiles or just the one? If it's just the one, what's different about that profile? Keep tracing.
This is pretty basic shit, anon.
Have you tried to read the error messages? Have you googled the error codes? Have you done anything besides nothing and coming here first?
>>52377246
No hardware or drivers have been changed since these bluescreens started happening, and they're the only bluescreens this computer has ever had. Haven't tested other profiles. I have googled and searched the error codes, and I wasn't really able to find anything solid.
>>52377379
Dust that fucking thing inside and out. Reapply thermal toothpaste.
>>52375798
RAM/HDD problem.
>>52377379
Willing to bet you bumped your laptop a few times too many and your ram has become mis-seated; that, or your memory has a hardware fault.
If you have multiple sticks, pull 1 and use the computer for a few days -- it looks like you're having crashes between every 1 and 4 days, so this shouldn't take too long to confirm.
Step 1: reseat memory sticks, wait few days, confirm operational. if not, proceed to step 2.
Step 2: run system with only 1 memory module, wait a few days, confirm operations. If not, proceed to step 3.
Step 3: same as step 2, just opposite stick. If continues, step 4.
Step 4: possibly bad memory slot, repeat test steps 2/3 but alternate the memory/slot from original test.
Step 5: if issue persists, you may need to replace your MB. Go to step 6.
Step 6: buy a mac, because they have soldered memory and don't have these problems.
>>52377246
>>52378119
These are both me, replying again. I'm pretty confident you didn't google the "bug check code" like I suggested you didn't.
Because it's clear you don't know how to google or perform research, I've taken the liberty of doing it for you; that said, I'm also going to take this time to remind you that you're incompetent and shouldn't be allowed around technology made in the past 10 years.
bug check errors:
> 0x00000109
> 0x0000003b
> 0x00000050
> 0x00000019
Links:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557228(v=vs.85).aspx
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/bsod-bug-check-code-0x00000109-issue/8c98e420-39c0-4d57-85ff-f0bff3351f3a?db=5
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/receiving-multiple-blue-screen-errors-0x00000109/7377827d-a24e-41ff-a8ab-c53ad51bc685?db=5
http://superuser.com/questions/949380/suddenly-getting-bsod-memory-management-issue-after-updating-to-windows-10
http://superuser.com/questions/1021027/what-is-causing-this-windows-10-blue-screen-memory-management-ntoskrnl-exe
http://www.sevenforums.com/bsod-help-support/
https://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx
http://answers.microsoft.com/en-us/windows/forum/all/error-systemserviceexception-stop-0x0000003b/f47e4f29-8787-42ac-ac65-d9aeef50cde3
>>52378265
Everything aside, I really do appreciate the help anon, I'll try out all your suggestions.
>>52378345
you're welcome.
but really, see step 6.
>>52378504
Will take into consideration
