BSOD Windows 7 64bit New Build

[adams756]

Hi,

I've just built a new system only a few days ago. Everything was running fine until a day after building, having installed the usual software etc it began BSOD'ing and restarting.

I'm having problems finding out what the problem is, I think it may be the memory but I'm unsure still. The motherboard is a MSI 770-C45. I'll upload the minidump.

If you need anything else, just let me know, any help would be greatly appreciated.

Thanks in advance,

Adam

 

[Jonathan_King]

Welcome to SF!

The only thing I notice out of order on your system is Avast. It is not uncommon for Avast to cause BSODs, so please remove it with this tool: http://files.avast.com/files/eng/aswclear5.exe

Replace it with MSE: http://www.microsoft.com/security_essentials

If the BSODs persist, enable driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Wait for a few BSODs, then follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 03:04:47.173 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:09.921
BugCheck 19, {3, fffffa800395a3e0, fffffa800395a3a0, fffffa800395a3e0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[adams756]

Ah I would have never though it could be avast.

I'll get rid of it using that tool and see how it goes.

Thank you for quick reply, its greatly appreciated, will keep you posted!

 

[adams756]

Update

Just wanted to give you an update on my situation.

I have removed Avast using the tool you suggested and installed MSE.

It was looking good then after a few restarts and some hours later I was faced with another BSOD.

That night I left memtest running for several hours just incase the error might be in the memory. The system is only new so the memory could have been damaged in transit/build. However it all shows up in the BIOS and Windows so I'm unsure.

I took a picture of the results the morning after which actually had one error. Could this mean that the memory is faulty? I can run more tests if need be, for example one of the two sticks at a time and in different slots etc if need be. I'm not brilliant at this sort of stuff so any advice would be really great!

Meanwhile I've followed your other instructions and enabled driver verifier. I'll wait until a few BSOD have happened before I continue with the posting instructions.

Please find attached an image containing the results of memtest after several hours and several passes. Sorry I dont know the exact amount of passes, it was approximately 10 hours.

http://img340.imageshack.us/img340/7352/imag0214l.jpg

Thanks in advance for any help!

Adam

 

[Jonathan_King]

Memtest was on pass 9, 10.5 hours, according to the image.

Could this be a heat problem? Download Speedfan and find out.

Otherwise, follow Part 3 of this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[adams756]

I've downloaded speedfan and left it running in the background while the computer has been in use.

So far, about an hour in, everything seems fine. This is to my knowledge anyway, here is a screenshot just incase.

http://img94.imageshack.us/img94/553/speedfanresults.jpg


I also, just to cover everything, have followed the instructions from your first post. I enabled driver verifier, allowed a few BSOD to occur and then used the .exe and saved a performance check. Please find those attached.

The system is Windows 7 64 bit, its the original install, brand new hard drive and it hasnt been reinstalled since, Its an OEM Home Premium copy, Hardware is 5 days old, along with the OS.

I will begin testing the individual sticks of RAM and each of the motherboard RAM slots tonight as you pointed out to in your previous post.

I hope this is of some use and hopefully points towards the cause! I appreciate all your help with this as I'd be very lost otherwise!

Thanks again,

Adam


EDIT - Just to let you know, the BSOD's only come up as I power on the system, it never seems to lock up or just crash. Its always as the system is powering up it will have trouble and BS. It then gives me the option once restarted to try system restore or detect a fix, which I have done several times but to no avail. Hope this helps!

- I've also added the minidump from today.

 

[Jonathan_King]

Hmm...the only new dump in the folder was not verifier-enabled.

I see that your system is set to create a Full dump:

Event[101]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2010-09-16T20:51:07.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: WoodwardPC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffffa8039bb4977, 0x0000000000000000, 0xfffff88002ac1ea7, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 091610-17050-01.

Make sure your system is configured to create a minidump:

View attachment 98205

Also, go through the Driver Verifier instructions again, and make sure it didn't get disabled.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 16 15:43:28.515 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:11.294
BugCheck 50, {fffffa8039bb4977, 0, fffff88002ac1ea7, 2}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[adams756]

ah, sorry about that, will do that now.

thanks

 

[adams756]

solved!

Just wanted to update this thread as i solved the problem. I reinstalled windows and found the problem persisted. So I decided it must be the memory as it returned errors previously and sent it back. The store also found it had errors and sent me some new memory. After installing and running it for a few days its been great!


Thanks for all the help,

Adam

 

[Jonathan_King]

Thanks for the report adams! We appreciate it.