Got a RAM. Windows just freezes on boot.

rgsilent · 12 May 2012

Firstly, my system specs are on my profile :)

I got a new ram stick for my PC.

Here's the link from where I bought it:Flipkart: Corsair DDR3 4 GB (1 x 4 GB) PC RAM (CMV4GX3M1A1333C9): Ram

So I put it in and booted up the computer. Worked fine till the welcome screen of windows7. I then logged in and after the startup processes were loaded, I got a blue screen of death. Got it couple more times when I booted it up. After that the screen never gave any BSOD. Just kept freezine. This kept happening again and again. I thought it might be because my older corsair ram sticks could be conflicting with this one. So I booted it with the new stick only. Same freezing of screen. So it definitely isn't conflicting RAMs.

I decided to see if the problem is with the stick or some driver issue. So I booted into Ubuntu and am currently typing through it. Been using it since a couple of hours and is working fine. So this definitely is a windows issue with the RAM stick as windows works fine if I remove the new stick.

Also, windows works fine in safe mode with the new stick too. Any idea what is the issue here? I'll be posting the minidumps of the BSOD in a short while.

Right now I'm installing virtual box on ubuntu and installing win7 on it to see if the problem can be simulated or not.

Any help will be appreciated. :)

Regards,
rgsilent

usasma · 12 May 2012

Please provide this info and we'll see if we can get to the bottom of this quickly: https://www.sevenforums.com/crashes-d...tructions.html

FWIW - if the system works without problem in Safe Mode and doesn't work properly in normal mode - then it's most likely a 3rd party program/driver causing your issues. Try a clean boot to see if you can figure out the 3rd party problem that way: How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

rgsilent · 12 May 2012

Here you go. Attaching the system report and the BSOD files generated by the exe provided in the thread.

usasma · 12 May 2012

The reports aren't complete. It looks as if you didn't run the program until it finished. Please run it again and leave it alone for a while (15 minutes should do it). It should let you know when it's done.

Corruption in the memory dumps.

First, please uninstall the XBox controller software and remove the device from the system. That has been a common problem recently.

Next, if that doesn't fix it - run the hardware diagnostics here: Initial Hardware Diagnostics
If they pass, follow on with the diagnostics here: Additional Hardware Diagnostics
Post back with the results of the testing (if you encounter any failures, post back immediately).

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
snapman.sys     Sat Apr 10 05:16:30 2010 (4BC041EE)
Sy              Mon Jul 13 19:19:54 2009 (4A5BC11A)
Sy              Mon Jul 13 20:00:13 2009 (4A5BCA8D)
Sy              Mon Jul 13 19:38:47 2009 (4A5BC587)
Syÿtem          Mon Jul 13 19:19:47 2009 (4A5BC113)
VBoxUSBMon.sys  Mon Dec 19 07:43:53 2011 (4EEF3189)
VBoxDrv.sys     Mon Dec 19 07:43:53 2011 (4EEF3189)
VBoxNetAdp.sys  Mon Dec 19 07:43:53 2011 (4EEF3189)
SyDtem          Tue Jan 17 07:45:46 2012 (4F156D7A)
mcdbus.sys      Tue Feb 24 05:34:07 2009 (49A3CD1F)
VBoxNetFlt.sys  Mon Dec 19 07:43:51 2011 (4EEF3187)
KMWDFILTER.sys  Wed Apr 29 02:20:48 2009 (49F7F1C0)
Syÿtem          Thu Aug 13 18:10:17 2009 (4A848F49)
Sy              Mon Jul 13 19:23:50 2009 (4A5BC206)
idmwfp.sys      Thu Jan 26 08:47:36 2012 (4F215978)
Sy              Wed Oct 07 04:28:44 2009 (4ACC513C)
Systemmoot      Mon Jul 13 19:19:47 2009 (4A5BC113)
duLp_asapiRsys  Mon Jul 13 19:19:47 2009 (4A5BC113)
LVPr2M64.sys    Wed Oct 07 04:26:50 2009 (4ACC50CA)
nvlddmkm.sys    Thu Feb 09 21:02:58 2012 (4F347AD2)
nvBridge.kmd    Fri May 20 23:58:23 2011 (4DD7385F)
Sy              Mon Mar 22 05:57:14 2010 (4BA73EFA)
SyDtemÿoot      Mon May 18 08:17:04 2009 (4A1151C0)
Syltem          Mon Jul 13 19:40:16 2009 (4A5BC5E0)
Rt64win7.sys    Mon Mar 22 05:57:14 2010 (4BA73EFA)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
nvhda64v.sys    Tue Jan 17 07:45:46 2012 (4F156D7A)
xusb21.sys      Thu Aug 13 18:10:17 2009 (4A848F49)
Syÿtemÿoot      Wed Oct 07 04:28:44 2009 (4ACC513C)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051112-18330-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri May 11 05:46:20.657 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:20.156
Probably caused by : memory_corruption ( nt!MmCheckCachedPageStates+41f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  pokki.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MmCheckCachedPageStates+41f
Bugcheck code 00000050
Arguments fffff800`0b88cbf0 00000000`00000000 fffff800`032e9e9f 00000000`00000002
BiosVersion = F6
BiosReleaseDate = 05/27/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051112-24944-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri May 11 05:44:15.540 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:26.038
Probably caused by : win32k.sys ( win32k!BuildVertexList+118 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!BuildVertexList+118
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`002128cc fffff880`038c6d30 00000000`00000000
BiosVersion = F6
BiosReleaseDate = 05/27/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

rgsilent · 12 May 2012

So I installed win7 on another disc. The stick causing the issues was plugged in all the while during the installation process. Then windows booted up and didn't freeze. I started browsing a little and then it restarted. All this while the only thing I had installed was nvidia drivers from my gpu. The xbox controller was plugged in but the software wasn't installed.

Anyway, will post the reports again when they complete. Thanks for your help usama!

rgsilent · 12 May 2012

Report attached

usasma · 13 May 2012

EasyTether device is disabled. For testing purposes please uninstall the software and remove the device from your system. Feel free to reinstall it once the system is stable again.

Volume dirty bit is set on your hard drive. There's only 2 ways to fix this error message:
- run chkdsk /r /f
- format the hard drive

Please run this:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
FWIW - I know that the /F is supposed to be redundant, but I prefer to have it run anyway.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Then, if this error message recurs, try the hard drive diagnostic located here: Hard Drive Diagnostic Procedure

SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?
Also, check out this troubleshooting link from Microsoft: Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2

I have had limited success in installing updates/Service Packs when using a "clean boot". I suspect that I'm just bypassing the problem - and that it can come back to bite me in the butt later on.

Older versions of Samsung Kies will cause BSOD's. Please ensure that you have the latest version available from the Samsung website.

XBox software and the device must be removed (at least for testing purposes). There have been known BSOD problems with this software over the last month or two. Feel free to reinstall it after the system is stable again.

Memory dumps are still corrupted, and there's no record of them in MSINFO32. As such I'd strongly suggest these free diagnostics (starting with the hard drive diagnostic): Hardware Diagnostics
Please post back with the results (and post back immediately if you encounter any failures).

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
snapman.sys     Sat Apr 10 05:16:30 2010 (4BC041EE)
Sy              Mon Jul 13 19:19:54 2009 (4A5BC11A)
Sy              Mon Jul 13 20:00:13 2009 (4A5BCA8D)
Sy              Mon Jul 13 19:38:47 2009 (4A5BC587)
Syÿtem          Mon Jul 13 19:19:47 2009 (4A5BC113)
VBoxUSBMon.sys  Mon Dec 19 07:43:53 2011 (4EEF3189)
VBoxDrv.sys     Mon Dec 19 07:43:53 2011 (4EEF3189)
VBoxNetAdp.sys  Mon Dec 19 07:43:53 2011 (4EEF3189)
SyDtem          Tue Jan 17 07:45:46 2012 (4F156D7A)
mcdbus.sys      Tue Feb 24 05:34:07 2009 (49A3CD1F)
VBoxNetFlt.sys  Mon Dec 19 07:43:51 2011 (4EEF3187)
KMWDFILTER.sys  Wed Apr 29 02:20:48 2009 (49F7F1C0)
Syÿtem          Thu Aug 13 18:10:17 2009 (4A848F49)
Sy              Mon Jul 13 19:23:50 2009 (4A5BC206)
idmwfp.sys      Thu Jan 26 08:47:36 2012 (4F215978)
Sy              Wed Oct 07 04:28:44 2009 (4ACC513C)
Systemmoot      Mon Jul 13 19:19:47 2009 (4A5BC113)
duLp_asapiRsys  Mon Jul 13 19:19:47 2009 (4A5BC113)
LVPr2M64.sys    Wed Oct 07 04:26:50 2009 (4ACC50CA)
nvlddmkm.sys    Thu Feb 09 21:02:58 2012 (4F347AD2)
nvBridge.kmd    Fri May 20 23:58:23 2011 (4DD7385F)
Sy              Mon Mar 22 05:57:14 2010 (4BA73EFA)
SyDtemÿoot      Mon May 18 08:17:04 2009 (4A1151C0)
Syltem          Mon Jul 13 19:40:16 2009 (4A5BC5E0)
Rt64win7.sys    Mon Mar 22 05:57:14 2010 (4BA73EFA)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
nvhda64v.sys    Tue Jan 17 07:45:46 2012 (4F156D7A)
xusb21.sys      Thu Aug 13 18:10:17 2009 (4A848F49)
Syÿtemÿoot      Wed Oct 07 04:28:44 2009 (4ACC513C)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051112-18330-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri May 11 05:46:20.657 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:20.156
Probably caused by : memory_corruption ( nt!MmCheckCachedPageStates+41f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  pokki.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MmCheckCachedPageStates+41f
Bugcheck code 00000050
Arguments fffff800`0b88cbf0 00000000`00000000 fffff800`032e9e9f 00000000`00000002
BiosVersion = F6
BiosReleaseDate = 05/27/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051112-24944-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri May 11 05:44:15.540 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:26.038
Probably caused by : win32k.sys ( win32k!BuildVertexList+118 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!BuildVertexList+118
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`002128cc fffff880`038c6d30 00000000`00000000
BiosVersion = F6
BiosReleaseDate = 05/27/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Maguscreed · 13 May 2012

You really should just rn memtest86 on it for a fee passes

usasma · 14 May 2012

Maguscreed said:

You really should just rn memtest86 on it for a fee passes

Great catch! Thanks Maguscreed!

Kaktussoft · 14 May 2012

Probably caused by : memory_corruption
=>run memtest86 or "windows memory diagnostics" Memory Diagnostics Tool

Your new memory is almost sure faulty! Test with only that memory inserted to prove it's faulty. Try another memoryslot as well, maybe slot is faulty