New system build - BSOD points to ntsokrnl.exe

Nick N

Honorable
Aug 10, 2013
18
0
10,510
I've recently built out a new system and I am getting intermittent BSOD. Using Bluescreenview all the minidumps point to the ntsokrnl.exe driver.

I have reinstalled Windows several times. I have run memtest86+ overnight (17 passes) without issue. I have also run FurMark 1.11.0 and stress tested the GPU. It completed successfully as well. The temps on the APU and GPU seem fine.

Drivers are up to date.

System specs:

OS - Windows 7 Pro 64 bit
Motherboard - MSI FM2-A75MA-E35
CPU - AMD A8-6600k APU 3.9GHZ
[strike]RAM - 2x4GB Patriot PC3-10600 1333MHz[/strike]
RAM - 2x4GB Kingston XMP Hyper X DDR3 1600MHz
Power Supply - ThermalLake TR 600w
Video Card - ASUS GeForce GTX 650 Ti
Network - Netgear N900 Wireless Dual Band VSB
DVD - HL-8T-ST DVDRAM SATA CDROM
HDD - 1 TB Toshiba DTOIACA SATA Disk

Any help would be greatly appreciated.

Thanks
 
Solution
SYSYEM_SERVICE_EXCEPTION is most often thrown due to bad RAM. That being said, you did run with a single stick and the errors remained, and the fact you BSOD's during windows install narrows your focus down to the motherboard, HDD, or RAM.

I'm leaning toward the possibility that one of the RAM slots on the motherboard might be bad. Only thing I can think of is to use a single (different) stick of RAM in a different slot. If two different sticks of RAM give BSOD's in different RAM slots, then I'd RMA the motherboard.

Nick N

Honorable
Aug 10, 2013
18
0
10,510
Ok, I will do that. Unfortunately the system just crashed so badly that I think I am going to need to reinstall again. May be a while before I get to that point.
 

Nick N

Honorable
Aug 10, 2013
18
0
10,510
Well I took one DIMM out and then tried to re-install windows. I got several BSOD with this error:

system_service_exception
STOP: 0x0000003B

I got these when I booted off the Windows CD and was just trying to re-install Windows7. I double checked and re-seated the single DIMM just to be sure and still got a failure.

I am running memtest86+ now. Its beenrunning 30 minutes and completed 1 pass without any errors. I'll let it run the rest of the night and see what happens. I may pull out the graphics card next.
 

Nick N

Honorable
Aug 10, 2013
18
0
10,510
Its was set to AHCI. I changed it to IDE. But the system crashed 4 straight times at the starting Windows prompt. It didn't leave a minidump. I put it back to AHCI and it came up fine.

I took out the first stick of memory and put the other stick in same slot. System came up fine. I have now reinstalled Windows. I have to go to work now. Thanks for looking at my thread, I'll be back on later today.
 

Nick N

Honorable
Aug 10, 2013
18
0
10,510
I had 2 BSOD today, which sadly is actually a good number. One when I tried to install 99 windows updates. It happened on reboot.

The second happened during the day while my son was playing MineCraft. Both dumps look similar in Blue Screen View. How can I attach the minidumps for viewing?
 

Nick N

Honorable
Aug 10, 2013
18
0
10,510
I have checked the BIOS with the Live Update tool and it says it is up to date. I belive my install is very clean. I have the latest drivers for everything and I have run sfc /verifyonly several times and it have completed successfully without error.

I have had 4 more crashes tonight. All with either ntoskrnl.exe alone or with ntfs.sys as the culprit.

What makes you think it is a CPU or board problem? I'm just trying to understand. Thanks for taking time to help me.
 
It's just a guess. These kind of issues are hard to troubleshoot without swapping parts. They are usually hardware related.
Just google for ntoskrnl and ntfs BSOD and you'll find lot of threads with no definite solution.
Memory, HDD, drivers, or other controllers issues.... hard to say.
I would firstly return the memory (if possible) and change for GSkill, Corsair or Kingston.
If still the same, RMA the board.
 
SYSYEM_SERVICE_EXCEPTION is most often thrown due to bad RAM. That being said, you did run with a single stick and the errors remained, and the fact you BSOD's during windows install narrows your focus down to the motherboard, HDD, or RAM.

I'm leaning toward the possibility that one of the RAM slots on the motherboard might be bad. Only thing I can think of is to use a single (different) stick of RAM in a different slot. If two different sticks of RAM give BSOD's in different RAM slots, then I'd RMA the motherboard.
 
Solution

Nick N

Honorable
Aug 10, 2013
18
0
10,510
I returned the Patriot RAM and got 2x4GB Kingston XMP Hyper X DDR3 1600MHz.

I ran a quick 15 minute Furmark GPU test which came back fine and then started running memtest86+. 2 passes in and no errors.

I plan on letting it run all night and then have my son game on it all day tomorrow. I will update with results end of day tomorrow or sooner if errors.