BSOD 0x3b both idle and playing

elbondish · 20 Jan 2013

Hello!

Since two days back Ive had some problems with random BSOD. All of them gives the same STOP code: 0x00...03b.
Im having a hard time figuring out whats causing it and the hole thing with reading dump files is all new to me. So I would really appreciate if you could help me or point me in the right direction.

I think its got to be something with some drivers. Most likely the GPU ones since it started after I tried to install a new graphic card. The new card didnt send any signals to the monitor so I put the old one back and after a couple of hours the first BSOD appeared.

Arc · 21 Jan 2013

Hello elbondish.

Scan the system for possible virus infection.

Code:

fffff880`0e185608  fffff880`06f55952Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
 aswSP+0x1c952

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download, install and update those, and then run full system scans with both of them, one by one, too.

Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept the restart.

Update Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC driver from Realtek

The Display driver you are using is problematic. Roll back to a stable earlier one.

Download and install Driver Fusion.
Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

Let us know the results.

elbondish · 26 Jan 2013

Hello again!

I thought I would brief you on how things went.

I followed all the steps you provided and along the way almost at every step I got a BSOD and a lot of different Codes causing the crash. Ive done a sf_diagnostic gathering from the latest BSOD thats added to this post.

For example when I did the WDO full scan the computer crashed twice. Same with WSE full scan. When I tried to do the short scans they both worked and no threats were found.

When I removed all programs except the anti virus to start with windows I got a 7E BSOD when I applied the changes.

Had a crash when I reinstalled the graphic drivers. I think this was caused by a express install instead of a clean one. After the restart windows made a hdd check which passed with a problem but during login I got a 1E crash and at the restart after this crash I got a 3B at login as well. After the 3B crash the computer worked for a while without crashes but at the next start up I got a BSOD code 34 and a 1A which made me wonder if my RAM was the problem.

What I didn't mention was that I installed a new set of RAM three days before the first BSOD. I didn't think they were the problem but after the 1A crash I tried to replace them with my old ones and after that the computer have not had any crashes even thought I have been playing games and such.

Can you see in the BSOD reports if the rams were the problem or shall I do a memory test on the new pair?

Arc · 26 Jan 2013

There is a probability that it may be RAM, but the dumps are not saying it precisely.

Code:

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000001238, The subtype of the bugcheck.
Arg2: fffffa8009f02010
Arg3: 0000000000000802
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_1238

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f8a0ef to fffff80002e99fc0

STACK_TEXT:  
fffff880`08acc678 fffff800`02f8a0ef : 00000000`0000001a 00000000`00001238 fffffa80`09f02010 00000000`00000802 : nt!KeBugCheckEx
fffff880`08acc680 fffff880`0193beb2 : 00000000`000004e6 fffffa80`09f02010 fffffa80`07d08118 00000000`000004e7 : nt!MmFreePagesFromMdl+0x5f
fffff880`08acc6e0 fffff880`0193b7df : fffffa80`07d08118 00000000`00000000 fffffa80`07da9ec6 fffffa80`00000000 : rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+0x4e
fffff880`08acc740 fffff880`0193a4ce : fffffa80`07d080b0 00000000`00000001 fffffa80`07d080b0 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCleanup+0x183
fffff880`08acc780 fffff880`01939a27 : fffffa80`07d080b0 00000000`00000001 fffffa80`07d080b0 fffff880`08accb60 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStCleanup+0x7a
fffff880`08acc7c0 fffff880`0193998a : fffff880`0195c8f0 00000000`00000008 fffffa80`07d080b0 fffff880`0195c870 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmStoreMgrCallback+0x4b
fffff880`08acc800 fffff880`019604b8 : fffff880`0195c870 fffff880`08accb60 00000000`00000000 fffffa80`07c13c58 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmCleanup+0x9a
fffff880`08acc830 fffff880`01941b26 : fffffa80`0a043990 fffffa80`0a043990 fffff683`00000000 00000000`00000000 : rdyboost!SmdRBContextShutdown+0x94
fffff880`08acc870 fffff800`031b0687 : 00000000`00000000 fffffa80`0a075760 fffffa80`0a075878 fffffa80`0a043990 : rdyboost!SmdDispatchDeviceControl+0x3ce
fffff880`08acc8d0 fffff800`031b0ee6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`08acca00 fffff800`02e99253 : fffff880`08accb60 0000007f`ffffffff fffffa80`098e0520 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`08acca70 00000000`77b6138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`012fee08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b6138a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e
fffff880`0193beb2 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7982e

FAILURE_BUCKET_ID:  X64_0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

BUCKET_ID:  X64_0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

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

Anyway, as it is not crashing after changing the RAM, you need to test the RAM that was in use in the earlier time.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.