BSOD/Resetting when adding 2nd stick of RAM or graphics card.

[jd1980]

-Windows 7 Pro x64
-Brand new install from Microsoft.com
-Full retail version

-All hardware is brand new
-Reinstalled the OS today.

Brand new build - I can get into Windows with only 1 stick of RAM installed and no Graphics Card (other than the on-board video card).
-Windows is updated and verified.
-Installed drivers for LAN and USB3.0.
-If I add the second stick of RAM or try and add (1 of 2) graphics cards then I get a quick BSOD flash as "Starting Windows" begins to complete the windows logo. Removing either of these items allows me to get back in with no problems.

Looking forward to hearing from you guys about this. I'm completely new to building and excited about trying this puppy out soon.

Thanks in advance!

 

[zigzag3143]

-Windows 7 Pro x64
-Brand new install from Microsoft.com
-Full retail version

-All hardware is brand new
-Reinstalled the OS today.

Brand new build - I can get into Windows with only 1 stick of RAM installed and no Graphics Card (other than the on-board video card).
-Windows is updated and verified.
-Installed drivers for LAN and USB3.0.
-If I add the second stick of RAM or try and add (1 of 2) graphics cards then I get a quick BSOD flash as "Starting Windows" begins to complete the windows logo. Removing either of these items allows me to get back in with no problems.

Looking forward to hearing from you guys about this. I'm completely new to building and excited about trying this puppy out soon.

Thanks in advance!

No DMP files included in upload. Please try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[Maguscreed]

Is this the correct motherboard?
ASUSTeK Computer Inc. - Motherboards- ASUS M5A88-V EVO
if so there are bios updates the first for memory issues and the second addresses a number of other problems. . If I got the wrong one sorry asus's website was being a bit strange with me today.

 

[jd1980]

Is this the correct motherboard?
ASUSTeK Computer Inc. - Motherboards- ASUS M5A88-V EVO
if so there are bios updates the first for memory issues and the second addresses a number of other problems. . If I got the wrong one sorry asus's website was being a bit strange with me today.

Yes that's the one, do I need to download each individually? Also I was having a similar issue with another brand new motherboard of a different brand.

 

[Maguscreed]

motherboard bios and ssd firmware are two things I suggest looking at with any new build.
It's also possible one of those memory sticks is bad, you haven't said anything about swapping them around.
I would update the bios specifically because the first fix is memory related.

...and bios updates are inclusive, you should only need the most recent one.

 

[jd1980]

I've swapped the ram and tried it in different slots, I also tried a completely different set of RAM and I could still only get it to run with 1.

I am pretty confused because I have tried 2 different mobos, 2 sets of RAM, 2 PSU's, 2 graphics cards. The only thing I haven't tried differently is the processor, CPU cooler.

-I will upload the DUMP file when I get home.
-I will also update the BIOS when I get home.

Is this the correct update?
M5A88-V EVO BIOS 0707 date: 2011.08.18 update

 

[jd1980]

looks like the BIOS was already updated, but I ran it again.

 

[jd1980]

-Windows 7 Pro x64
-Brand new install from Microsoft.com
-Full retail version

-All hardware is brand new
-Reinstalled the OS today.

Brand new build - I can get into Windows with only 1 stick of RAM installed and no Graphics Card (other than the on-board video card).
-Windows is updated and verified.
-Installed drivers for LAN and USB3.0.
-If I add the second stick of RAM or try and add (1 of 2) graphics cards then I get a quick BSOD flash as "Starting Windows" begins to complete the windows logo. Removing either of these items allows me to get back in with no problems.

Looking forward to hearing from you guys about this. I'm completely new to building and excited about trying this puppy out soon.

Thanks in advance!

No DMP files included in upload. Please try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

I've followed the directions and double checked, I'm in SAFE mode now and the Minidump folder is not there. I also purposely made my computer crash.

 

[jd1980]

Delete - last comment

 

[jd1980]

I'm still in the same boat and unable to find the minidump file even after a crash. Anymore info on this?

 

[zigzag3143]

I'm still in the same boat and unable to find the minidump file even after a crash. Anymore info on this?

Several things can prevent a DMP file from being written among them no page file, page file on a different HD, a system configuration error, malware.

Have you tried searching for *.DMP?

Might also want to look in C:\windows for a file called MEMORY.DMP

 

[jd1980]

Here are some current dump files, I ended up moving to an old MOBO, CPU, and Ram for now.

 

[zigzag3143]

Here are some current dump files, I ended up moving to an old MOBO, CPU, and Ram for now.

These report that the crashes were related to SysInternals Process Explorer driver. I would remove it at least to test.

 

[jd1980]

Just read into something a bit, I'm using:

Microsoft Windows 7 with Service Pack 1 Debug/Checked Build 32-bit (English)

apparently debug builds throw errors on purpose if anything happens. As opposed to retail builds that just move past errors.

Operating System: Debug Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: G31M-S2L
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz (2 CPUs), ~2.0GHz
Memory: 4096MB RAM
Available OS Memory: 4094MB RAM
Page File: 1323MB used, 6865MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

 

[zigzag3143]

Just read into something a bit, I'm using:

Microsoft Windows 7 with Service Pack 1 Debug/Checked Build 32-bit (English)

apparently debug builds throw errors on purpose if anything happens. As opposed to retail builds that just move past errors.

Operating System: Debug Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: G31M-S2L
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz (2 CPUs), ~2.0GHz
Memory: 4096MB RAM
Available OS Memory: 4094MB RAM
Page File: 1323MB used, 6865MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

Its the anything that happens that is the true cause but you are right

 

[jd1980]

I wanted to update this forum so that it may help others out in the future. Though I'm not absolutely certain what the issue was. Here are some problems that were found. Keep in mind that I am a brand new builder and my knowledge of the process was limited to what I read in the manuals and online.

-1st BIG mistake - Received a Debug/Checked version of Windows 7 Pro. This caused a crash anytime it encountered a problem. Lesson learned - Debug/Checked versions are for anyone seeking out software/hardware issues that normally would go unnoticed on retail versions. Not for the typical user.

-2nd beginner mistake - As soon as I saw a problem, I started swapping out components. One of those parts was the HDD. Apparently this is bad. Lesson learned - HDD's stay with the motherboard.

-Bios setting - Dimms were all set to IDE. I was directed to change that to AHCI. Lesson learned - it may or may not have helped. Read more about these acronyms if attempting a build.

-4th mistake - I may have pulled the video card and some RAM when I first had issues. Lesson learned - Ensure all hardward is connected before trying to load OS.

Some other thoughts:
-Forums are an excellent tool for getting answers, use them.
-Web chat is another amazing tool - this ended up solving all my issues when a gentleman that was working with me realized that I probably made all kinds of silly mistakes and walked me through it step by step.
-Verify combatibility for CPU/Mobo, RAM/Mobo through each manufactures website. The mobo I used had a Qualified Vendor List to show which processors and RAM were fully compatible.

Good luck on those builds!