BSOD random, but more often in BF3 / gaming

[macca22]

Afternoon,

im new to the forum, and not to clever with Computers.... i have recently upgraded my current PC but i get BSOD after about 20mins of gaming and sometimes random during anything!!!! Any help would be V much appreciated. i have followed the instructions and saved the SF file is that file attached. Also Memtest clean after 11 passes...

Anthony

 

[Arc]

Welcome aboard.

It is caused by NXP Semiconductors 3xHybrid.

[COLOR=Red]*** WARNING: Unable to verify timestamp for 3xHybr64.sys
*** ERROR: Module load completed but symbols could not be loaded for 3xHybr64.sys[/COLOR]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880044d7f30, fffff88003c3d518, fffff88003c3cd70}

Probably caused by : hardware ( 3xHybr64+68f30 )

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

And it is very old.

lmvm 3xHybr64.sys
start             end                 module name
0: kd> lmvm 3xHybr64
start             end                 module name
fffff880`0446f000 fffff880`04544300   3xHybr64 T (no symbols)           
    Loaded symbol image file: 3xHybr64.sys
    Image path: \SystemRoot\system32\DRIVERS\3xHybr64.sys
    [COLOR=Red]Image name: 3xHybr64.sys
    Timestamp:        Fri Apr 20 11:10:07 2007 [/COLOR](46285237)
    CheckSum:         000DDA00
    ImageSize:        000D5300
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try to update it from Home :: NXP Semiconductors.

Let us know the results.

 

[macca22]

Sorry im no Pc expert...... what exactly do i search for to update, thanks again for your help

 

[Arc]

In such a situation, you may take help of DriverMax.

 

[macca22]

thanks just updated, and ill see how it goes thanks again for your help

 

[macca22]

Hi,

i have tried the driver max and it updated around 8, things been going ok until 5mins ago , another BSOD any ideas !!! i have attached the Zip

Thanks again for your help

 

[Arc]

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Also test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Let us know the results, with the subsequent crash dumps, if any.

 

[macca22]

Hi done a memtest already 11 passes clean, i try the driver option thanks again

 

[macca22]

RANDOM BSOD any time doing anything.....

Hi,

i have had on going issues with BSOD but now it seems to be getting worse, if im working from home all day i probably get 3-4 per day sometimes more, any help would be great. I done a mem test with no issues.


Thanks

 

[Arc]

NovaShield Kernel Network Module driver Believed to be a part of BullGuard Internet Security.

BugCheck C2, {7, 109b, 92d8140, fffffa80069c76a0}

*** WARNING: Unable to verify timestamp for NSNetmon.sys
*** ERROR: Module load completed but symbols could not be loaded for NSNetmon.sys
GetPointerFromAddress: unable to read from fffff800032ff100
GetUlongFromAddress: unable to read from fffff800032ff1c0

fffffa80069c7690 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...

GetUlongFromAddress: unable to read from fffff8000326da38
Probably caused by : tdx.sys ( tdx! ?? ::FNODOBFM::`string'+2ff8 )

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

And that is old.

fffff880`0100d000 fffff880`01017000   NSNetmon T (no symbols)           
    Loaded symbol image file: NSNetmon.sys
    Image path: \SystemRoot\system32\DRIVERS\NSNetmon.sys
    Image name: NSNetmon.sys
    Timestamp:        Wed Nov 09 02:59:32 2011 (4EB99F3C)
    CheckSum:         000140A5
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would suggest you to uninstall BullGuard. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
If you dont agree, update it from Online Support, Product & Tech Guides. After a few days problems will continue again.

Agnitum Firewall Driver.

BugCheck BE, {9e0120, eda000011940d025, fffff80004447370, a}

*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for afw.sys
*** ERROR: Module load completed but symbols could not be loaded for afw.sys
Probably caused by : afw.sys ( afw+24ca )

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

Again agnitum.

BugCheck A, {0, 2, 1, fffff800030da065}

*** WARNING: Unable to verify timestamp for afwcore.sys
*** ERROR: Module load completed but symbols could not be loaded for afwcore.sys
Probably caused by : afwcore.sys ( afwcore+3c5e )

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

My suggestion is to delete it.

Logitech WingMan Translation Driver

BugCheck D1, {fffff8807f428ff0, 6, 0, fffff88004206390}

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

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

This is very old.

fffff880`04200000 fffff880`04211480   WmXlCore T (no symbols)           
    Loaded symbol image file: WmXlCore.sys
    Image path: \SystemRoot\system32\drivers\WmXlCore.sys
 [COLOR=Red]   Image name: WmXlCore.sys
    Timestamp:        Wed Apr 28 01:39:26 2010 [/COLOR](4BD74476)
    CheckSum:         000211D4
    ImageSize:        00011480
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Logitech - Support & Software Downloads.

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

And, reply back with the results. Two and half a month is not a continuation.

 

[macca22]

thanks for your help ill give this a whirl.....
i did just notice in the startup list there are 2 boxes checked for bullgaurd... could this have been the issue... i have checked now only one and will see what happens...i have also upadted the logitech drivers ....thanks again

 

[Arc]

The issue is the existence of bullguard and the other firewall in the entire system, not only in startup.

 

[macca22]

ok thanks , i had a bsod whilst replying to you i have attached the latest SF dump, just in case it shows anything else that may help, thanks again

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 50[/COLOR], {fffff70001d00004, 0, fffff800030aacdf, 2}


Could not read faulting driver name
[COLOR=Red]Probably caused by : dxgmms1.sys [/COLOR]( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------------
fffff880`037edf78  fffff880`04a0b2e8Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1402e8[/COLOR]
----------------------------------------------------------------------------------------------------------
fffff880`048cb000 fffff880`053ec000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
[COLOR=Red]    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 01 08:54:02 2012[/COLOR] (50B97852)
    CheckSum:         00B0A675
    ImageSize:        00B21000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

A side issue, a beta version of a display driver. You should use a WHQL one, as your system is crashing. But I cannot suggest you to apply the latest WHQL, as it is known a buggy. Better you roll it back to an earlier stable one.

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

Report us back when everything of this post and of post #10 is done.

 

[macca22]

Hi
Done all you asked.... worked fine all day and 5 mins ago had first BSOd of the day,
details attached
Thanks

 

[Arc]

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

[COLOR=Red]BAD_POOL_HEADER (19)[/COLOR]
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, [B][COLOR=Red]and then special pool applied to the suspect tags or the driver
verifier to a suspect driver[/COLOR][/B].
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa80069c63e0, The pool entry we were looking for within the page.
Arg3: fffffa80069c6c10, The next pool entry.
Arg4: 0000000004830013, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffffa80069c63e0 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033b7cae to fffff8000328cfc0

STACK_TEXT:  
fffff880`09fa8298 fffff800`033b7cae : 00000000`00000019 00000000`00000020 fffffa80`069c63e0 fffffa80`069c6c10 : nt!KeBugCheckEx
fffff880`09fa82a0 fffff800`0357f42c : fffffa80`069c63f0 fffff880`09fa85e0 00000000`74696157 00000000`00000006 : nt!ExDeferredFreePool+0x12da
fffff880`09fa8350 fffff800`035ac80d : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000001 : nt!ObpWaitForMultipleObjects+0x3a6
fffff880`09fa8820 fffff800`0328c253 : 00000000`00000000 fffff8a0`0a716a00 00000000`746c6644 fffff8a0`0a716a00 : nt!NtWaitForMultipleObjects32+0xec
fffff880`09fa8a70 00000000`75262e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01b0ef78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75262e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObpWaitForMultipleObjects+3a6
fffff800`0357f42c e935ffffff      jmp     nt!ObpWaitForMultipleObjects+0x2e0 (fffff800`0357f366)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!ObpWaitForMultipleObjects+3a6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x19_20_nt!ObpWaitForMultipleObjects+3a6

BUCKET_ID:  X64_0x19_20_nt!ObpWaitForMultipleObjects+3a6

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

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[macca22]

Afternoon,
been away for the weekend but just ran DV, first crash attached fingers crossed this helps,
Really appreciate your help on this

 

[Arc]

Hello mate, the last crash contained in the zip is of 30/01/2013. That means the new crashes were not recorded.

Most probably it occurred before the desktop loaded? If so, disable DV. Then re-enable it, making it sure that you are not selecting any driver provided by "microsoft" and "unknown". Hopefully it will go upto desktop and will crash there.

If the crash occurred on desktop and still not recorded, check that the crash dump recording is properly configured. Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[macca22]

will do ,thanks again

 

[macca22]

just happened, this one reset to windows