• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Normal to have this many BSODs and app crashes?

L

lariz

Member
The only real problems I've been having lately have to do with games I play on my PC. I want to finally rule out the issue that's causing some of the games to either crash to desktop or give me a nasty BSOD.
Oblivion and BF 2142 have been the worst games (crash wise) on my hard drive. I've had a total of 5 BSODs with Oblivion with my first ever play through. I'm not even going to count how many times it's crashed to desktop.
BF 2142 is a bit different, it's much better than Oblivion but still gives me a few random desktop crashes when playing multiplayer.

I've narrowed it down to 3 things. It's either my hardware, my operation system(vista 32) or the actual game itself.

Most of my hardware isn't over a year old. I've ran memtest a ton of times and have never encountered an error. I rarely have computer shutdowns and freezes since I reinstalled my OS. Can it still be a piece of hardware I'm not seeing?
I have a 7900GS and I usually run games at 1680 x 1024 res on max settings. Could this be a problem? Can a game crash as a BSOD due to the fact the video card is not good enough to handle the settings? It certainly explains why I can run most older game fine.

Vista has a ton of problems, everything from the annoying and useless updates to the security that a 12 year old can bypass. On top of all this it doesn't seem to like games.
It almost seems that running games from the admin account(not admin mode on your regular account) makes apps run better. But people keep telling me that a regular account is more stable. Anyone out there actually use their admin account as their main account?

Maybe it's the games themselves. I've heard tons of other people having problems with these 2 games. I've heard of the BSOD horrors with Oblivion and how often BF 2142 should crash. Maybe it has nothing to do with my computer, but has something to do with the actual game I'm running.


I guess my general question is: How normal is it to have BSODs and desktop crashes when running PC games. Are there people out there that never have issues playing?
 
It can be many things what are these BSOD's telling you (what error do you get)? I've been racking my brain lately over a similar issue I had on my machine, it ran memtest fine and got no errors. I changed the ram anyways and made sure it was according the the specs of the motherboard (intel board is picky it had to have CL5) and voila BSOD's went away.

It can be many things, run scandisk on your HD's make sure you don't have any data corruption or even worse bad sectors.
Got a spare system lying around? Try the video card in there see if it works ok there. These are the worst things to troubleshoot, it's all trial and error.
 
That definitely sounds like a defective video card. If you have an older spare lying around, try that.

"I have a 7900GS and I usually run games at 1680 x 1024 res on max settings. Could this be a problem? Can a game crash as a BSOD due to the fact the video card is not good enough to handle the settings?"

No, not unless the card is defective.

"I've narrowed it down to 3 things. It's either my hardware, my operation system(vista 32) or the actual game itself. "
You narrowed it down? I am curious, what did you rule out?
The influence of Venus? Gremlins? ;-)
 
Originally posted by: oynaz

You narrowed it down? I am curious, what did you rule out?
The influence of Venus? Gremlins? ;-)
Click to expand...

Heh, that sounded better in my head, but i guess I worded it wrong.


Anyways, about the card. I've used it for over a year without much issues. It runs old games and MMOs fine. What way could I check the card?
 
The best way would be to replace the card. It does not need to be another 7900GS. Any card will do, though another Nvidea card would be easier, as you can avoid reinstalling the drivers that way.

Come to think of it, it might be a driver issue. Try reinstalling it.

Regarding Vista and admin / user accounts. I have serious issues with using common user accounts. It has come to a point where I have given up and just use an admin account all the time. Bad for security, but I rely heavily on Bluetooth, and that did not work with a common user account.
I have not seen any performance increase by going to the admin account.

I have not seen a BSOD on my Vista rig yet, though I have not had it for long. I play a lot of Bioshock, which runs flawlessly.
 

I'll be upgrading my card very soon regardless of the problems I'm having with my 7900. I just hope it's nothing serious with my motherboard or operating system. The last thing I want to do is install a new 8800 on an unstable system.
 
Originally posted by: lariz

I'll be upgrading my card very soon regardless of the problems I'm having with my 7900. I just hope it's nothing serious with my motherboard or operating system. The last thing I want to do is install a new 8800 on an unstable system.
Click to expand...

What causes a BSOD? Either bad hardware or bad drivers. User-mode software (games, applications) do not cause BSOD. The game may run the 3D card, and the 3D card relies on a driver, and the driver may be bad, so the system BSOD's, but the game itself doesn't BSOD the box - the driver does.

Go to my web page, read my guide, set up the debugger per the directions, and debug your dumpfile. Post your results and what you find here. In 10 minutes or so you should be able to resolve your own problem.

PS: Ignore anyone who talks about BSODs (that aren't hardware related) without telling you debug the dump first....with very few exceptions.
 
Originally posted by: dclive
Originally posted by: lariz

I'll be upgrading my card very soon regardless of the problems I'm having with my 7900. I just hope it's nothing serious with my motherboard or operating system. The last thing I want to do is install a new 8800 on an unstable system.
Click to expand...

What causes a BSOD? Either bad hardware or bad drivers. User-mode software (games, applications) do not cause BSOD. The game may run the 3D card, and the 3D card relies on a driver, and the driver may be bad, so the system BSOD's, but the game itself doesn't BSOD the box - the driver does.

Go to my web page, read my guide, set up the debugger per the directions, and debug your dumpfile. Post your results and what you find here. In 10 minutes or so you should be able to resolve your own problem.

PS: Ignore anyone who talks about BSODs (that aren't hardware related) without telling you debug the dump first....with very few exceptions.
Click to expand...

I checked out your site and followed your steps, but I couldn't find all of the BSOD dump files in vista. I found 1 named MEMORY.dmp in my temp folder but it said "access denied", even though I was on my admin account.

I find it odd that I never get BSOD's and any other problems with day to day computer work. It's only when I run these two games. Like you said, it's possibly a driver issue.
 
okay, I'll need the following info:

Motherboard Manufacturer with Model and BIOS Revision:
CPU Manufacturer and Model:
RAM Manufacturer and Model:
PSU Manufacturer and Model:
HDD(s): Manufacturer and Model:
CDRW/CDROM/DVD Manufacturer and Model:
Video Card: Manufacturer and Model:
Sound Card: Manufacturer and Model:
WIFI and/or Wired NIC Manufacturer and Model:
Operating System and Service Pack:
 
Originally posted by: robisbell
okay, I'll need the following info:

Motherboard Manufacturer with Model and BIOS Revision: Asus P5N-E SLI. BIOS revision 0202.
CPU Manufacturer and Model: Intel dual core E6600
RAM Manufacturer and Model: CORSAIR XMS2 2GB
PSU Manufacturer and Model: CORSAIR CMPSU-620HX ATX12V v2.2 and EPS12V 2.91 620W Power Supply
HDD(s): Manufacturer and Model: B: Western Digital Caviar RE WD2500YS 250GB
C: Western digital 320gb
CDRW/CDROM/DVD Manufacturer and Model: master: Samsung CD/DVDW SH-S182M ATA Slave: Sony DVD-ROM DDU1615 ATA
Video Card: Manufacturer and Model: evga nVIDIA 7900GS (I'll be getting an XFX 8800gt 512mb tomorrow)
Sound Card: Manufacturer and Model: onboard
WIFI and/or Wired NIC Manufacturer and Model: Netgear PCI adapter GA311
Operating System and Service Pack: Windows Vista Ultimate 32 bit. SP1 BETA, build 6001
Click to expand...

 
And the second question ... ?

Re: Access Denied - boot in safe mode, copy the files somewhere, and then zip and send them. Or right-click on the folder and give your user-ID permissions to the folder.
 
My OS is in my C drive.

I found the files and opened them with the debugger. I'll post them now:


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Admin\Documents\dump files BSOD\Mini010408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
Debug session time: Fri Jan 4 13:25:54.643 2008 (GMT-5)
System Uptime: 0 days 2:24:10.515
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.............................................................................................................................................
Loading User Symbols
Loading unloaded module list



-----------------------------------
-----------------------------------


* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
Debug session time: Sat Jan 5 11:07:16.026 2008 (GMT-5)
System Uptime: 0 days 2:13:27.898
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.............................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys

--------------------------
--------------------------


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Admin\Documents\dump files BSOD\Mini011708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Kernel Version 6001 (Service Pack 1.668) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81a10000 PsLoadedModuleList = 0x81b27c70
Debug session time: Thu Jan 17 11:08:58.366 2008 (GMT-5)
System Uptime: 0 days 3:24:15.239
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\drivers\watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10E, {1f, aaa3aee0, 0, 62bf7}

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.






I have about 7 of these files and all of them say the same thing. My guess would be that this ntkrnlpa.exe is at fault.

EDIT: To my knowledge ntkrnlpa has something to do with a video driver, so mavbe this explains why I haven't gotten any BSODs these past two days after I downloaded the new Nvidia beta drivers...but I could be wrong.
 
Re-read the documentation (pls see my website) and fix your symbols. Once you've done that, reopen the dumps in the debugger and re-analyze them. As long as the symbols error shows up, you're not getting a decent analysis.

NTKRNLPA is the Windows OS kernel.
I see DX.... in there - that is DirectX, and obviously that part is video card related.
 
Here it is with the symbols loaded:
These are the main 2 I get.



Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Admin\Documents\dump files BSOD\Mini010408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
Debug session time: Fri Jan 4 13:25:54.643 2008 (GMT-5)
System Uptime: 0 days 2:24:10.515
Loading Kernel Symbols
.............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {de9a8434, 0, 818198c9, 2}



Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+1ab )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: de9a8434, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 818198c9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

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




READ_ADDRESS: GetPointerFromAddress: unable to read from 819315ac
Unable to read MiSystemVaType memory at 819117e0
de9a8434

FAULTING_IP:
nt!MiDeleteAddressesInWorkingSet+1ab
818198c9 f7401800000008 test dword ptr [eax+18h],8000000h

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: WoW.exe

CURRENT_IRQL: 0

TRAP_FRAME: 9302b754 -- (.trap 0xffffffff9302b754)
ErrCode = 00000000
eax=de9a841c ebx=8512ca58 ecx=21701a11 edx=23093601 esi=c0118498 edi=c0801000
eip=818198c9 esp=9302b7c8 ebp=9302bc24 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiDeleteAddressesInWorkingSet+0x1ab:
818198c9 f7401800000008 test dword ptr [eax+18h],8000000h ds:0023😀e9a8434=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8188fbb4 to 818a9ef2

STACK_TEXT:
9302b73c 8188fbb4 00000000 de9a8434 00000000 nt!MmAccessFault+0x106
9302b73c 818198c9 00000000 de9a8434 00000000 nt!KiTrap0E+0xdc
9302bc24 81819cc7 8512c888 8512c888 8512c888 nt!MiDeleteAddressesInWorkingSet+0x1ab
9302bc54 81a1bd12 8512c888 930207fc 84bdd120 nt!MmCleanProcessAddressSpace+0x14f
9302bcbc 81a1b5cb 00000000 85e455c0 85e45601 nt!PspExitThread+0x64a
9302bcd4 818b1410 84bdd120 9302bd00 9302bd0c nt!PsExitSpecialApc+0x22
9302bd2c 8188cb56 00000001 00000000 9302bd44 nt!KiDeliverApc+0x1dc
9302bd2c 774b0e40 00000001 00000000 9302bd44 nt!KiServiceExit+0x56
WARNING: Frame IP not in any known module. Following frames may be wrong.
16beff60 00000000 00000000 00000000 00000000 0x774b0e40


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeleteAddressesInWorkingSet+1ab
818198c9 f7401800000008 test dword ptr [eax+18h],8000000h

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!MiDeleteAddressesInWorkingSet+1ab

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 470c2f52

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x50_nt!MiDeleteAddressesInWorkingSet+1ab

BUCKET_ID: 0x50_nt!MiDeleteAddressesInWorkingSet+1ab

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










second:


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Admin\Documents\dump files BSOD\Mini011608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Kernel Version 6001 (Service Pack 1.668) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.17052.x86fre.longhorn_rc1.071129-2315
Kernel base = 0x81a1c000 PsLoadedModuleList = 0x81b33c70
Debug session time: Wed Jan 16 21:05:39.449 2008 (GMT-5)
System Uptime: 0 days 11:35:45.321
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {84f52a24, ea29e0cf, 81b11b64, a}

Unable 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


Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::UnreferencePrimaryAllocation+f )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 84f52a24, Virtual address for the attempted write.
Arg2: ea29e0cf, PTE contents.
Arg3: 81b11b64, (reserved)
Arg4: 0000000a, (reserved)

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




CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xBE

PROCESS_NAME: System

CURRENT_IRQL: 2

TRAP_FRAME: 81b11b64 -- (.trap 0xffffffff81b11b64)
ErrCode = 0000000b
eax=84f52a24 ebx=8f1f9280 ecx=ffffffff edx=00000000 esi=84f52a18 edi=865ee008
eip=8bc0b3be esp=81b11bd8 ebp=81b11bdc iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
dxgkrnl!VIDMM_GLOBAL::UnreferencePrimaryAllocation+0xf:
8bc0b3be f00fc108 lock xadd dword ptr [eax],ecx ds:0023:84f52a24=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81a4e2f4 to 81a987d1

STACK_TEXT:
81b11b4c 81a4e2f4 00000001 84f52a24 00000000 nt!MmAccessFault+0x10a
81b11b4c 8bc0b3be 00000001 84f52a24 00000000 nt!KiTrap0E+0xdc
81b11bdc 8bc0bba8 00000001 84f52a18 00000001 dxgkrnl!VIDMM_GLOBAL::UnreferencePrimaryAllocation+0xf
81b11c18 8bc0ad30 0000002a 00000000 85539000 dxgkrnl!VidSchiCompleteFlipEntry+0x10a
81b11c78 8bc075d3 8852dfb8 8853f008 8f1f9280 dxgkrnl!VidSchiProcessDpcVSyncCookie+0x26e
81b11c90 8bc076ff 8853f008 00000001 87211000 dxgkrnl!VidSchDdiNotifyDpcWorker+0x57
81b11cb4 8b438c91 87246968 871ea8e0 87246a20 dxgkrnl!VidSchDdiNotifyDpc+0x6e
WARNING: Stack unwind information not available. Following frames may be wrong.
81b11ce8 81aa8536 87246d38 87246968 00000000 nvlddmkm+0x2dc91
81b11d50 81aa82cd 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
81b11d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl!VIDMM_GLOBAL::UnreferencePrimaryAllocation+f
8bc0b3be f00fc108 lock xadd dword ptr [eax],ecx

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl!VIDMM_GLOBAL::UnreferencePrimaryAllocation+f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 474fe16f

FAILURE_BUCKET_ID: 0xBE_dxgkrnl!VIDMM_GLOBAL::UnreferencePrimaryAllocation+f

BUCKET_ID: 0xBE_dxgkrnl!VIDMM_GLOBAL::UnreferencePrimaryAllocation+f

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



EDIT: edited with more information

 
For a BSOD, unless you have overheating hardware, bad hardware or something similar, it's almost always a driver (with very rare exceptions). The question is, which driver?

To me the first isn't conclusive, the second is graphics and nVidia driver related. You've said the latest nVidia driver seemed to stop the BSODs; let's see if that holds.
 
It's great news that it's a driver. I haven't gotten any problems since I switched to the new beta drivers so I guess the old ones were at fault.

Thanks for all the help guys, I really appreciate it.
 
Originally posted by: robisbell
I'd say something else, beta drivers are buggy at best. if it's working there's a issue still, just covered up.
Click to expand...

Assuming the problem stopped, how do you figure that?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top