Random BSODs every 24-36 hours on new computer

[ephi]

I just got a custom built computer, and I'm getting random BSODs every day or so. They seem have different codes. I tried looking at the dumps in windbg but was not able to understand what the problem is.
I also ran an overnight memtest which was fine.
Attached are the dump files.
Thanks in advance!!

 

[axe0]

Hi ephi,

Welcome to the 7forums.

For a full analyse, Please read BSOD Posting Instructions

Please remove ESET using the uninstall instructions.
ESET has been flagged multiple times.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

 

[ephi]

Thank you very much for the quick reply!

What did you mean by "For a full analyse, Please read BSOD Posting Instructions" ? I thought I followed the instructions by uploading the dump files.. what else do I need to do for a full analysis?

In the meantime I uninstalled ESET and am running the hard drive tests that you suggested.

Thanks, Ephi

 

[axe0]

Thank you very much for the quick reply!

What did you mean by "For a full analyse, Please read BSOD Posting Instructions" ? I thought I followed the instructions by uploading the dump files.. what else do I need to do for a full analysis?

In the meantime I uninstalled ESET and am running the hard drive tests that you suggested.

Thanks, Ephi

There are only dump files, it is prefered to read the instructions.

 

[ephi]

Still don't understand

Hi, I'm sorry, I'm feeling very stupid but I've gone through the instructions a number of times and I don't understand what I'm missing.
There are 9 steps in the instructions which I followed one by one.. I ran the 'DM Log Collector' and uploaded the file which was created by it to this thread.
What am I missing?
Thanks, Ephi

 

[Pauly]

Your upload is incomplete there are many files missing, try running the tool again and wait for several minutes for all the files to be generated in the background before uploading, have a look at someone elses upload and you will see what should be there

 

[ephi]

thanks and update

Thanks for explaining!
I'm pretty sure the tool completed the first time before I uploaded the file, but I may have missed something. In any case I reran and indeed see the missing files now!
Thank you very much for pointing me in the right direction..

Attached is the new file.

In the meantime - I've uninstalled ESET like suggested and tried running the HDD tests.
The short diagnostic self test seems to get stuck at 90% and then prints FAIL but I don't see any other information. Does this for sure mean that there is a problem?
The short generic test PASSed fine.
I tried running the long generic test overnight but by the morning the computer had restarted due to another BSOD (despite the fact that ESET was already uninstalled..). I don't know if the BSOD happened before or after the long test finished.

 

[axe0]

1. There are problems with the Windows Anti-Malware protection system.

2. The NTFS system was marked activily when ESET was still installed.

3. The latest crash was a 0x1a meaning memory problems.
___________________________________________________

1.
Please try the following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

2.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html



3.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

[ephi]

Update

Thanks,

1. System File Check finished with "Windows Resource Protection did not find any integrity violation" both before and after reboot.

2.
SeaTools on the HDD - the Short DST goes to 90% and then hangs for a bit and then fails. However the Short Generic and Long Generic tests passed.
See attached log.

Chkdsk on both HDD and SSD - pass without errors (See attached event logs in zip file)

So how should I consider the failure of the Seatools Short DST test? Does it mean that there is indeed a problem despite that the other tests passed? How can I check into this further?

3. Memtest ran for 8 passess with no errors. See attached log.

 

[axe0]

It means that the hard drive is likely failing.

What command(s) did you use with chkdsk?

 

[ephi]

I ran through the Windows UI and checked both "Automatically fix file system errors" and "Scan for and attempt recovery of bad sectors".

Is there any way to verify that the hard disk indeed has a problem? This is a brand new hard disk (the entire rig is brand new)

 

[axe0]

Please reboot your system and try the short DST again.
Please open an admin command prompt and enter "chkdsk c: /r" (without quotes) (assuming C: is the windows partition letter)
Reboot if asked

 

[ephi]

Thanks,

1. The Short DST fails consistently also after reboot, with the same behavior (hangs at 90% and then fails)

2. "chkdsk /r" like you suggested reports no problems

So what next? I am continuing to get random BSODs, just got another one this morning.

Thanks, Ephi

 

[axe0]

Disconnect the hard drive and see if you get crashes