Random BSOD ever ~2-3 weeks

Logan Snyder

Honorable
Jul 16, 2013
27
0
10,530
The good news is, they all seem to be related to the same thing. A lot of people seem to say it's drivers, but I don't know exactly what to do about that. I don't know if this is related, but I have an SSD and HDD, and sometimes my HDD just randomly turns on. It seems completely random.

1. "Bug check code: 0000001A
Probably caused by: nt!wcsncat_s Driver"

2. "Bug check code: 0000003B
Probably caused by: nt!KeSynchronizeExecution Driver

The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code."

3. "Bug check code: 0000000A
Probably caused by: nt!KeSynchronizeExecution Driver

The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above."

4. "Bug check code: 0000000A
Probably caused by: nt!KeSynchronizeExecution Driver

The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above."

Any feedback would be greatly appreciated, thanks.
 
basically, nt is the abreviation for the windows kernel. Saying caused by nt is the same as saying caused by windows.
Not very useful. It is just a driver that is trying to use a resource incorrectly and causing a problem. Or you have a hardware problem memory corruption. You might want to start to check for that by running memtest86.exe off a boot cd or thumb drive to confirm your basic system works as expected.
 

Logan Snyder

Honorable
Jul 16, 2013
27
0
10,530
I didn't run the memtest, but since then, I got another BSOD.

"
Bug check code: 00000050
Probably caused by: win32k!EngCreatePalette Driver

The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced."

So I guess it's my RAM.
 
bad guess, the memory error means that the data contained in the RAM is not what was expected.
It can be bad RAM in a small percent of the cases but most often it is a bad driver that wrote data on top of another drivers memory space. (drivers share access to each others memory data in RAM)

you use the memtest86.exe on its own cd to confirm that your BIOS settings for memory and basic hardware work or don't work correctly. (windows is not involved so it can not be a winodows driver)

if memtest86 works as expected then you have to figure out why windows does not. That often takes some time. Do save your self some time and run a virus scan and a malwarebytes scan on your system.
then run a chkdsk /f /r on your drive (repairs corrupted filesystems)
and a system file check
sfc.exe /scannow (repairs corrupted system files)

before you spend too much time trying to figure out your problem.