Frequent BSOD mostly with STOP code 3B and win32k.sys

fslateef · 26 Jun 2011

Thanks mgorman87, the article is very good although I am not clear that running RAM in 1600MHz speed is going to damage my CPU's memory controller Or if I use this like now (means with some crashes) then its fine ?

Also I ran sfc /verifyonly and sfc /scannow _and_ there is nothing wrong with system-files.

Another question if can give me some suggestions:

-- According to my motherboard memory QVL G.Skill 1600MHz is supported with 8-8-8-24 timings and other one is supported with 7-7-7-24. These are the closest to my current RAM specs which is 7-8-7-24. So now can I try using 1600MHz with 8-8-8-24 ? Or its not possible to increase timings ?

Thank you very much for your help.

mgorman87 · 26 Jun 2011

Are you running two different brands/types of memory?

fslateef · 27 Jun 2011

No, they are same brand with exactly same model number ... 2 x F3-12800CL7-4GBRM (2 x 2GB kit) (7-8-7-24).

According to motherboard QVL list, the closest (to my current model) compatible are F3-12800CL8-4GBRM (8-8-8-24) and F3-12800CL7-4GBRH (7-7-7-24). So the only difference between my model and listed model is only one timing

fslateef · 27 Jun 2011

Hi,

Yesterday I changed memory settings to default which is 1333MHz with 9-9-9-24 timings. Then ran Prime95 blend test and got crash in 30mins or so .....

Here's the dump, please suggest something if possible soon. I am now getting one crash per day at-least

My System is not overheating during Prime95 blend test I think, CPU temp was 59 constantly, NB was 30 and GPU was around 30.

Thanks for helping,

Waiting for reply.

mgorman87 · 28 Jun 2011

The crash happened while running the mcafee back up (MOBKbackup). For testing purposes, I would like you to completely remove McAfee from your system. Use MSE as a replacement. Virus, Spyware & Malware Protection | Microsoft Security Essentials See if the crashes continue

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun 27 14:08:25.422 2011 (UTC - 4:00)
System Uptime: 0 days 0:28:44.578
Probably caused by : ntkrnlmp.exe ( nt!NtWaitForMultipleObjects+fe )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  MOBKbackup.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!NtWaitForMultipleObjects+fe
BiosReleaseDate = 04/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

fslateef · 29 Jun 2011

Thanks mgorman87 for helping. I will uninstall mcafee and will give it a try.

I yesterday installed Coolermaster V6 GT CPU cooler which covered my first RAM slot thus I had to remove one 2GB RAM module. Now I am running 3 x 2GB DDR3 RAMs at motherboard's auto/default 1333 9-9-9-24 configuration.

When I started booting into Windows and logged-in to my id, system crashed again with BSOD mentioning MEMORY_MANAGEMENT and stop code 0x1A. After that rebooted fine and I just spent 10mins on it as it was late night. I don't have bsod dump at the moment but I will post it as soon as reach home.

So my question is: on dual channel, can I use 3 DIMM modules (not in full pairs) ? and if yes then beside performance is it going to effect OS functionality ?

Thanks again.

fslateef · 29 Jun 2011

Attaching yesterday's BSOD mentioning stop code 0x1A and MEMORY_MANAGEMENT on 2nd line of BSOD.

fslateef · 29 Jun 2011

Latest BSOD, now mentioning NTFS.sys and stop code 0x24 in BSOD screen

mgorman87 · 30 Jun 2011

I wouldn't run the RAM like that. You don't want to have a missing pair in there it can cause problems. Try running with just the two sticks. Also, your last crash happened when McAfee was the top process. Have you not removed it yet? As for the memory crash try running memtest from a cold boot for about 15minutes.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jun 29 16:56:07.557 2011 (UTC - 4:00)
System Uptime: 0 days 0:16:50.650
Probably caused by : Ntfs.sys ( Ntfs!NtfsSetFileObject+107 )
PROCESS_NAME:  mcshield.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsSetFileObject+107
BiosReleaseDate = 04/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 28 19:37:57.064 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:10.266
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46585 )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  SearchIndexer.
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46585
BiosReleaseDate = 04/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

fslateef · 30 Jun 2011

Thanks for reply. I haven't removed mcafee yet (sorry for this). I was assuming that mcafee is fine as I am running the same version (got 3-licenses) on my Windows 7 Pro 64-bit 'Dell Studio 1557' laptop and haven't faced any BSOD.

Can this be due to some HDD issue ? Although I haven't have any issues in downloading, copying files to and from that HDD and even installing Games on main OS/C drive.

Today I will try to install fresh windows 7 on my other HDD and will install minimal drivers and softwares. Will get back to you with status.

Will run memtest again for some time (as you suggested). I don't want to use less than 6GB of RAM thats why I am avoiding removing that single extra RAM for now.