Member Avatar for Ithz

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!

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

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

==================================================
minidumps.zip (104.64 KB)
  • 2 Contributors
  • 5 Replies
  • 357 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by Ithz

Dani AI

Generated

Brief summary and targeted next steps that build on 's posts and 's driver/MBR suggestions.

Because a clean Windows reinstall did not stop the crashes and the dump shows a kernel-frame (ntoskrnl.exe + offset), the problem is more likely kernel-mode drivers, memory corruption, storage/firmware, PSU/thermal issues, or BIOS/firmware bugs than an active userland virus. Kernel offsets often point to the symptom (kernel unwind) rather than the root cause, so focus on low-level drivers and hardware.

Recommended, ordered diagnostic checks:

  1. Run an overnight memory test with MemTest86 (multiple full passes).
  2. Check drive health and SMART data (use vendor tools for full diagnostics); run a surface scan if HDD.
  3. Reset BIOS to defaults, disable any overclocking, then update BIOS and chipset/storage controller drivers from the motherboard vendor.
  4. Perform a clean boot (disable all non-Microsoft services) to see if third-party drivers/services trigger the crash.
  5. Use targeted Driver Verifier on non-Microsoft drivers only (have a recovery medium ready and know verifier /reset to disable it if it causes a boot loop).
  6. Reseat/remove RAM sticks and test one stick at a time; try different SATA cables/ports and a different power cable for the drive.
  7. Stress-test CPU/GPU/PSU (Prime95/OCCT/FurMark) while monitoring temperatures to rule out thermal/PSU instability.
  8. Analyze minidumps with WinDbg or WhoCrashed and inspect the first non-ntoskrnl module listed — that module name is often the best clue.

If crashes keep showing different addresses, prioritize memory and storage checks first (those produce variable failures). Driver Verifier will usually expose a specific faulty driver; proceed only after full backups and a recovery plan.

Member Avatar for Khav

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)

Member Avatar for Ithz

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.

Member Avatar for Khav

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

Member Avatar for Ithz

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?

Member Avatar for Ithz

Sorry, here's the new minidump files.

minidumps_on_fresh_install.zip (54.53 KB)
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.