Windows 7: Random BSOD's

ptrsok · 09 Sep 2011

Hi, I've been having random BSOD's, the last being whilst registering for this forum!
The previous one was this morning. I had been running dBpoweramp converter overnight converting 18,000 files. 12 hours in to a 14 hour operation and it failed.
I have 14,000 files converted but no idea what went wrong.
Can anybody help please?

Peter

Jonathan_King · 09 Sep 2011

Hello,

Try updating your nVidia display drivers: Drivers - Download NVIDIA Drivers

Code:

nvlddmkm.sys     Sat Oct 16 13:12:46 2010 (4CB9DD0E)

Run SeaTools on your hard drives: SeaTools for Windows | Seagate

Code:

Event[2211]:
  Log Name: System
  Source: Disk
  Date: 2011-09-03T17:56:12.553
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Peter-PC
  Description: 
The driver detected a controller error on \Device\Harddisk2\DR2.

If the BSODs persist, run driver verifier: Driver Verifier - Enable and Disable

...Summary of the dumps:

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Sep  4 13:37:23.719 2011 (UTC - 4:00)
System Uptime: 0 days 9:40:29.687
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
BiosReleaseDate = 11/11/2010
SystemProductName = X58A-UD3R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

ptrsok · 11 Sep 2011

Thanks for the reply.
I updated the graphics driver and ran SeaTools, all good.
I then ran dBpoweramp converter overnight again and woke to another restart screen following a BSOD. I've attached the dump files.
I'll now run driver verifier and see what happens.

Peter

seth500 · 11 Sep 2011

also update your directx components as one of the .dmp files points to it as a cause:

Download Details - Microsoft Download Center - DirectX 11 Technology Update

Code:

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


Loading Dump File [C:\Users\Administrator\Downloads\Windows_NT6_BSOD_jcgriff2\090411-23431-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e9d670
Debug session time: Sun Sep  4 11:37:23.719 2011 (UTC - 6:00)
System Uptime: 0 days 9:40:29.687
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 1, fffff880010100a4}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )

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

4: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880010100a4, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f07100
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
fffff880`010100a4 48897108        mov     qword ptr [rcx+8],rsi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  iexplore.exe

TRAP_FRAME:  fffff8800bb718d0 -- (.trap 0xfffff8800bb718d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010100a4 rsp=fffff8800bb71a60 rbp=fffffa80060f1d50
 r8=fffff8800bb71a80  r9=0000000000000000 r10=0000000000000000
r11=fffff880018d4120 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30:
fffff880`010100a4 48897108        mov     qword ptr [rcx+8],rsi ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd41e9 to fffff80002cd4c40

STACK_TEXT:  
fffff880`0bb71788 fffff800`02cd41e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0bb71790 fffff800`02cd2e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`060f1f58 : nt!KiBugCheckDispatch+0x69
fffff880`0bb718d0 fffff880`010100a4 : 00000000`00000000 fffffa80`060f1f58 fffffa80`060f1f48 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0bb71a60 fffff880`0103aae1 : 00000000`00000200 fffffa80`07ba1010 fffff8a0`00000000 fffffa80`05d26430 : dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30
fffff880`0bb71ab0 fffff880`0103d523 : 00000000`00000200 fffff880`0bb71d80 fffffa80`07272010 00000000`00000000 : dxgmms1!VidSchiAllocateQueuePacket+0x45
fffff880`0bb71b90 fffff880`0456d764 : 00000000`00000000 00000000`00000200 fffff880`0bb722c0 00000000`00000000 : dxgmms1!VidSchSubmitCommand+0x1f7
fffff880`0bb71bf0 fffff880`0456c773 : fffff8a0`00000001 fffff8a0`00000020 fffff880`0bb72270 fffff960`00000002 : dxgkrnl!DXGCONTEXT::Render+0xadc
fffff880`0bb72200 fffff960`001de8fa : 00000000`0126c830 00000000`40000001 00000000`0126d2f0 00000000`0126fd20 : dxgkrnl!DxgkRender+0x3e7
fffff880`0bb72470 fffff800`02cd3ed3 : 00000000`03868fd8 fffff880`0bb72520 00000000`00000000 00000000`7efa7000 : win32k!NtGdiDdDDIRender+0x12
fffff880`0bb724a0 00000000`73c0164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0126c808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73c0164a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
fffff880`010100a4 48897108        mov     qword ptr [rcx+8],rsi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

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

Jonathan_King · 11 Sep 2011

Go ahead and run Driver Verifier, but I believe this is a hardware problem. Try running the three Prime95 tests, as well as Memtest86.

http://www.sevenforums.com/tutorials...t-prime95.html

RAM - Test with Memtest86+

Seth - dxgmms1.sys is the Microsoft DirectX kernel driver, and won't actually be the cause of any crashes. Sometimes, when it is mentioned, it is a sign of video trouble: bad card? bad drivers? Often times, it doesn't even mean that though.

...Summary of the dumps:

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Sep 11 01:31:15.087 2011 (UTC - 4:00)
System Uptime: 0 days 22:10:26.038
Probably caused by : Ntfs.sys ( Ntfs!NtfsRemoveClose+83 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x7E_Ntfs!NtfsRemoveClose+83
BiosReleaseDate = 11/11/2010
SystemProductName = X58A-UD3R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

ptrsok · 13 Sep 2011

I ran Memtest86+ for 11 hours, 11 passes and no errors.
I ran Prime95, monitoring with RealTemp and the CPU temperatures rose to 90C.
With the system at idle temperatures are still 60C or 35C above ambient.
Before I go any further I will replace the stock heatsink and fan for something more efficient.
I didn't build this machine, an IT guy at work did, but I'm happy to work on it to improve it.
Once I've got the temperatures down I'll run Prime95 for a day and see what happens.

I think my BSOD's still might be software related because I've had plenty of them just browsing the web.

Peter

seth500 · 13 Sep 2011

Hi Peter remember that Prime95 is going to make that CPU run hotter than any other application you put to it. I will take a look at your event viewer logs and stuff and see if anything is off there..

seth500 · 13 Sep 2011

Code:

Event[4]:
  Log Name: Application
  Source: VSS
  Date: 2011-09-09T18:06:35.000
  Event ID: 12348
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Peter-PC
  Description: 
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{a566d7d6-ecf4-11df-82db-6cf049ec58f2}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Removing auto-release shadow copies
   Loading provider

Context:
   Execution Context: System Provider

Quote:

Resolve

Ensure that VSS has access to the volume root directory

If the Volume Shadow Copy Service (VSS) does not have access to the volume root directory, shadow copy creation on the volume will fail.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To ensure that VSS has access to the volume root directory:

Open an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type icacls <VolumeRootPath> /grant system:f at the command prompt, where <VolumeRootPath> is the path to the volume root directory, for example, D:\.

For more information about the icaclscommand, see Icacls.
Verify

To verify that the Volume Shadow Copy Service (VSS) is operating correctly, retry the previous VSS operation.

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

Code:

Event[1]:
  Log Name: Application
  Source: CVHSVC
  Date: 2011-09-09T18:13:01.000
  Event ID: 100
  Task: Client Virtualization Handler
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Peter-PC
  Description: 
Information only. Failed to complete bits job

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

Code:

Event[13]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-09T18:03:15.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Peter-PC
  Description: 
Fault bucket , type 0
Event Name: StartupRepairOnline
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7600.16385
P2: 6.1.7600.16385
P3: Gigabyte Technology Co., Ltd.
P4: 171
P5: 0
P6: AutoFailover
P7: 1
P8: NoRootCause
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_6.1.7600.16385_5d9d6d12f486f9f3e780236dbd53daacbc746ecd_cab_11bcfc48

Analysis symbol: 
Rechecking for solution: 0
Report Id: 997eb835-db05-11e0-ac0a-6cf049ec58f2
Report Status: 4

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

Code:

Event[21]:
  Log Name: Application
  Source: Application Virtualization Client
  Date: 2011-09-09T18:02:57.000
  Event ID: 3057
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Peter-PC
  Description: 
{tid=A5C}
The Application Virtualization Client Core initialized correctly. 
Installed Product: 
Version: 4.6.0.1523
Install Path: C:\Program Files (x86)\Microsoft Application Virtualization Client
Global Data Directory: C:\ProgramData\Microsoft\Application Virtualization Client\
Machine Name: PETER-PC
Operating System: Windows 7 64-bit Service Pack 1.0 Build 7601
OSD Command:

Probably ought to look at those applications and reinstall them..

Windows 7: Random BSOD's

Random BSOD's problems?