Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD random, but more often in BF3 / gaming

30 Jan 2013   #11
macca22

windows 7 pro 64
 
 

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


My System SpecsSystem Spec
.
30 Jan 2013   #12
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

The issue is the existence of bullguard and the other firewall in the entire system, not only in startup.
My System SpecsSystem Spec
30 Jan 2013   #13
macca22

windows 7 pro 64
 
 

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
My System SpecsSystem Spec
.

30 Jan 2013   #14
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff70001d00004, 0, fffff800030aacdf, 2}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------------
fffff880`037edf78  fffff880`04a0b2e8Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1402e8
----------------------------------------------------------------------------------------------------------
fffff880`048cb000 fffff880`053ec000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 01 08:54:02 2012 (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.
Report us back when everything of this post and of post #10 is done.
My System SpecsSystem Spec
30 Jan 2013   #15
macca22

windows 7 pro 64
 
 

Hi
Done all you asked.... worked fine all day and 5 mins ago had first BSOd of the day,
details attached
Thanks
My System SpecsSystem Spec
30 Jan 2013   #16
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
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, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
04 Feb 2013   #17
macca22

windows 7 pro 64
 
 

Afternoon,
been away for the weekend but just ran DV, first crash attached fingers crossed this helps,
Really appreciate your help on this
My System SpecsSystem Spec
04 Feb 2013   #18
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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: Dump Files - Configure Windows to Create on BSOD
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.
My System SpecsSystem Spec
04 Feb 2013   #19
macca22

windows 7 pro 64
 
 

will do ,thanks again
My System SpecsSystem Spec
04 Feb 2013   #20
macca22

windows 7 pro 64
 
 

just happened, this one reset to windows
My System SpecsSystem Spec
Reply

 BSOD random, but more often in BF3 / gaming




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD when gaming
I have been getting random blue screen of death when I am playing games. The error on the BSOD is page fault in non paged area. Also my games will randomly crash when I am playing with the error thegame.exe has stopped working. I have ran memtest and have found no errors.
BSOD Help and Support
Random BSOD while gaming
Hey there, I've been experiencing some random BSOD's while gaming recently and have been unable to pin point the exact cause. There doesn't seem to be a pattern to it, they just seem to happen. Any assistance with this would be much appreciated. Cheers, D.
BSOD Help and Support
Random BSOD during gaming
As far as I can tell, my new system is not overheating. Generally the BSOD comes during gaming, but since this new box is primarily for gaming, that does not indicate very much. Please let me know if you can figure anything out from the dump files. The error message given is "A clock interrupt...
BSOD Help and Support
Random BSOD, mostly when gaming
Hi So I am getting a few random BSOD happens most of the times when I play games. I have runned prime95 for a couple of hours with no errors I have runned memtest+ for 4 hours and no errors Might need to write down that I am running 2 computer screens of my nVidia gtx 260, 1 with the...
BSOD Help and Support
random bsod when gaming and not doing anything
can analyze these dump files bsod in gaming (a lot) bsod while doing nothing (rare ) got dxgmms1.sys bsod too
BSOD Help and Support
Random BSOD's especially while gaming
I keep getting random BSODs like SYSTEM_SERVICE_EXCEPTION, IRQ_NOT_LESS_OR_EQUAL, and dxgmms1.sys crash BSOD. Have inlcude the required files in the zipped file. Windows 7 x64 is the original installed OS on the system - an OEM - System is 6-7 months old - OS is also same as was...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:50.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App