BSOD at random, errors 0x0000001e, 0x00000024, 0x0000003b, 0x00000050

RAM settings all look good. Memtest86+ does not always catch memory errors. Sometimes, it is better to test your RAM as in Part 3 of the Memtest86+ tutorial, but instead of testing each module and slot through Memtest86+, test them by doing your normal routine in Windows. If you get a blue screen crash, that module or slot is bad. If the system is stable, the module and slot are good, and you can test the other slots with the good module. Then test the other module in the good slot. If both modules cause blue screen crashes in all slots, then there is something else underlying causing your crashes.


First, disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:

verifier /reset

-> Restart your computer. Then test the RAM modules. Avoid Static Damage to Your PC when swapping out the RAM modules.


There is another form of memory in your system that could be causing the crashes, as well. Use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.

OK thanks for the reply, I'll try switching my RAM around. For the stress test, does it matter that I don't actually have a video card but instead it is an onboard gfx card that is built into the mobo? Also I forgot to mention that before all these crashes started happening, my onboard sound started going bad and I had to replace it with a sound card. Could it be that the motherboard itself is going bad?

No need to run the graphics card memory test if you have onboard graphics. Onboard graphics uses the RAM for the memory, so switching the RAM around should resolve the problems if they are the issue. And yes, it could be the motherboard, but we should try to rule out other causes first.

Okay, I've switched the RAM around to different slots and it still crashes at least once a day. Do you have any other suggestions? Could it be a driver fault or is it looking like I need a new mobo?

We can try Verifier again and see if we have better luck this time. There are better settings for internet debugging than those used before. The ones you used before are typically for on site debugging (as in actually having your system in front of us and running a Kernel debugger).

• To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 208158
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  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 System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.

The driver verifier was turned on on the 25th. Hopefully this helps, thanks.

Attachment 209093

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\tctam\Windows_NT6_BSOD_jcgriff2\Windows_NT6_BSOD_jcgriff2\042612-18127-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e53650
Debug session time: Thu Apr 26 17:45:35.221 2012 (UTC - 6:00)
System Uptime: 0 days 2:54:34.954
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {115, fffffa80076963b0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000115, System didn't finish shutting down in a long time.
Arg2: fffffa80076963b0, The address of the thread responsible for the shutdown, that might be deadlocked.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_115

FAULTING_THREAD:  fffffa80076963b0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800031143dc to fffff80002c8bc80

STACK_TEXT:  
fffff800`00b9c4e8 fffff800`031143dc : 00000000`000000c4 00000000`00000115 fffffa80`076963b0 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c4f0 fffff800`0312159e : fffff800`02e03080 00000000`0000eb00 fffff980`041eaee8 fffff980`041eaf28 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff800`00b9c530 fffff800`02c9695c : fffff800`00b9c600 fffff800`00000000 00000000`40eb0088 fffff800`00b9c600 : nt!ViShutdownWatchdogExecuteDpc+0x8e
fffff800`00b9c570 fffff800`02c967f6 : fffff980`041eaee8 00000000`000a3eeb 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`02c966de : 00000018`638f2bbf fffff800`00b9cc58 00000000`000a3eeb fffff800`02e04fe8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02c964c7 : 00000023`5c134bc2 00000023`000a3eeb 00000023`5c134b0e 00000000`000000eb : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02c8398a : fffff800`02e00e80 fffff800`02e0ecc0 00000000`00000000 fffff880`014a3a00 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  .thread 0xfffffa80076963b0 ; kb

FOLLOWUP_IP: 
nt!VerifierBugCheckIfAppropriate+3c
fffff800`031143dc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

FAILURE_BUCKET_ID:  X64_0xc4_115_VRF_nt!VerifierBugCheckIfAppropriate+3c

BUCKET_ID:  X64_0xc4_115_VRF_nt!VerifierBugCheckIfAppropriate+3c

Followup: MachineOwner
---------

The crashes are still all over the place... One of the crashes did indicate hard disk problems. Run another disk check. I have also seen disk checks come up clean on faulty drives, so run the SeaTools short and long tests to check the drive.

Disable Verifier before doing the hard disk diagnostics.

I ran the short test and it came up negative, I haven't been able to run the long test yet, but now the computer not only blue screens but has been freezing randomly. It has frozen several times while using chrome and frozen when I try to log in to windows.

Continue with the long test and post back how it goes. We'll proceed with other troubleshooting steps if it comes up clean.