Random BSOD, not sure what the cause is

s2323 · 04 Apr 2012

I received a BSOD today, after starting Firefox and waiting for a page to load. Windows gave me this error at first:

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    4105

Additional information about the problem:
  BCCode:    3b
  BCP1:    00000000C0000005
  BCP2:    FFFFF800033FCA9B
  BCP3:    FFFFF88002D14E80
  BCP4:    0000000000000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\040412-38126-01.dmp
  C:\Users\sammy\AppData\Local\Temp\WER-66674-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I tried WinDbg and got this:

Code:

Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\040412-38126-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:/Windows/SYMBOLS*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03251000 PsLoadedModuleList = 0xfffff800`03495650
Debug session time: Wed Apr  4 06:37:16.035 2012 (UTC - 4:00)
System Uptime: 0 days 0:09:06.455
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800033fca9b, fffff88002d14e80, 0}

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )

Followup: Pool_corruption
---------

I also tried the program "BlueScreenView" and it tells me this:

Code:

Dump File: 040412-38126-01.dmp 
Crash Time: 04/04/2012 6:38:49 AM 
Bug Check String: SYSTEM_SERVICE_EXCEPTION 
Bug Check Code: 0x0000003b 
Parameter 1: 00000000`c0000005 
Parameter 2: fffff800`033fca9b 
Parameter 3: fffff880`02d14e80 
Parameter 4: 00000000`00000000 
Caused By Driver: ntoskrnl.exe 
Caused By Address: ntoskrnl.exe+7cd40 
File Description: NT Kernel & System 
Product Name: Microsoft Windows Operating System
Company: Microsoft Corporation 
File Version: 6.1.7601.17727 (win7sp1_gdr.111118-2330) 
Processor: x64 
Crash Address: ntoskrnl.exe+7cd40 
Stack Address 1: 
Stack Address 2:  
Stack Address 3:  
Computer Name: 
Full Path: C:\Windows\Minidump\040412-38126-01.dmp 
Processors Count: 4
Major Version: 15 
Minor Version: 7601 
Dump File Size: 262,144

Other info: my 1-year-old laptop is running an OEM version of Windows 7 Home Premium. I attached both the Windows_NT6_BSOD_jcgriff2 folder and perfmon /report contents as well as the minidump file. Please help me make sense of what's going on here! What process caused this BSOD? Thanks!

zigzag3143 · 04 Apr 2012

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

RAM - Test with Memtest86+

Driver verifier

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.

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

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 "Special Pool", "Force Pending I/O Requests" and "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.

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.

s2323 · 04 Apr 2012

^Um, all verifier.exe managed to do was make my laptop fail to boot, and I had to go into the BIOS window and start Windows 7 again with 'last known settings'.

I really don't have time to burn a CD or do memtest and I work on this laptop, so is there anything else I can do to find out what caused this BSOD?

I was hoping you would scan the dump file because I haven't been able to properly configure the symbols for it--keeps giving me errors. I think that's why it produces such a short Bugcheck Analysis.

zigzag3143 · 04 Apr 2012

s2323 said:

^Um, all verifier.exe managed to do was make my laptop fail to boot, and I had to go into the BIOS window and start Windows 7 again with 'last known settings'.

I really don't have time to burn a CD or do memtest and I work on this laptop, so is there anything else I can do to find out what caused this BSOD?

I was hoping you would scan the dump file because I haven't been able to properly configure the symbols for it--keeps giving me errors. I think that's why it produces such a short Bugcheck Analysis.

Um, I did the first time, how do you think I came to the memory exception conclusion?