Random Multiple BSOD

[Arc]

A little question, is it possible that my current windows corrupted because of FAT32 format of flash disk? Well I always used FAT32 instead of NTFS and I never used the official tools to burn the iso file to dvd

Not very sure .... but it is always better to keep close to the defaults

 

[Icezed]

Well i'm starting to suspect my former windows 7 installation method
And by the way I'm done with the clean install, hope nothing goes wrong

 

[Icezed]

Ok, I got no BSODs so far but my PC seems to have another problem, it froze occasionally every several hours of normal usage . Perhaps it's a sign that BSOD will appear again

 

[Arc]

What is the wattage of your PSU?

 

[Icezed]

It's 600W, not a problem I guess

 

[Arc]

Ok, if it problems again let us know.

 

[Icezed]

Oh it's back, just like nightmares
I'm just wondering, what is ntoskrnl.exe? this is always shown to be the main cause in BluescreenView

 

[charkzilla20]

This might be helpful:

http://www.sevenforums.com/bsod-help-support/23643-ntoskrnl-exe-bsod.html

 

[Icezed]

Thanks, i'll check right away

 

[Arc]

A thread of the same name might not be any helpful at all ... as BSODs occur due to a wide range of causes; and it it showing ntoskrnl.exe as the error, it is nothing but the crash recording mechanism failed to record the actual cause of the BSOD.

ntoskrnl.exe is never the cause of the BSOD, but the system kernel on which it crashed.

Here we have enough reason to believe that the system is infected.

fffff880`02ecca18  fffff800`02cb9d0c nt!ExReleaseRundownProtectionCacheAware
fffff880`02ecca20  fffff880`012010d1 fvevol!FvePassThroughCompletion+0x29
fffff880`02ecca28  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02ecca30  fffff800`02ed9c38 nt!BBTBuffer <PERF> (nt+0x281c38)
fffff880`02ecca38  fffff880`01200000 fvevol!FveCompletionRoutine <PERF> (fvevol+0x0)
fffff880`02ecca40  fffff880`0120b00c fvevol!SHA256Magic <PERF> (fvevol+0xb00c)
fffff880`02ecca48  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02ecca50  fffff800`02edbdd4 nt!BBTBuffer <PERF> (nt+0x283dd4)
fffff880`02ecca58  fffff880`011aa000 CLASSPNP!ClassCompleteRequest <PERF> (CLASSPNP+0x0)
fffff880`02ecca60  fffff880`011c6078 CLASSPNP!WPP_MAIN_CB <PERF> (CLASSPNP+0x1c078)
fffff880`02ecca68  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02ecca70  fffff800`02edbdd4 nt!BBTBuffer <PERF> (nt+0x283dd4)
fffff880`02ecca78  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02ecca80  fffff880`00f96780 ataport!__PchSym_ <PERF> (ataport+0x17780)
fffff880`02ecca88  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02ecca90  fffff880`00f9675c ataport!__PchSym_ <PERF> (ataport+0x1775c)
fffff880`02ecca98  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02eccaa0  fffff880`00f96234 ataport!__PchSym_ <PERF> (ataport+0x17234)
fffff880`02eccaa8  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02eccab0  fffff880`00f96960 ataport!__PchSym_ <PERF> (ataport+0x17960)
fffff880`02eccab8  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02eccac0  fffff880`00f96948 ataport!__PchSym_ <PERF> (ataport+0x17948)
fffff880`02eccac8  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02eccad0  fffff800`02edc374 nt!BBTBuffer <PERF> (nt+0x284374)
fffff880`02eccad8  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02eccae0  fffff800`02eda514 nt!BBTBuffer <PERF> (nt+0x282514)

I would request cottonball to have a look at your thread. Please wait for him. He will be able to guide you the best to remove such infections, if it is there.

 

[Icezed]

A thread of the same name might not be any helpful at all ... as BSODs occur due to a wide range of causes; and it it showing ntoskrnl.exe as the error, it is nothing but the crash recording mechanism failed to record the actual cause of the BSOD.

ntoskrnl.exe is never the cause of the BSOD, but the system kernel on which it crashed.

Here we have enough reason to believe that the system is infected.

fffff880`02ecca18  fffff800`02cb9d0c nt!ExReleaseRundownProtectionCacheAware
fffff880`02ecca20  fffff880`012010d1 fvevol!FvePassThroughCompletion+0x29
fffff880`02ecca28  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02ecca30  fffff800`02ed9c38 nt!BBTBuffer <PERF> (nt+0x281c38)
fffff880`02ecca38  fffff880`01200000 fvevol!FveCompletionRoutine <PERF> (fvevol+0x0)
fffff880`02ecca40  fffff880`0120b00c fvevol!SHA256Magic <PERF> (fvevol+0xb00c)
fffff880`02ecca48  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02ecca50  fffff800`02edbdd4 nt!BBTBuffer <PERF> (nt+0x283dd4)
fffff880`02ecca58  fffff880`011aa000 CLASSPNP!ClassCompleteRequest <PERF> (CLASSPNP+0x0)
fffff880`02ecca60  fffff880`011c6078 CLASSPNP!WPP_MAIN_CB <PERF> (CLASSPNP+0x1c078)
fffff880`02ecca68  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02ecca70  fffff800`02edbdd4 nt!BBTBuffer <PERF> (nt+0x283dd4)
fffff880`02ecca78  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02ecca80  fffff880`00f96780 ataport!__PchSym_ <PERF> (ataport+0x17780)
fffff880`02ecca88  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02ecca90  fffff880`00f9675c ataport!__PchSym_ <PERF> (ataport+0x1775c)
fffff880`02ecca98  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02eccaa0  fffff880`00f96234 ataport!__PchSym_ <PERF> (ataport+0x17234)
fffff880`02eccaa8  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02eccab0  fffff880`00f96960 ataport!__PchSym_ <PERF> (ataport+0x17960)
fffff880`02eccab8  fffff880`00f7f000 ataport!ChannelSyncAcpiEvalMethod <PERF> (ataport+0x0)
fffff880`02eccac0  fffff880`00f96948 ataport!__PchSym_ <PERF> (ataport+0x17948)
fffff880`02eccac8  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02eccad0  fffff800`02edc374 nt!BBTBuffer <PERF> (nt+0x284374)
fffff880`02eccad8  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02eccae0  fffff800`02eda514 nt!BBTBuffer <PERF> (nt+0x282514)

I would request cottonball to have a look at your thread. Please wait for him. He will be able to guide you the best to remove such infections, if it is there.

So it's positively a virus infection? how about the motherboard corruption you mentioned before?

 

[cottonball]

Icezed,

Please do the following to check if malware is the cause of the problem...


:info: First, please download the Farbar Recovery Scan Tool
Select the 64-bit version.


Save it to the Desktop.

• Double-click the downloaded file to run it.
• When the tool opens click Yes to disclaimer.
• Press the Scan button.
• FRST64 makes a log (FRST.txt) in the same directory from which the tool is run (Desktop).

Please provide the FRST.txt in your reply. <<---

The first time the tool is run, it also makes another log: Addition.txt
Also post the Addition.txt in your reply. <<---



:info: Also, download Farbar Service Scanner


Save to the Desktop

• Make sure the following options are checked:
  • Internet Services
  • Windows Firewall
  • System Restore
  • Security Center
  • Windows Update
  • Windows Defender
• Press: Scan
• FSS creates a log, FSS.txt, on the Desktop.

Please provide the FSS.txt in your reply. <<---

However, to provide the above reports, please start a new topic at the System Security Forum:
http://www.sevenforums.com/system-security/

If there is malware on the computer, we'll take care of it there.

Thanks!

 

[Arc]

Icezed, as I told you earlier, it is either a rootkit or a bad port on the motherboard. Better you go through the process of malware removal at first. Follow cottonball.

If it saves you from the process of replacing the motherboard (alongwith the processor and RAM), it will be the better option for sure.

Thanks a lot, cottonball

 

[Icezed]

I'm terribly sorry for dissapearing in the last few days, because i had some work to do. I'll report my scan result within few hours