BSOD crash of SYSTEM_SERVICE_EXCEPTION ntoskrnl.exe pls help!!!

[weingkham]

m getting BSOD frequently sometimes more than 4 in one hour ..after doing some research i installed the BLUESCREEN VIEWER where from i got this error type.pls guys help me solve this bug

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[weingkham]

OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DOMINO-PC
System Manufacturer INTEL_
System Model DH55PJ__
System Type x64-based PC
Processor Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz, 3193 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Intel Corp. TCIBX10H.86A.0035.2010.0429.1516, 29-04-2010
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale India
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name domino-PC\domino
Time Zone India Standard Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.86 GB
Available Physical Memory 5.65 GB
Total Virtual Memory 15.7 GB
Available Virtual Memory 13.2 GB
Page File Space 7.86 GB
Page File C:\pagefile.sys

 

[weingkham]

https://rapidshare.com/files/1382260897/minidump.zip

 

[weingkham]

plus i even got this BSOD also NTFS_FILE_SYSTEM Ntfs.sys

 

[zigzag3143]

plus i even got this BSOD also NTFS_FILE_SYSTEM Ntfs.sys

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[weingkham]

btw my rams were new i got it last two months ago only ( corsair vengence 1600mhz ddr3) can it get corupt so soon

 

[weingkham]

i didnt overclocked but i did put on some log in screen and windows 8 theme by editing some system files...got it throught devianart
1. Windows 7 - Metro UI Login by ~poiZNxx on deviantART

2. Windows 8 VS for Win7 by =fediaFedia on deviantART

these got error after i did sfc /scannow so removed both.
should i remove rainmeter

 

[writhziden]

i didnt overclocked but i did put on some log in screen and windows 8 theme by editing some system files...got it throught devianart
1. Windows 7 - Metro UI Login by ~poiZNxx on deviantART

2. Windows 8 VS for Win7 by =fediaFedia on deviantART

these got error after i did sfc /scannow so removed both.
should i remove rainmeter

Plenty use rainmeter without issues. How is the system currently responding to the theme removal?

btw my rams were new i got it last two months ago only ( corsair vengence 1600mhz ddr3) can it get corupt so soon

Further reading regarding this question: Avoid Static Damage to Your PC | PCWorld