Blue Screen Error

Anonymous

Hey all, I had posted a question about this issue in the past (http://answers.microsoft.com/en-us/windows/forum/windows\_7-system/apparent-blue-screen-error-bccode-19/926cad07-b0e5-4517-b44e-bb21ae8ec29b), but it seems to not have been resolved even after following the steps given to me in the previous question (deleting Neo_0010.sys in the System32 folder).

Here are the past three Action Center reports: https://www.dropbox.com/s/q30bfnv6qaewzqo/Action%20Center%20Reports.txt?dl=0

Here are the past 3 DMPs (2 happened today, and 1 happened on the 8th), MSInfo32 and Speccy report: https://www.dropbox.com/s/d0q0f6usik3aqd1/DMPs%20MSInfo32%20and%20Speccy.rar?dl=0

This starting to get frustrating, especially since my laptop is only about 2-3 months old, and I want to resolve this as soon as possible.

If more information is needed let me know.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

45 answers

Anonymous

2014-10-20T21:29:56+00:00

Jesse

Please upload a fresh copy of your system information file. Click "start", type 'msinfo32", Click "file" at the top of the page, select "export" and give the file a name and click "save".

Navigate to where the file was saved to, and upload the generated text file to a public folder on your OneDrive account and post the link here.

After the upload, Run driver verifier (DV) per the instructions in the link below.

Note: Make sure to read and remember the steps to reset DV in the event of a crash.

　

Driver Verifier-- tracking down a mis-behaving driver. Created by ZigZag3143, Co.authored by by JMH3143

http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

https://onedrive.live.com/redir?resid=6858C63B379322D7!113&authkey=!AMYDLfmA9-s-s50&ithint=file%2crar

Use !analyze -v to get detailed debugging information.

BugCheck A, {1f0, 2, 0, fffff80003293325}

Unable to load image \SystemRoot\system32\drivers\MBfilt64.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for MBfilt64.sys

*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys

Probably caused by : MBfilt64.sys ( MBfilt64+1817 )

Followup: MachineOwner

STACK_COMMAND: kb

FOLLOWUP_IP:

MBfilt64+1817

fffff880`067b9817 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: MBfilt64+1817

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MBfilt64

IMAGE_NAME: MBfilt64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a7267b0

FAILURE_BUCKET_ID: X64_0xA_VRF_MBfilt64+1817

BUCKET_ID: X64_0xA_VRF_MBfilt64+1817

Followup: MachineOwner

This is definitely being triggered by the old MBfilt64.sys. Do you still have open broadcaster software (OBS.exe) still installed?

Yes

Is there a way to disable the software, for a while and then monitor the system to check if the crashing stops?
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-20T21:13:51+00:00

Jesse

Please upload a fresh copy of your system information file. Click "start", type 'msinfo32", Click "file" at the top of the page, select "export" and give the file a name and click "save".

Navigate to where the file was saved to, and upload the generated text file to a public folder on your OneDrive account and post the link here.

After the upload, Run driver verifier (DV) per the instructions in the link below.

Note: Make sure to read and remember the steps to reset DV in the event of a crash.

　

Driver Verifier-- tracking down a mis-behaving driver. Created by ZigZag3143, Co.authored by by JMH3143

http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

https://onedrive.live.com/redir?resid=6858C63B379322D7!113&authkey=!AMYDLfmA9-s-s50&ithint=file%2crar

Use !analyze -v to get detailed debugging information.

BugCheck A, {1f0, 2, 0, fffff80003293325}

Unable to load image \SystemRoot\system32\drivers\MBfilt64.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for MBfilt64.sys

*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys

Probably caused by : MBfilt64.sys ( MBfilt64+1817 )

Followup: MachineOwner

STACK_COMMAND: kb

FOLLOWUP_IP:

MBfilt64+1817

fffff880`067b9817 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: MBfilt64+1817

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MBfilt64

IMAGE_NAME: MBfilt64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a7267b0

FAILURE_BUCKET_ID: X64_0xA_VRF_MBfilt64+1817

BUCKET_ID: X64_0xA_VRF_MBfilt64+1817

Followup: MachineOwner

This is definitely being triggered by the old MBfilt64.sys. Do you still have open broadcaster software (OBS.exe) still installed?

Yes
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-20T20:34:33+00:00

Jesse

Please upload a fresh copy of your system information file. Click "start", type 'msinfo32", Click "file" at the top of the page, select "export" and give the file a name and click "save".

Navigate to where the file was saved to, and upload the generated text file to a public folder on your OneDrive account and post the link here.

After the upload, Run driver verifier (DV) per the instructions in the link below.

Note: Make sure to read and remember the steps to reset DV in the event of a crash.

　

Driver Verifier-- tracking down a mis-behaving driver. Created by ZigZag3143, Co.authored by by JMH3143

http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

https://onedrive.live.com/redir?resid=6858C63B379322D7!113&authkey=!AMYDLfmA9-s-s50&ithint=file%2crar

Use !analyze -v to get detailed debugging information.

BugCheck A, {1f0, 2, 0, fffff80003293325}

Unable to load image \SystemRoot\system32\drivers\MBfilt64.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for MBfilt64.sys

*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys

Probably caused by : MBfilt64.sys ( MBfilt64+1817 )

Followup: MachineOwner

STACK_COMMAND: kb

FOLLOWUP_IP:

MBfilt64+1817

fffff880`067b9817 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: MBfilt64+1817

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MBfilt64

IMAGE_NAME: MBfilt64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a7267b0

FAILURE_BUCKET_ID: X64_0xA_VRF_MBfilt64+1817

BUCKET_ID: X64_0xA_VRF_MBfilt64+1817

Followup: MachineOwner

This is definitely being triggered by the old MBfilt64.sys. Do you still have open broadcaster software (OBS.exe) still installed?
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-20T18:32:33+00:00

Some your installed software may not be suitable for Windows 7. Please download and run the Windows 7 Upgrade Advisor and upload a copy of the report to your OneDrive as a shared file:

https://www.microsoft.com/en-gb/download/details.aspx?id=20

https://onedrive.live.com/redir?resid=6858C63B379322D7!114&authkey=!APJqQbeU0BP\_LkM&ithint=file%2cmht
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-20T18:30:37+00:00

Jesse

Please upload a fresh copy of your system information file. Click "start", type 'msinfo32", Click "file" at the top of the page, select "export" and give the file a name and click "save".

Navigate to where the file was saved to, and upload the generated text file to a public folder on your OneDrive account and post the link here.

After the upload, Run driver verifier (DV) per the instructions in the link below.

Note: Make sure to read and remember the steps to reset DV in the event of a crash.

　

Driver Verifier-- tracking down a mis-behaving driver. Created by ZigZag3143, Co.authored by by JMH3143

http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

https://onedrive.live.com/redir?resid=6858C63B379322D7!113&authkey=!AMYDLfmA9-s-s50&ithint=file%2crar
Was this answer helpful?

0 comments No comments