Solved Weird BSOD.. please help.

[Anders]

so, ive recently put together a pc for my first time, everything went fine until i started getting BSOD whilst watching movies/series with VLC media player, it happens every time i watch movies for "random amounts of time"..i can play games all day long without any problems occuring... - tried re-installing software, checked every single driver in device management for updates, tried formatting but leads to the same issue.

BSOD info with some dumps:

Problemsignature:
Problem Event Name: BlueScreen
OS-version: 6.1.7601.2.1.0.768.3
Locale-ID: 1030

For more information about the problem:

BCCode: D1
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880061DB403
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


For more information about the problem:

C:\Windows\Minidump\090213-21138-01-dmp
C:\Users\Anders\AppData\Local\Temp\WER-100355-0.sysdata.xml

i tried a program called BlueScreenView, it lists out 2 files called:

e22w7x64.sys - e22w7x64.sys+8403
ntoskrnl.exe - ntoskrnl.exe+f20c4

Thanks in Advance, Anders

-
dump files created with the SF tool:

 

[YoYo155]

Hi ,

Two drivers are responsible:

BugCheck D1, {0, 2, 0, fffff880061db403}

*** WARNING: Unable to verify timestamp for e22w7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys
*** WARNING: Unable to verify timestamp for [COLOR=Red][U][B]afwcore[/B][/U][/COLOR].sys
*** ERROR: Module load completed but symbols could not be loaded for afwcore.sys
Probably caused by : [COLOR=Red][U][B]e22w7x64[/B][/U][/COLOR].sys ( e22w7x64+8403 )

lmvm afwcore
start             end                 module name
fffff880`03c7a000 fffff880`03cef000   afwcore  T (no symbols)           
    Loaded symbol image file: afwcore.sys
    Image path: \SystemRoot\system32\DRIVERS\afwcore.sys
    Image name: afwcore.sys
    Timestamp:        [COLOR=Red][U][B]Tue Oct 16 15:18:21 201[/B][/U][U][B]2[/B][/U][/COLOR] (507D508D)
    CheckSum:         0007BE76
    ImageSize:        00075000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


7: kd> lmvm e22w7x64
start             end                 module name
fffff880`061d3000 fffff880`061fd000   e22w7x64 T (no symbols)           
    Loaded symbol image file: e22w7x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e22w7x64.sys
    Image name: e22w7x64.sys
    Timestamp:        [COLOR=Red][U][B]Wed Dec 05 18:43:48 2012[/B][/U][/COLOR] (50BF79C4)
    CheckSum:         00035FA2
    ImageSize:        0002A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the driver for your "Killer-NIC"

• MSI Global ? Download Center

Remove the Agnitum Firewall software.

• Driver Reference Table - AfwCore.sys
  

 

[Anders]

Hey yoyo155, i could have sworn that i already updated the killer-NIC, anyhow.. so i reinstalled it using your link and started looking for the Agnitum Firewall software. But its nowhere to be found, also, ive never ever heard of it before... so what do i do?

EDIT: was looking around the internet for Agnitum Firewall software, when i saw that someone said it was a part of Bullguard's Firewall (my current anti-virus) would disabling the firewall in bullguard work? or do i have to find a different anti-virus?

 

[YoYo155]

Hey yoyo155, i could have sworn that i already updated the killer-NIC, anyhow.. so i reinstalled it using your link and started looking for the Agnitum Firewall software. But its nowhere to be found, also, ive never ever heard of it before... so what do i do?

EDIT: was looking around the internet for Agnitum Firewall software, when i saw that someone said it was a part of Bullguard's Firewall (my current anti-virus) would disabling the firewall in bullguard work? or do i have to find a different anti-virus?

I'm sorry my post wasn't very detailed, I would have been late for work if I would've stayed any longer .

Most third-party anti viruses are known to cause issues.
It's best you uninstall the software and use Microsoft Security Essentials as an alternative.

 

[Anders]

Just wanted to say, so far so good, havent had a single BSOD yet.

Thanks for your help yoyo155.

 

[YoYo155]

I'm happy .
Leave this thread open for a couple of days longer then if no issues arise mark it as solved.