BleepingComputer.com: Frequent BSOD

Hey peeps. So computer is clean from any possible threats. Still have issues with BSOD and would like to get to the hardware bottom of this. If there is faulty hardware I will need to contact OverClockers and have parts replaced etc...

Here is the BSOD logs from teh previous thread.

==================================================
Dump File : 021111-29047-01.dmp
Crash Time : 11-Feb-11 4:02:18 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`03354728
Parameter 3 : fffff880`03353f90
Parameter 4 : fffff880`012af1f2
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+961f2
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021111-29047-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,224
==================================================

==================================================
Dump File : 021111-30139-01.dmp
Crash Time : 11-Feb-11 3:59:08 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a0`10406178
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`05f2e848
Parameter 4 : 00000000`00000002
Caused By Driver : hal.dll
Caused By Address : hal.dll+7b7f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021111-30139-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,224
==================================================

==================================================
Dump File : 020911-28953-01.dmp
Crash Time : 09-Feb-11 2:31:33 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`001aefc5
Parameter 3 : 00000000`00000005
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\020911-28953-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 265,528
==================================================

==================================================
Dump File : 020911-30435-01.dmp
Crash Time : 09-Feb-11 1:31:54 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`031a7d99
Parameter 3 : fffff880`0abfc340
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\020911-30435-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,224
==================================================

==================================================
Dump File : 020811-33290-01.dmp
Crash Time : 08-Feb-11 6:43:39 PM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x000000be
Parameter 1 : fffff8a0`001489a8
Parameter 2 : 80000001`aa075101
Parameter 3 : fffff880`0473f6c0
Parameter 4 : 00000000`0000000b
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\020811-33290-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,224
==================================================

==================================================
Dump File : 020711-31668-01.dmp
Crash Time : 07-Feb-11 12:13:32 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`00002080
Parameter 4 : 00002082`01004100
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\020711-31668-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,224
==================================================

==================================================
Dump File : 020611-30357-01.dmp
Crash Time : 06-Feb-11 6:56:41 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`056e2817
Parameter 3 : fffff880`08fcc900
Parameter 4 : 00000000`00000000
Caused By Driver : atikmdag.sys
Caused By Address : atikmdag.sys+90817
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\020611-30357-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,224
==================================================

Whats my next step

I can see from your topic here: http://www.bleepingcomputer.com/forums/topic378951.html/page__p__2130251__fromsearch__1#entry2130251 that a very serious number of trojans has been detected by Eset scan.
I have a reason to believe, that much more is going on on your computer.

With the information you have provided I believe you will need help from the malware removal team. I would like you to start a new thread and post a DDS log HERE and include a link to this thread. Please make sure that you read the information about getting started before you start your thread.

It would be helpful if you post a note here once you have completed the steps in the guide and have started your topic in malware removal. Good luck and be patient. Help is on the way!

I already got cleaned as this thread shows.

The trojans have all been cleaned and were not the cause of BSOD, however I understand its a necessary step to eliminate potential problems.

What do I do with my BSOD logs and do I need to get any more in depth logs for teh forums consideration?

Thanx

I will check back in next 24 hours, bed beckons.

This post has been edited by AnaLoGMunKy: 11 February 2011 - 10:33 PM

I saw your thread, but I suspect, there is more there. That's why I directed you to more advanced forum.

Ok, is it possible to keep this thread open so I can come back to it after getting the DDS logs

Here is the thread with the DDS log

This post has been edited by AnaLoGMunKy: 12 February 2011 - 07:45 AM

Hi AnaLoGMunky. With rare exception, threads are never closed.

This one will be here for you when you are done in the Virus, Trojan, Spyware, and Malware Removal Logs forum.

How ever. At this point you should only take instructions for a member of the Malware Removal Team. Follow all their instructions to the letter and make no other changes, hardware or software, to the machine in question unless instructed to do so by the Malware Team member working with you.

This post has been edited by ThunderZ: 12 February 2011 - 08:59 AM

Now that your log is properly posted, you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a Malware Removal Team member, nor should you continue to ask for help elsewhere. Doing so can result in system changes which may not show it the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the Malware Removal Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the Malware Removal Team members are very busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the Malware Removal Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another MRL Team member is already assisting you and not open the thread to respond.

To avoid confusion, I am closing this topic.
After the malware team is done we can reopen this if needed.

Topic reopened as no malware is involved. Malware removal topic here

A. If you have more than one RAM module installed, try starting/running computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

Hi

I have 3 2GB sticks so I will pop one at a time in and run memtest86+

How do I get memtest to run automatically? I couldnt figure it out last time.

This is not what I suggested...

Quote

Run the computer on one stick for a day, or so and see, if any BSOD will occur.
If not, switch to next stick and so on....

I apologize for my lack of communication, I have had a plethora of events and headaches of different reasons.

I now have a Crucial C300 64GB SSD and I have not been using my WD 540GB HDD. Windows crashed on a fresh install when the HDD was plugged in as a slave so I took it out completely and just running windows with steam, DOW2 and Crysis 2 (a couple of those events I was talking about) and using the web browser Opera. SO apart from these programs and the MB drivers, video card drivers etc. I have not installed anything else. Windows has BSOD again.

I am right now following your instruction and have removed 2 sticks of RAM and will be running for at least day with each in. I also shed a tear as Im pretty close to completing Crysis 2 and wont be running this on 2GB of RAM but hey, priorities right?

I will post back with more info soon.

This post has been edited by AnaLoGMunKy: 30 March 2011 - 02:44 PM

I'll be around

Actually... crysis 2 DOES run... woohoo!

Good news