Solved Random BSOD's, error 0x0000003b... I don't know what to do!

[Savoysuit]

Hi everyone,

EDIT: :::I have now attached a zip with the info:::

I'm a first time poster... and also only average when it comes to technical know-how with computers (so go easy on me lol).

I'm getting a lot of BSOD's this is the information from the one that just happened. I was just surfing the net (I think I had some music playing as well). It seems to be happening more and more. Before it was only every few days... but for example today I have had it 5 times so far! I'm freaking out a bit...


I have a laptop machine with these basic specs:

2630 QM
8G RAM
AMD Radeon 6870m



Here is some information from the last 2 BSOD's:

==================================================
Dump File : 120211-36223-01.dmp
Crash Time : 02/12/2011 6:53:42 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d1fb55
Parameter 3 : fffff880`0a1f5b40
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\120211-36223-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================


and


==================================================
Dump File : 120111-20950-01.dmp
Crash Time : 01/12/2011 12:25:35 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d7e4b3
Parameter 3 : fffff880`0652dda0
Parameter 4 : 00000000`00000000
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+313f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\120111-20950-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================



please help... it's a pretty new machine and I spent a fair amount of money... don't want it to have problems!

 

[writhziden]

In order to further assist you, we need the actual dmp files. If you follow http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html, you can download an executable that will copy your dmp files into a folder in your documents folder. Then you can get the system report and put it in your documents folder and zip both files together (the instructions are very clear on how to do so in the above link). Thank you.

 

[JMH]

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory

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.

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

IF YOU ARE OVERCLOCKING STOP!

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.

 

[Savoysuit]

Hi,

thank you for your responses and sorry for not realizing I needed to post that stuff. I have now attached the info you asked for.


I hope this helps!! I'm at a loss here.

here's my system:

Windows 7 Home 64bit
It's OEM
THe system is only 2 months old


p.s. It says in one of the files that I don't have a virus scanner... but I do... I've installed Microsoft security essentials...

 

[Savoysuit]

sorry for the bump... I'm just wondering if maybe I have a network issue that's causing it? I'm using a usb modem (but have been for 2 weeks and the problems have only been getting really bad in the last few days). I noticed that there was some sort of bluetooth error in the analysis....

 

[writhziden]

Your problems are all related to memory corruption, which could mean a bad module/slot, or it could be an underlying driver problem. Start with the memory testing first:
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial.

After the above steps, run Driver Verifier as follows:
1. Backup your system and user files
2. Create a system restore point
3. If you do not have a Windows 7 DVD, Create a system repair disc
4. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the above steps.

 

[JMH]

Following on from writhziden's advice.

* You say your computer is only only 2 months old.
Is it under Warranty?

* FYI
Microsoft states that the possible fixes for the BCC 3B include:

> Download and install updates and device drivers for your computer from Windows Update.
> Scan your computer for computer viruses.
> Check your hard disk for errors.

* Another possibility is this error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

You could...
> Run a Malwarebytes scan.
Malwarebytes Anti-Malware - Free software downloads and software reviews - CNET Download.com

> Run chkdsk
http://www.sevenforums.com/tutorials/433-disk-check.html

> Re-install graphics driver using this method

When upgrading your graphic driver you MUST remove all traces of the current driver.
In order to do that we recommend using

Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

 

[Savoysuit]

thank you. I will try this stuff tonight and let you know how it goes...

as for warranty... yes I have one, but it's pretty much useless since I am now in a different country than where I bought the computer.

 

[Savoysuit]

Could this have solved my problem? Until today, for the past 2 weeks I was using a usb modem... today I was able to hook my pc up to a cable. So far after a few hours of use I have had no crashes.

I always found the usb modem to be a bit annoying, and maybe caused conflicts with my computer.

Is it within the realm of possibility that this could have solved it, or am I just fooling myself?

 

[JMH]

Keep it under observation.

 

[Savoysuit]

hi guys,

so I ran memtest86 and it found 2128 errors. What can I do? I know you say to then test each stick, but that is so far beyond my abilities... especially with a laptop (I could probably do it with a desktop).

I should also clarify that this is an alienware machine... so I'd have open up BOTH sides of the computer (I'm not doing that). Like I said, my warranty is basically useless right now.

would a computer shop be able to help me?

 

[Savoysuit]

so I had another crash... but it was a DIFFERENT error code... I have attached information.

What does this now mean?

 

[writhziden]

Your most recent crash was hard drive related. To fix the issue:
1. Click Start Menu
2. Click My Computer
3. Right click the C: drive
4. Click Properties
5. Click the Tools tab
6. Click Check now...
7. Put a tick in Automatically fix file system errors
8. Click OK.
9. Click Yes.
10. Restart your computer.

 

[writhziden]

You are also still having memory corruption issues, which makes sense since Memtest86+ found errors. Contact your laptop vendor for the procedure on how to access your memory modules (i.e. call them, e-mail them, look for the manual for the laptop, etc.)

Edit: If you are still under warranty by the manufacturer/vendor, see if you can get a service done to fix the computer. That is the safest/most efficient way to get it fixed.

 

[Savoysuit]

do you think the 2 could be connected?

 

[writhziden]

do you think the 2 could be connected?

Possibly, especially if any blue screens caused a total system crash where nothing could be written to the disk. Hard disk errors usually result from hard resets (computer is shut down improperly).

 

[Savoysuit]

so what you're saying is... continuing to use the computer could inadvertent harm my Hard drive? That's not good!

Anyhow... I ran the disk checker... that issue is now fixed I guess?

 

[writhziden]

so what you're saying is... continuing to use the computer could inadvertent harm my Hard drive? That's not good!

Anyhow... I ran the disk checker... that issue is now fixed I guess?

It could, but I would not worry about it too much. Hard drives are fairly resilient. What is important is that we track down any underlying cause to the blue screen errors you are experiencing.

 

[Savoysuit]

Ever since I ran the disk error checker I haven't had a BSOD, and the computer has been on and (mostly) in use for 18 straight hours.

(Am I just deluding myself into hoping that maybe somehow the problem is fixed?)

 

[writhziden]

Ever since I ran the disk error checker I haven't had a BSOD, and the computer has been on and (mostly) in use for 18 straight hours.

(Am I just deluding myself into hoping that maybe somehow the problem is fixed?)

See how it goes for the next few days. Maybe it was due to errors on the disk. If it blue screens again, go into your BIOS and reset the CMOS as described in the first method of three methods to clear the CMOS and rerun Memtest86+. Memtest86+ can report false positives (negatives?) about errors being present if the CMOS becomes corrupted.