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

[fslateef]

I recently build a custom machine (specs in detail are in "My System Specs") and getting BSODs randomly and from past 2-days its frequent. Last 3 BSODs are with stop code 3B + win32k.sys (I am attaching my latest dump) and before that BSOD was with stop code 24 + ntfs.sys.

I tried removing all overclocking and hardware management tools from manufacturer but the problem is still there. I last 4 or 5 BSODs happened when system doing nothing or very little work like simple browsing; I haven't saw any BSOD while playing games like Crysis with maximum settings.

From past some-days I am trying to understand analyzing BSODs and tried running windbg but its not able to load symbols. Can anyone point me to some tutorial for setting-up and using windbg ?

I also tried using Driver-Verifier and each time I run it with whatever driver I select to test (without selecting Low Resources/Memory Simulation option); it crashes before booting into Windows. The BSOD for verifier always has stop code D5 and no information about any .sys driver or process. Is this suppose to happen ? If not then is this giving some hints ? I first tried selecting "not verified drivers by windows" which are atikmdag.sys and atikmpag.sys and it gave me BSOD with stop code D5 all the time and then I selected win32k.sys only and it gave me again same D5 error.

Can someone help me in this regard ? I am getting frustrated (as I already spent lot of money and time in building this system)

Thanks in advance.

P.S. I have Mcafee total-protection installed. Also if my logs are not complete then let me know as I am at job and will reach home after some hours. So please don't mind if I posted in wrong manner.

I will also try to post dump again tonight according to what forum rules says.

 

[fslateef]

Here's the complete dump and perfmon report as per rules. This dump contains all crashes/BSOD happened till now and includes 4 crashes with Stop Code D5 when I was trying to run Verifier for different drivers.

System basic info: (details are in my system details link, please don't mind):

Windows 7 x64 Professional with SP1
Dell OEM version
System/Hardware age - less than 1-month
Windows recently installed (less than a week ago)


Please respond as early as possible.

 

[fslateef]

Can anyone help me for this please ?

Yesterday I tried running Prime95 64-bit with custom settings (might be running FFT only not sure will do Blend tonight) for 2 hours and 10 minutes with utilizing 6.5GB of RAM by Prime95 and around 700MB by windows (out of 8GB); Haven't got any errors or crash and my CPU and NB/SB temperatures remained quite fine I think. I am attaching screen-shot also when test was running for 2-hours. You can see RAM/CPU utilization in right hand side and temperature in left side.

 

[mgorman87]

Lots of stuff going on here.

First off, your verified dumps are blaming your ASUS video card driver. This is a driver that is installed when you use the CD that came with your video card to install the drivers. You need to uninstall your video card from device manager and then reinstall the drivers from the ATI site.
ATI Radeon

MOBK.sys     Thu Dec 31 22:20:07 2009 (4B3D69E7)

I guess this driver belongs to something called Mozy? It was blamed in one of the crashes. If you don't need it then uninstall. If you do then try to find a newer driver.

athrx.sys    Mon Oct 05 12:33:57 2009 (4ACA1FF5)

Update your Atheros driver. It was blamed in a crash -
ATHEROS drivers for Microsoft Windows

sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)

Removed Daemon Tools/Alcohol 120%. Its driver, SPTD, is known to cause BSODs. Once the program is removed run the SPTD removal tool. DuplexSecure

Run a memory test
Memtest86 - Run for 7-8 passes - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 21 18:37:25.742 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:15.851
*** ERROR: Module load completed but symbols could not be loaded for ATKDispLowFilter.sys
Probably caused by : ATKDispLowFilter.sys ( ATKDispLowFilter+d8e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD5_VRF_ATKDispLowFilter+d8e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 21 18:21:22.090 2011 (UTC - 4:00)
System Uptime: 0 days 0:36:31.838
Probably caused by : win32k.sys ( win32k+83cd0 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k+83cd0
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 21 17:41:45.340 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:13.088
*** ERROR: Module load completed but symbols could not be loaded for ATKDispLowFilter.sys
Probably caused by : ATKDispLowFilter.sys ( ATKDispLowFilter+d8e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD5_VRF_ATKDispLowFilter+d8e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 21 17:34:19.558 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:13.667
*** ERROR: Module load completed but symbols could not be loaded for ATKDispLowFilter.sys
Probably caused by : ATKDispLowFilter.sys ( ATKDispLowFilter+d8e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD5_VRF_ATKDispLowFilter+d8e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 21 17:25:17.168 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:13.277
*** ERROR: Module load completed but symbols could not be loaded for ATKDispLowFilter.sys
Probably caused by : ATKDispLowFilter.sys ( ATKDispLowFilter+d8e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD5_VRF_ATKDispLowFilter+d8e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 21 17:15:02.683 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:13.792
*** ERROR: Module load completed but symbols could not be loaded for ATKDispLowFilter.sys
Probably caused by : ATKDispLowFilter.sys ( ATKDispLowFilter+d8e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD5_VRF_ATKDispLowFilter+d8e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 21 15:39:27.532 2011 (UTC - 4:00)
System Uptime: 0 days 0:39:27.280
Probably caused by : win32k.sys ( win32k+158ca5 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k+158ca5
BiosReleaseDate = 04/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 18 22:38:11.554 2011 (UTC - 4:00)
System Uptime: 0 days 7:04:33.663
*** WARNING: Unable to verify timestamp for MOBK.sys
*** ERROR: Module load completed but symbols could not be loaded for MOBK.sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsReleaseAllFiles+4b )
PROCESS_NAME:  svchost.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!NtfsReleaseAllFiles+4b
BiosReleaseDate = 04/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun 17 14:58:20.796 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:53.528
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+f2061 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_athrx+f2061
BiosReleaseDate = 04/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[fslateef]

Lots of stuff going on here.

First off, your verified dumps are blaming your ASUS video card driver. This is a driver that is installed when you use the CD that came with your video card to install the drivers. You need to uninstall your video card from device manager and then reinstall the drivers from the ATI site.
ATI Radeon

MOBK.sys     Thu Dec 31 22:20:07 2009 (4B3D69E7)

I guess this driver belongs to something called Mozy? It was blamed in one of the crashes. If you don't need it then uninstall. If you do then try to find a newer driver.

athrx.sys    Mon Oct 05 12:33:57 2009 (4ACA1FF5)

Update your Atheros driver. It was blamed in a crash -
ATHEROS drivers for Microsoft Windows

sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)

Removed Daemon Tools/Alcohol 120%. Its driver, SPTD, is known to cause BSODs. Once the program is removed run the SPTD removal tool. DuplexSecure

Run a memory test
Memtest86 - Run for 7-8 passes - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

I am really thankful for your detailed suggestions and response.

I will install ATI drivers from AMD site; I was thinking that I am using official driver from AMD but I was wrong as you mentioned me.

I think I haven't installed anything like mozy _but_ a quick google on MOBK.sys tells that its provided by windows and its not specifically a device-driver. I will try to look for its source to uninstall but if its from Windows then it won't be possible to remove.

I will update Atheros driver. And remove Alcohol also. Can you suggest some alternative ?

Another question: The driver-verifier should not crash system if everything is fine or working ?

For memory test, I will do this but isn't running Prime95 with utilizing all available RAM tested it also ?

Thanks again.

 

[mgorman87]

MOBK is not a Windows driver. It is part of a 3rd party application.

You can use MagicISO as an alternative.

Driver verifier shouldn't crash the computer if there are no bad drivers

I think Prime95 and Memtest test the memory differently. Run memtest for 7-8 passes for best results.

 

[fslateef]

MOBK is not a Windows driver. It is part of a 3rd party application.

You can use MagicISO as an alternative.

Driver verifier shouldn't crash the computer if there are no bad drivers

I think Prime95 and Memtest test the memory differently. Run memtest for 7-8 passes for best results.

Thanks for your quick reply.

I will run memtest tonight.

For MOBK I did some research an found that its part of Mcafee Online Backup and you can't stop or remove it without uninstalling Mcafee. Like MOBKbackup.exe is constantly running and can't be killed.

After following your suggestions, I removed ATI drivers from ASUS and updated Atheros driver and removed all remaining Asus's Graphics Overclocking related applications. Installed latest AMD Catalyst drivers and now Driver-Verifier is not crashing or giving BSOD.

At the moment I am running Prime95 Stress test with Blend which is working without any issues even after 3-hours. So I think my CPU is at-least good.

Will update status soon.

Thanks again.

 

[fslateef]

Hi,

I just shutdown and restarted my system and got this STOP code 3B exception. This is happening when system is idle or now when booting.

I haven't removed Alcohol 120% till now (which I am going to do first) _but_ please it will be good if you can have a look at it also and point me if something is different than before please.

------------------------

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

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

Files that help describe the problem:
C:\Windows\Minidump\062411-31637-01.dmp
C:\Users\flateef\AppData\Local\Temp\WER-67205-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

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

-------------------------------------------------------------

Attaching latest dump.

 

[fslateef]

Hello,

I am really confused; the problem is weird I am trying to explain it in as much details as possible:

-- I uninstalled Alcohol 120%
-- Ran memtest and during 2nd Pass I got some bit-errors at address around 6.8GB; then I stopped that test
-- Ran memtest again for 7 passes on one set of RAM (2 x 2GB) and later again on other set of RAM (2x2GB) for 8 passes (in both tests I used different set of motherboard slots to verify motherboard also. Attaching screen-shots of memtest
-- Then ran memtest again on full 8GB of RAM for 8+ passes and no errors. Screen-shot attached.
-- Now first time boot after full 8GB RAM memtest gave me BSOD; attaching log/minidump.

I am really confused now, I am assuming that due to that inconsistent RAM errors (which I saw once in one memtest when full 4 slots on motherboard were populated and RAM is also have strict-timings) this crash happens sometimes ?

Please I really need your help. My RAM specs says 1.6V which I set manually in BIOS already. Do I have to increase voltage ? If yes then how much increase ? Also why 2nd RAM test with full 8GB RAM was fine even after 8-passes in memtest.

Waiting for your response.

Thanks in advance.

 

[mgorman87]

The issue could be with your CPU and memory speeds. There are issues with AM3 processors and RAM running at 1600mhz.

Here is a good article explaining the issue: VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS


Try lowering your RAM speeds to 1333mhz and see if the problem continues or not.


I would like you to run a system file check to make sure there are no corrupted Windows files
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 26 12:11:05.425 2011 (UTC - 4:00)
System Uptime: 0 days 3:00:15.892
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+8490b )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  sidebar.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k+8490b
BiosReleaseDate = 04/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[fslateef]

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]

Are you running two different brands/types of memory?

 

[fslateef]

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]

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]

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

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[fslateef]

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]

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

 

[fslateef]

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

 

[mgorman87]

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

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[fslateef]

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.