Solved Random BSODs playing BF4

[palli]

Hello!

My BSOD problems started a few days ago while playing BF4. I have tried solving the problem myself without success and today I got a BSOD while watching some youtube videos.

I have, to my knowledge, updated all drivers I can think of.

My RAM and graphics card have been upgraded within a year.

Here's some info on the last two BSODs:


BCCode: d1
BCP1: 0000000043787254
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF88013D4C5C0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

BCCode: c9
BCP1: 0000000000000226
BCP2: FFFFF88005B17644
BCP3: FFFFF9800EFC4D30
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


And the dmp files on all BSODs so far.

Thanks in advance for all the help!

 

[Arc]

Search for any possible driver update for your HUAWEI Mobile Connect. Huawei - Support - Downloads

Let us know the situation after the update is done.
________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {226, fffff88005b17644, fffff9800efc4d30, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ew_usbenumfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ew_usbenumfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for ew_usbenumfilter.sys
Probably caused by : ew_usbenumfilter.sys ( ew_usbenumfilter+2644 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
    or someone forgot to return STATUS_PENDING.
Arg2: fffff88005b17644, The address in the driver's code where the error was detected.
Arg3: fffff9800efc4d30, IRP address.
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc9_226

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  226

FAULTING_IP: 
ew_usbenumfilter+2644
fffff880`05b17644 488bc4          mov     rax,rsp

FOLLOWUP_IP: 
ew_usbenumfilter+2644
fffff880`05b17644 488bc4          mov     rax,rsp

IRP_ADDRESS: fffff9800efc4d30

DEVICE_OBJECT: fffffa800a3fb040

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LOCK_ADDRESS:  fffff80003088da0 -- (!locks fffff80003088da0)

Resource @ nt!PiEngineLock (0xfffff80003088da0)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80003088da0
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800033114ec to fffff80002e84bc0

STACK_TEXT:  
fffff880`031a13d8 fffff800`033114ec : 00000000`000000c9 00000000`00000226 fffff880`05b17644 fffff980`0efc4d30 : nt!KeBugCheckEx
fffff880`031a13e0 fffff800`0331b58a : fffff800`0330fb00 fffff880`05b17644 fffff980`0efc4d30 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031a1420 fffff800`0331c593 : 00000000`00000226 fffffa80`09eadff8 fffff980`0efc4d30 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`031a1470 fffff800`033278ac : 00000000`00000000 fffffa80`09eadf40 fffffa80`09eadff8 fffffa80`09eb0ad0 : nt!VfErrorReport1+0x63
fffff880`031a1510 fffff800`03327c73 : fffffa80`09eadf40 00000000`00000002 fffffa80`0a3fb040 fffff800`0331a3b7 : nt!IovpCallDriver2+0x1bc
fffff880`031a1570 fffff800`0332dd3e : fffff980`0efc4d30 fffff980`0efc4d30 00000000`00000002 fffffa80`0a3fb040 : nt!VfAfterCallDriver+0x353
fffff880`031a15c0 fffff800`030f0571 : fffffa80`0a3fb040 fffff880`031a16c0 00000000`c00000bb fffffa80`09eadf40 : nt!IovCallDriver+0x57e
fffff880`031a1620 fffff800`03241b48 : 00000000`c00000bb fffff880`031a1860 fffff880`031a17d8 fffffa80`09eb8a00 : nt!IopSynchronousCall+0xe1
fffff880`031a1690 fffff800`03244590 : 00000000`00000000 fffffa80`0a3b39d0 00000000`00000000 fffffa80`0a3b39d0 : nt!PnpIrpQueryID+0x68
fffff880`031a1720 fffff800`03272cee : fffffa80`0a3b39d0 00000000`00000000 00000000`00000001 00000000`00000001 : nt!PnpQueryID+0x30
fffff880`031a1780 fffff800`03273f28 : fffffa80`09eb1af0 fffffa80`0a3b39d0 fffffa80`09de8780 00000000`00000001 : nt!PiProcessNewDeviceNode+0x12e
fffff880`031a1950 fffff800`03274468 : 00000000`00000000 00000000`00000000 00000000`00000010 fffff800`032743d0 : nt!PipProcessDevNodeTree+0x2e8
fffff880`031a1bc0 fffff800`02f87827 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000084 : nt!PiProcessReenumeration+0x98
fffff880`031a1c10 fffff800`02e8e261 : fffff800`02f87500 fffff800`0317bc01 fffffa80`06bc1b00 00000000`0000055a : nt!PnpDeviceActionWorker+0x327
fffff880`031a1cb0 fffff800`0312073a : 00000000`00000000 fffffa80`06bc1b50 00000000`00000080 fffffa80`06ba9ae0 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02e758e6 : fffff880`02f64180 fffffa80`06bc1b50 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  ew_usbenumfilter+2644

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ew_usbenumfilter

IMAGE_NAME:  ew_usbenumfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ba43c18

FAILURE_BUCKET_ID:  X64_0xc9_226_VRF_ew_usbenumfilter+2644

BUCKET_ID:  X64_0xc9_226_VRF_ew_usbenumfilter+2644

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc9_226_vrf_ew_usbenumfilter+2644

FAILURE_ID_HASH:  {4a03b0c5-2d82-cddc-645a-85bf3cce666b}

Followup: MachineOwner
---------

3: kd> lmvm ew_usbenumfilter
start             end                 module name
fffff880`05b15000 fffff880`05b18680   ew_usbenumfilter T (no symbols)           
    Loaded symbol image file: ew_usbenumfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\ew_usbenumfilter.sys
    Image name: ew_usbenumfilter.sys
    Timestamp:        Sat Mar 20 08:38:08 2010 (4BA43C18)
    CheckSum:         00011E8B
    ImageSize:        00003680
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[palli]

I updated the Huawei Mobile connector, will test for few days now to see if any BSODs appear...

 

[Arc]

Yes, you need to observe the situation.

 

[palli]

The problem seems to be gone! Thank you very much

 

[Arc]

Good to know.

Let us know for any further BSOD.

 

[palli]

Damn.... BSODs started again. Im a little more worried than the last time because it said hardware problems. Here is the info:

BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8007B57028
BCP3: 00000000B6004000
BCP4: 00000000F4000135
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

 

[Arc]

A stop 0x124 during gaming, BF4.

Are you overclocking?
As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest for at least 8 passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Stress test the CPU.

Hardware - Stress Test With Prime95
​

Let us know the results.

 

[palli]

No Im not overclocking, but I have turned my normally 2 core CPU into 4 core CPU (AMD Phenom II x2 555 Black edition --> AMD Phenom II x4 B55). If that counts. It has worked for over a year now without issues. And the stress tests showed no issues on the CPU.

I have a 500 watt PSU and I got these results:
Minimum PSU wattage 251
Recommended PSU wattage 301

Speccy screenshot added.

I tested with Furmark, passed, the heat leveled at 64 celsius. Ran for 30 minutes.

Prime95 passed.

As for the memtest how long do you think 8GB would take to test? Should I leave it running for the night and if so do I have to wake up to see what is going on or can I check in the morning?


EDIT: On a side note, can dust cause these kind of problems? I cleaned my system with compressor today and it was VERY dusty.

 

[Arc]

On a side note, can dust cause these kind of problems? I cleaned my system with compressor today and it was VERY dusty.

That is one of the most frequent causes of stop 0x124. It increases the heat there, which causes the BSOD.

Now, as the other tests all went good, see how it runs in the coming few days.

Let us know for any further BSOD.

 

[palli]

Seems like the dusting did the trick!! I have to clean up more often... Thanks again!

 

[Arc]