BSOD Randomly

[imtiax]

I just built a new computer and it's been having BSOD randomly. Usually one after the first cold boot of the day.

Is Windows 7 . . . - x86 (32-bit) or x64 ? 64BIT - the original installed OS on the system? YES - an OEM or full retail version? RETAIL - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? LESS THAN 1WEEK - What is the age of OS installation (have you re-installed the OS?) LESS THAN 1 WEEK

I ran MEMTESt and had an error, but the 2nd time I let it run over night and no errors. So I can not tell if my ram is faulty. Here is a thread that I posted on TomsHardWare Scared of my MemTest86 Results - Memory - Motherboards-Memory

PC Specs:

Windows 7 Home Premium 64 Bit
8GB CORSAIR XMS3 1333MHZ DDR3
750W Corsair TX-2
640GB WD HDD
Motherboard ASUSTeK Computer Inc. -Support- Drivers and Download P5G41T-M LX PLUS

Anti Virus - ESET Smart Secuirity 5
Malware Protection - Malware Bytes

When the BSOD Occurs I can not read the Error Code because it goes away really fast. My computer auto reboots after around 4 seconds of a BSOD.

 

[soho1]

As your error is related to PCI have you started by updating the bios for your motherboard and video?

 

[imtiax]

Yes I have updated the bios yesterday.

Not sure about that Video BIOS date.

 

[imtiax]

Here is a list of all my BSOD's since day one.

Note: All of them happen right after a cold boot, maybe 5 - 10 min after the cold boot (First boot of the day usually after I get home from school)

 

[imtiax]

Can someone please tell me what is wrong?

 

[writhziden]

If you receive an error with Memtest86+ at any time, it is one error too many. Make sure your RAM is compatible with your system; that includes being compatible with the motherboard as well as with the CPU. At a quick glance, it appears it should be, but double check. If it is compatible, RMA it and try to get a replacement for the RAM kit.

If you want to determine which RAM is responsible, proceed through part 3 of Memtest86+, and during the steps in that part, Avoid Static Damage to Your PC.

If you are comfortable adjusting RAM settings in the BIOS, we could also try this to see if the problem can be solved with some tweaks. Let us know if you are interested.

 

[imtiax]

I only received that error the FIRST time I ran MemTest.

A few hours after that FIRST time I ran it again and left it on over night for like 7 rounds.

No Errors.

Last night I ran Microsoft Memory Diagnostics thing and still NO Errors.

I'm assuming that First time was a glitch?

 

[writhziden]

Probably was not a glitch. Could have been due to cold startup issues which can be difficult to track down, but if they point to memory, chances are that is what is causing the cold startup problem.

Anytime you get even one error with Memtest86+, that is one error too many. Also, sometimes you have to run Memtest86+ multiple times to catch any errors, and if you do catch an error, it points to memory problems regardless of how often it has passed before.

As I said, there are setting in the BIOS that can be adjusted to fix such problem in some instances. Often, a better course of action is to RMA the RAM.

 

[imtiax]

Okay, I will RMA. Hopefully the new ram will not have errors.

 

[imtiax]

As your error is related to PCI have you started by updating the bios for your motherboard and video?

What about PCI?

Can you go into more detail?

 

[writhziden]

Also, at some point you should make sure all updates are installed for Windows. I see Service Pack 1 has not yet been installed.

Not sure where the PCI analysis came from. All .dmp reports point to memory_corruption as the cause of the crashes which supports the tests that have been run and errors/crashes found due to the bad module. I too would be interested in where the PCI errors were determined.

 

[imtiax]

Also, at some point you should make sure all updates are installed for Windows. I see Service Pack 1 has not yet been installed.

Not sure where the PCI analysis came from. All .dmp reports point to memory_corruption as the cause of the crashes which supports the tests that have been run and errors/crashes found due to the bad module. I too would be interested in where the PCI errors were determined.

Thank you! For confirming the memory error. I was also confused as to why that guy said PCI error. I was wondering if it was a motherboard issue.

But now I know for sure it's a memory error.

Once again thank you very much.

 

[writhziden]

No problem. One other thing, you have a possible outdated driver:

RTL8187	fffff880`020a1000	fffff880`0210d000	Thu Jun 26 19:40:34 2008 (48644512)	00062063		RTL8187.sys

RTL8187.sys

Wanted to let you know in case you have any network related problems in the future regarding your wireless USB connection. Your USB network adapter may be outdated and could potentially cause problems in the future.

 

[imtiax]

Actually that USB Adapter driver is upto date. That date you posted is the latest version of that driver

 

[writhziden]

I was afraid of that. I would recommend replacing the device. We see a lot of blue screen crashes on this forum related to USB wireless, and it is almost 100% certain to cause issues if the drivers are pre-Windows 7.

 

[imtiax]

Update: I updated the bios 2 days ago and have had none of those cold boot up BSOD's.

Any way to guarantee their gone for good?

 

[writhziden]

The best way is to run for a few weeks (doing your normal routine) and see whether the system is stable.

 

[imtiax]

I have 16 days before the 30day rma period is gone.

 

[writhziden]

Ah, I see your dilemma. You were getting a blue screen crash basically on a daily basis before, so see how it runs for a few days.

 

[imtiax]

Okay...I'll run memtest86 on a cold boot tomorrow before I leave for school. I'll post results after I get back home about 8 hours later.