4 BSODs in a week - help?

Question

Ithz 0 Newbie Poster

12 Years Ago

Hi guys, I've been getting sporadic bsods without any identifiable cause, and would like to know if anyone could help me identify the problem. It used to hang sometimes while playing games, which I attributed to the games themselves, but recently bsods have been happening while the computer's idle.

I'm on a custom-built pc, which had a virus attack quite a few months ago which I resolved by doing a fresh install.

I'm uploading the minidump logs with this thread - in the zip file "minidump"; the txt file "bsod" is a copy-paste of what i see in the minidump viewer program. (I've downloaded a minidump viewer and can view them but I can't seem to post them without messing this thread up)

Considering the fact that it's a different 'crash address' each time, could this be a virus attack again? I've scanned with avg, malwarebytes and avast and they haven't found anything except for some tracking cookies - serving-sys and atdmt (found by avg) which have been "healed" or "moved to virus vault".

I've run chkdsk, which hasn't turned up with any errors.

Would like some help asap.

Cheers!

display windows-vista-7-8

bsod.txt (7.51 KB)

==================================================

Dump File         : 081912-48297-01.dmp

Crash Time        : 8/19/2012 10:58:20 PM

Bug Check String  : KERNEL_DATA_INPAGE_ERROR

Bug Check Code    : 0x0000007a

Parameter 1       : fffff6fc`40021d08

Parameter 2       : ffffffff`c000000e

Parameter 3       : 00000000`63277860

Parameter 4       : fffff880`043a1784

Caused By Driver  : intelppm.sys

Caused By Address : intelppm.sys+8784

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ntoskrnl.exe+66580

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\081912-48297-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7600

Dump File Size    : 305,312

==================================================



==================================================

Dump File         : 081712-31184-01.dmp

Crash Time        : 8/17/2012 11:38:54 PM

Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug Check Code    : 0x1000007e

Parameter 1       : ffffffff`c0000005

Parameter 2       : fffff880`00c8f008

Parameter 3       : fffff880`053e89a8

Parameter 4       : fffff880`053e8210

Caused By Driver  : ataport.SYS

Caused By Address : ataport.SYS+1eea4

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ataport.SYS+19008

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\081712-31184-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7600

Dump File Size    : 297,600

==================================================



==================================================

Dump File         : 081712-29390-01.dmp

Crash Time        : 8/17/2012 10:38:13 PM

Bug Check String  : KERNEL_DATA_INPAGE_ERROR

Bug Check Code    : 0x0000007a

Parameter 1       : fffff6fc`50049ba8

Parameter 2       : ffffffff`c000000e

Parameter 3       : 00000000`4a5d8880

Parameter 4       : fffff8a0`09375000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+66580

File Description  : NT Kernel & System

Product Name      : Microsoft Windows Operating System

Company           : Microsoft Corporation

File Version      : 6.1.7600.21207 (win7_ldr.120503-2030)

Processor         : x64

Crash Address     : ntoskrnl.exe+66580

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\081712-29390-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7600

Dump File Size    : 297,600

==================================================



==================================================

Dump File         : 081112-25677-01.dmp

Crash Time        : 8/11/2012 10:29:03 PM

Bug Check String  : CRITICAL_OBJECT_TERMINATION

Bug Check Code    : 0x000000f4

Parameter 1       : 00000000`00000003

Parameter 2       : fffffa80`09383b30

Parameter 3       : fffffa80`09383e10

Parameter 4       : fffff800`031cbdf0

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+66580

File Description  : NT Kernel & System

Product Name      : Microsoft Windows Operating System

Company           : Microsoft Corporation

File Version      : 6.1.7600.21207 (win7_ldr.120503-2030)

Processor         : x64

Crash Address     : ntoskrnl.exe+66580

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\081112-25677-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7600

Dump File Size    : 297,600

==================================================

This attachment is potentially unsafe to open. It may be an executable that is capable of making changes to your file system, or it may require specific software to open. Use caution and only open this attachment if you are comfortable working with zip files.

minidumps.zip (104.64 KB)

2 Contributors
5 Replies
335 Views
2 Days Discussion Span
Latest Post 12 Years Ago Latest Post by Ithz

Reply to this topic

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Khav 0 Junior Poster · Answer 1 · 2012-08-19T16:37:31+00:00

Use the TDSSkiller from Kapersky to remove this MBR-virus rootkit.win32.TDSS.tdl4. Afterwards scan your PC with Malwarebytes. It will help.

I Suggest that you do a fresh install and install a good antivirus(I suggest kaspersky)

Ithz 0 Newbie Poster · Answer 2 · 2012-08-19T17:02:24+00:00

Hey Khav. I just did a scan with TDSSkiller and nothing was found. The only other option I know of now is to do a fresh install (like you said, and another friend suggested) and see if the problems still persist, thereby narrowing it down to a hardware or software problem. I'd like to know if there's a less tedious method though.

Khav 0 Junior Poster · Answer 3 · 2012-08-19T17:15:37+00:00

Hmmm
Better do a fresh install
Here are some tips
Just after fresh install install the following in the order below
1.Fresh Install
2.Install antivirus(Kaspersky or AvG are best)
3.Install all UPDATED drivers(check for your motherboard site for that) - This is most probable in your case
4.Retrieve all your backup files if any

That's wil be all

Ithz 0 Newbie Poster · Answer 4 · 2012-08-22T05:08:28+00:00

Hi, I did a fresh install yesterday, left it running overnight, and still had a BSOD occur.

It's a "critical object termination" and the "address in stack" is "ntoskrnl.exe + 450fff" if that makes any sense? The minidump files are attached.

Where should I go from here?

Ithz 0 Newbie Poster · Answer 5 · 2012-08-22T05:09:53+00:00

Ithz 0 Newbie Poster

12 Years Ago

Sorry, here's the new minidump files.

This attachment is potentially unsafe to open. It may be an executable that is capable of making changes to your file system, or it may require specific software to open. Use caution and only open this attachment if you are comfortable working with zip files.

minidumps_on_fresh_install.zip (54.53 KB)