BSOD at random times, Ntoskrnl.exe, error0x0000003b

rivalscho0ls · Nov 21, 2011

Hi everyone,
I'm trying to get some help with these BSODs I'm getting:
==================================================
Dump File : 111911-30825-01.dmp
Crash Time : 11/19/2011 1:14:14 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d91671
Parameter 3 : fffff880`071bbab0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111911-30825-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7601
Dump File Size : 274,760
==================================================

Hardware: HP Pavillion Elite OEM Windows 7 Home Premium x64
AMD Phenom II X6 1045T Processor 2.70
8.00 GB RAM
1 TB Seagate Barracuda
AMD Radeon HD 5570

I've already sent the computer back to HP once and they claimed to hae replaced the mobo, but since I've gotten the computer back I've had 2 BSODs caused by Ntoskrnl.exe. The first one was overnight with the PC idling. The second was while streaming HD video content from giantbomb.com.

I've been searching this constantly but I have not been able to find any useful information, so I thought I'd try here. Thanks in advance for any help!

FredeGail · Nov 21, 2011

Hello Rival and welcome.

Fairly hard to analyse these dumps, but we have a few regular things to try.

Run MemTest86+

SYSTEM_SERVICE_EXCEPTION could cause a mem-corruption.

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

Update your Graphic Driver (ATI)

As far as I can see you have an ATI-card. The bug-check can also indicate broken Graphic Driver. Do the process below.

i) Find your driver here, save it to your desktop
ii) Download Driver sweeper, for the leftover files
iii) Uninstall your driver from the Control Panel
iv) While rebooting, go into safe-mode without internet (tip: plugout your LAN cable or disconnect wireless)
v) Run Driver Sweeper, click all the Nvidia components and analyse them
vi) Clean them all
vii) Head into Windows, without internet
viii) Install the Driver from the desktop

Thank you for your attention, and keep uploading dumps for further analyses.

Welcome to SevenForums again.
Fred.

zigzag3143 · Nov 21, 2011

rivalscho0ls said:
Hi everyone,
I'm trying to get some help with these BSODs I'm getting:
==================================================
Dump File : 111911-30825-01.dmp
Crash Time : 11/19/2011 1:14:14 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d91671
Parameter 3 : fffff880`071bbab0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111911-30825-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7601
Dump File Size : 274,760
==================================================

Hardware: HP Pavillion Elite OEM Windows 7 Home Premium x64
AMD Phenom II X6 1045T Processor 2.70
8.00 GB RAM
1 TB Seagate Barracuda
AMD Radeon HD 5570

I've already sent the computer back to HP once and they claimed to hae replaced the mobo, but since I've gotten the computer back I've had 2 BSODs caused by Ntoskrnl.exe. The first one was overnight with the PC idling. The second was while streaming HD video content from giantbomb.com.

I've been searching this constantly but I have not been able to find any useful information, so I thought I'd try here. Thanks in advance for any help!

Bet you got NTOSKRNL.exe as being the cause from Blue screen view.

First:

I do notice Symantec which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials at least to test.

http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

http://www.microsoft.com/security_essentials/

These crashes were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.

1-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 or 6 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.

Click to expand...

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

2-Driver verifier

I'd suggest that you first backup your data 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"
- 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.

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

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.

Click to expand...

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

rivalscho0ls · Nov 21, 2011

Thanks for the tips guys.

I did forget to mention that I've run both Memtest86 and Memtest86 plus on each individual stick for at least 5 to 6 passes each prior to sending the computer away. I had no errors on any of the sticks, so I even went so far as to test each of the DIMMs separately for 5-6 passes with the same stick, and no errors.

I actually just uninstalled everything symantec - I had microsoft security essentials already installed, and just hadn't removed the symantec stuff yet.

I'll see how it runs after removing that, and if I get another BSOD, I'll move on to the other suggestions. I'll let you know how it goes.

Thanks!

zigzag3143 · Nov 21, 2011

rivalscho0ls said:
Thanks for the tips guys.

I did forget to mention that I've run both Memtest86 and Memtest86 plus on each individual stick for at least 5 to 6 passes each prior to sending the computer away. I had no errors on any of the sticks, so I even went so far as to test each of the DIMMs separately for 5-6 passes with the same stick, and no errors.

I actually just uninstalled everything symantec - I had microsoft security essentials already installed, and just hadn't removed the symantec stuff yet.

I'll see how it runs after removing that, and if I get another BSOD, I'll move on to the other suggestions. I'll let you know how it goes.

Thanks!

Good luck

BSOD at random times, Ntoskrnl.exe, error0x0000003b

rivalscho0ls

New member

My Computer

FredeGail

It's full of stars

My Computer

zigzag3143

Account closed by request

My Computer

rivalscho0ls

New member

My Computer

zigzag3143

Account closed by request

My Computer