BSOD on Startup of PC SYSTEM_SERVICE_EXCEPTION and NTFS.sys

I've been asking this question for a while now and I can't seem to get it resolved. Sometime when I boot up my PC It will either BSOD asfter loading to Deskop, giving me either a SYSTEM_SERVICE_EXCEPTION or a NTFS.sys error (and sometime it will give me an error 0x0000 I cant remeber the exact code).

I've ran memtest 86 for 12 hours (pass 7) and have recieved no errors.

When I try to user driver verifier, it doesn't immediately BSOD to tell me what corrupt drivers I have. Any help on this?

cav said:

I've ran memtest 86 for 12 hours (pass 7) and have recieved no errors.

Click to expand...

As you have multiple bugcheck codes, memory is the primary suspect. And memtest86 is a crap tool, havind a deceptively similar name with memtest86+, the real memory testing tool.

Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Arc said:

cav said:

I've ran memtest 86 for 12 hours (pass 7) and have recieved no errors.

Click to expand...

As you have multiple bugcheck codes, memory is the primary suspect. And memtest86 is a crap tool, havind a deceptively similar name with memtest86+, the real memory testing tool.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Click to expand...

I just ran memtest 86+ for 22 hours (7 am Thursday to 6 am Friday) and got to pass 10. I have recieved NO errors at all

Good news.

Now enable Driver Verifier to monitor the drivers. Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.



Let us know the results, with the subsequent crash dumps, if any.

Arc said:

Good news.

Now enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why 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.

   Warning

Before 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.

   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.

Let us know the results, with the subsequent crash dumps, if any.

Click to expand...

so ive left driver verifier running for pretty close to 24 hours (its been 19 atm and I still haven't turned it off) but I still haven't received a single BSOD. I posted this a bit early because it seems to me like the verifier will not BSOD my pc within 24 hours, but i will continue to let it run until it hits that mark. I will upload my minidumps too.

Disable DV now. 24 hours are enough to run it.

Do one further test ... Test your HDD using Data Lifeguard Diagnostic for Windows. Take both the short test and the extended test.

I will wait to see one more BSOD in normal mode, to comment any further on it.

Arc said:

Disable DV now. 24 hours are enough to run it.

Do one further test ... Test your HDD using Data Lifeguard Diagnostic for Windows. Take both the short test and the extended test.

I will wait to see one more BSOD in normal mode, to comment any further on it.

Click to expand...

I just finished the two tests and I passed on both the short and the extended. I will report back if I recive another BSOD like you said

Arc said:

Disable DV now. 24 hours are enough to run it.

Do one further test ... Test your HDD using Data Lifeguard Diagnostic for Windows. Take both the short test and the extended test.

I will wait to see one more BSOD in normal mode, to comment any further on it.

Click to expand...

hey so i got another bsod (booted up, got to desktop, bsod, restarted, everything was fine). It was a system_service_exception and had a technical error or 0x0000003b *something similar to this.

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Arc said:

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Click to expand...

I used the dm log collector. here is my my file.

Another BSOD pointing towards the memory issue, but you reported that the tests found nothing.

In this situation it would be the best that you perform a clean reinstall. If any undiscovered driver is causing the issue, that will be supposed to be rectified by it. And if the BSODs does not stop, we have to understand that it is the hardware that is the problem.

Arc said:

Another BSOD pointing towards the memory issue, but you reported that the tests found nothing.

In this situation it would be the best that you perform a clean reinstall. If any undiscovered driver is causing the issue, that will be supposed to be rectified by it. And if the BSODs does not stop, we have to understand that it is the hardware that is the problem.

Click to expand...

I'm planning on getting an ssd (samsung 840 evo 120) for Christmas. I'd rather wait until then since I'm planning on running windows off of that. Quick question to prepare before hand, I just realized I have an OEM version of windows 7, will I run into any problems reinstalling or activating it since I read something about OEMs only being able to be installed on one PC at a time.

A desktop with OEM license means it is system builder license. All versions of windows (OEM or retail) can be used on a single machine at a time. The main feature of OEM that the license is tagged with the motherboard.

You can use a retail license for activating windows installations on different machines, but not at the same time. Whereas an OEM license is for activating a single machine only, using the unique motherboard.

You are putting a new disc only, with the same motherboard. So activation will not be any problem after installation.

Arc said:

A desktop with OEM license means it is system builder license. All versions of windows (OEM or retail) can be used on a single machine at a time. The main feature of OEM that the license is tagged with the motherboard.

You can use a retail license for activating windows installations on different machines, but not at the same time. Whereas an OEM license is for activating a single machine only, using the unique motherboard.

You are putting a new disc only, with the same motherboard. So activation will not be any problem after installation.

Click to expand...

Hey Arc, it's been a while but I got a new SSD recently and performed a clean install of Windows 7 onto it. However I still seem to be having that BSOD on startup issue. I recently got a SYSTEM_SERVICE_EXCEPTION and a Stop 0x00000024. Any suggestions on how to fix it?

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Arc said:

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Click to expand...

sorry for the late reply I just got back from school. Anyways here are my minidumps using the DM Log Collector!

Another clueless BSOD. Better we start from the old tests again.

Test your RAM modules for possible errors.Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.



Let us know the results, with the subsequent crash dumps, if any.

Arc said:

Another clueless BSOD. Better we start from the old tests again.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why 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.

   Warning

Before 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.

   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.

Let us know the results, with the subsequent crash dumps, if any.

Click to expand...

Hey Arc, sorry for the EXTREMELY late reply but I got caught up with some school work and other activities in life. Anyways, this issue is kinda scaring me a bit more now because I just recieved a BSOD while browsing the web, which is something that has never happened before. I used BlueScreenView to save my minidump as a text file but seeing as how its the only minidumo I have aside from the one I showed you before I will post it here:
==================================================
Dump File : 020315-5943-01.dmp
Crash Time : 2/3/2015 6:25:46 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`08cf88f8
Parameter 3 : fffff880`08cf8150
Parameter 4 : fffff800`02c968d0
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+4211
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+76e80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020315-5943-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7601
Dump File Size : 352,013
Dump File Time : 2/3/2015 6:26:49 PM
==================================================

Anyways, I am EXTREMELY sorry about these frequent posts and late replies. I just keep getting put into situations that I have to focus more on forget to comment back. I apologize if this is inconvenient for you.

If you report a BSOD, please do it following the Blue Screen of Death (BSOD) Posting Instructions .... otherwise we have nothing in hand.

Arc said:

If you report a BSOD, please do it following the Blue Screen of Death (BSOD) Posting Instructions .... otherwise we have nothing in hand.

Click to expand...

I used SF Diagnostic Tool. Here is my file