Various BSOD Errors, Please Help!

[Taio]

I am brand new to these forums and I am not extremely proficient with serious computer stuff, but I do believe I have compiled all the information the sticky thread mentioned in the attached ZIP folder. I also included a DxDiag for good measure. I posted most of my computer's specs in my profile, but here are the answers the sticky says to provide:

Windows 7 Professional x86 SP1
OEM (downloaded as an ISO as part of a deal through my Junior College)
Original OS was Windows XP Professional Retail, full wipe and reload done to install Win7.
All system components were purchased in January 2008 with the exception of the GTX 275 video card and Corsair 850W PSU which were purchased August 2009.
Current OS installation is only a few months old, I estimate I installed it around April 2011.

Thank you in advance for any and all help you folks can provide!

 

[FredeGail]

Hello Taio & Welcome to SevenForums! rb:

Let's get to it. Many of your .dmp files is unloaded, so this is just a random pick. Therefore, upload any new .dmp files incoming during the thread. Here's one of your crashes:

:ar: BSOD Summary

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {a7b99538, 2, 1, 979265a6}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextStatus+29e )

Followup: MachineOwner

dxgmms1.sys is connected to DirectX, so the first thing we'll try is to update your DirectX files. Download it here (Click), and report back any incoming .dmp file.

If you wonder what DirectX is, you can shortly read the link below.

What is DirectX - Wiki

Best Regards,
FredeGail

 

[Taio]

The installer said that a more recent or equivalent version was already installed, I believe I was instructed to update DirectX while trying to troubleshoot some World of Warcraft crashes I was experiencing. Can you look at one of the more recent dumps to see if one of them indicate a different problem?

 

[FredeGail]

The installer said that a more recent or equivalent version was already installed, I believe I was instructed to update DirectX while trying to troubleshoot some World of Warcraft crashes I was experiencing. Can you look at one of the more recent dumps to see if one of them indicate a different problem?

If you experience problems in World of Warcraft, it's likely that it'll be your DirectX. Can you take a snapshot of the error message the DX installer is giving you?

Best Regards,
FredeGail

 

[Taio]

Here it is!

 

[FredeGail]

I'm quite stomped. Let's wait for an answer by someone else.

I'll report back if I got news.
FredeGail

 

[Taio]

Thanks for the help anyhow, Frede The BSODs are so inconsistent, which probably makes them hard to diagnose effectively.

 

[Taio]

Got another BSOD, this time a Driver IRQL Not Less Or Equal. Dump is attached.

 

[FredeGail]

Easy. Reinstall your Nvidia Graphic Driver. It's optional to make a clean install in the Installation of the driver. You'll notice it when you select what to install.

Tip: Look for a :warn: when searching for a clean install. Tick it. By this - It will remove the previous driver.

:ar: BSOD Summary

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


Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI01.520\080411-15756-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82a37000 PsLoadedModuleList = 0x82b804d0
Debug session time: Fri Aug  5 03:49:55.794 2011 (UTC + 2:00)
System Uptime: 0 days 5:15:32.464
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, 98521b31}

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 : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveEntryList+1d )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 98521b31, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82ba0848
Unable to read MiSystemVaType memory at 82b7fe20
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiInterlockedRemoveEntryList+1d
98521b31 8901            mov     dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  dwm.exe

TRAP_FRAME:  807e2d1c -- (.trap 0xffffffff807e2d1c)
ErrCode = 00000002
eax=00000000 ebx=884ea3e4 ecx=00000000 edx=00000000 esi=85962008 edi=875f74f4
eip=98521b31 esp=807e2d90 ebp=807e2da0 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
dxgmms1!VidSchiInterlockedRemoveEntryList+0x1d:
98521b31 8901            mov     dword ptr [ecx],eax  ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 98521b31 to 82a785cb

STACK_TEXT:  
807e2d1c 98521b31 badb0d00 00000000 8672331a nt!KiTrap0E+0x2cf
807e2da0 9851adf1 875f74f4 884ea3e4 859621bc dxgmms1!VidSchiInterlockedRemoveEntryList+0x1d
807e2dc0 9851fd48 85962008 884ea3e0 875f7008 dxgmms1!VidSchiFreeQueuePacket+0x4f
807e2e10 9851fd77 024ea3e0 807e2e60 9852135c dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x48e
807e2e1c 9852135c 884ea3e0 875fc000 875fcaf0 dxgmms1!VidSchiProcessCompletedQueuePacket+0xd
807e2e60 98521451 875f7008 875fcaf0 875fce58 dxgmms1!VidSchiProcessDpcCompletedPacket+0x3e4
807e2e7c 9852151e 875f7008 87452000 875f7008 dxgmms1!VidSchiProcessDpcDmaPacket+0xc5
807e2e94 98521832 87452000 00000001 86b76000 dxgmms1!VidSchDdiNotifyDpcWorker+0xb2
807e2eb8 9845ef28 8694f5d0 807e2ed8 9845ee88 dxgmms1!VidSchDdiNotifyDpc+0x78
807e2ec4 9845ee88 8673aaa0 8694f5d0 983ffeb8 dxgkrnl!VIDSCH_EXPORT::VidSchDdiNotifyDpc+0x11
807e2ed8 97acd428 8694f5d0 983ffeb8 00000000 dxgkrnl!DxgNotifyDpcCB+0x5d
WARNING: Stack unwind information not available. Following frames may be wrong.
807e2ef4 97acd657 86b76000 86b76000 00000000 nvlddmkm+0xa1428
807e2f0c 97acdc05 86b76000 00000000 983ffeb8 nvlddmkm+0xa1657
807e2f28 97a4c971 807c3a00 86b76074 87c9adcc nvlddmkm+0xa1c05
807e2f3c 97a4c627 97a4c93f 807e2fa4 82aaf1b5 nvlddmkm+0x20971
807e2f48 82aaf1b5 86b76074 86b76000 00000000 nvlddmkm+0x20627
807e2fa4 82aaf018 807c2120 87c9ad48 00000000 nt!KiExecuteAllDpcs+0xf9
807e2ff4 82aae7dc 9f54fce4 00000000 00000000 nt!KiRetireDpcList+0xd5
807e2ff8 9f54fce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82aae7dc 00000000 0000001a 00d6850f bb830000 0x9f54fce4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiInterlockedRemoveEntryList+1d
98521b31 8901            mov     dword ptr [ecx],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgmms1!VidSchiInterlockedRemoveEntryList+1d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1

FAILURE_BUCKET_ID:  0xD1_dxgmms1!VidSchiInterlockedRemoveEntryList+1d

BUCKET_ID:  0xD1_dxgmms1!VidSchiInterlockedRemoveEntryList+1d

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

Best Regards,
FredeGail

 

[Taio]

I literally just reinstalled that driver a week ago. >.< I will try a clean reinstallation though, I did not know of that option.

 

[FredeGail]

I literally just reinstalled that driver a week ago. >.< I will try a clean reinstallation though, I did not know of that option.

You could also just remove it and use the Windows Update one, if you want to.

Best Regards,
FredeGail

 

[Taio]

I got a couple more BSODs before I reinstalled my graphics driver. Those are attached.

I just uninstalled the graphics driver in Safe Mode, restarted, and allowed Windows Update to install and update the graphics driver. Fingers crossed!

 

[FredeGail]

I got a couple more BSODs before I reinstalled my graphics driver. Those are attached.

I just uninstalled the graphics driver in Safe Mode, restarted, and allowed Windows Update to install and update the graphics driver. Fingers crossed!

Great!
Here's the last BSOD you had.

:ar: BSOD Summary

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82a900ed, a104bc98, 0}

Probably caused by : win32k.sys ( win32k!GreGetDeviceCaps+24d )

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

.. which is a Multi-User Win32 Driver. Quoting here from a forum:

   Warning

At own risk trying this fix!

The behavior may occur if the win32k.sys is corrupted. Go to
C:\WINDOWS\System32 and rename the Win32k.sys file to Win32k.old and then
close the window. Now go back to the system32 folder and you will have a
new and non-corrupt Win32k.sys file.

The behavior also may be caused by that the virtual memory of the Windows XP
is corrupted. Disable and then enable the Virtual Memory to see whether it
solved the problem.

To disable Virtual memory:

1. Right click My Computer and choose properties
2. Click the Advanced tab
3. Under Performance click settings.
4. Click the Advanced tab.
5. Under Virtual memory click change
6. Click no paging file
7. Click OK
8. Restart the computer

To enable Virtual memory:

1. Right click My Computer and choose properties
2. Click the Advanced tab
3. Under Performance click settings.
4. Click the Advanced tab.
5. Under Virtual memory click change
6. Click System Managed Size
7. Click OK
8. Restart the computer

Best Regards,
FredeGail