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 crashes... various different reasons.


12 Sep 2010   #1

Windows 7 Professional x64
 
 
BSOD crashes... various different reasons.

Windows 7 Pro x64
Original OS installed
OEM version
Hardware is all new (brand new pc build)
OS installation is about 1 week old.

So I built the PC for a client and I have had it back a few times due to BSOD. At first I thought it was the RAM so I ran Memtest86+ and it did not encounter any problems.

I have followed the instructions and ran the BSOD Dump & System File Collection app as well as the Perfmon /report.

It is zipped and attached.

If anyone can give me some info about what I can do to try to get this system sorted I would be greatful!!


My System SpecsSystem Spec
.

12 Sep 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by goldcoastred View Post
Windows 7 Pro x64
Original OS installed
OEM version
Hardware is all new (brand new pc build)
OS installation is about 1 week old.

So I built the PC for a client and I have had it back a few times due to BSOD. At first I thought it was the RAM so I ran Memtest86+ and it did not encounter any problems.

I have followed the instructions and ran the BSOD Dump & System File Collection app as well as the Perfmon /report.

It is zipped and attached.

If anyone can give me some info about what I can do to try to get this system sorted I would be greatful!!
There are so many different causes of the creashes I have too start thinking hardware.

Lets see there is your dvd authoring software (drive is over 2 years old), you video driver, the logitech driver Khalmnpr.exe is a component of Logitech's Bluetooth mouse installation that allows for advanced configuration, ESET, and last but not least memory corruption.

Here is what I would do

1-update the drivers below
2-remove the dvd authoring sware
3-update your video driver

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

4-run a memory test

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

With all those answers we can start figuring out the problems.


Analysis
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\091310-20482-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03255000 PsLoadedModuleList = 0xfffff800`03492e50
Debug session time: Sun Sep 12 21:20:12.357 2010 (GMT-4)
System Uptime: 0 days 0:00:55.481
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88004582ff0, fffff88006d20698, fffff88006d1ff00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004582ff0, The address that the exception occurred at
Arg3: fffff88006d20698, Exception Record Address
Arg4: fffff88006d1ff00, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0
fffff880`04582ff0 488908          mov     qword ptr [rax],rcx

EXCEPTION_RECORD:  fffff88006d20698 -- (.exr 0xfffff88006d20698)
ExceptionAddress: fffff88004582ff0 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000000a0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88006d1ff00 -- (.cxr 0xfffff88006d1ff00)
rax=fffa8007451200f0 rbx=fffff8a001211c10 rcx=fffffa80083035f0
rdx=fffff8a00124f140 rsi=fffffa800831abe0 rdi=fffffa80079d1000
rip=fffff88004582ff0 rsp=fffff88006d208d0 rbp=0000000000000000
 r8=fffffa800831ac30  r9=fffff88006d20901 r10=0000000000000000
r11=fffffa8007a22010 r12=0000000000000018 r13=0000000000000000
r14=fffffa80082f7810 r15=000000000000002e
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa0:
fffff880`04582ff0 488908          mov     qword ptr [rax],rcx ds:002b:fffa8007`451200f0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fd0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0
fffff880`04582ff0 488908          mov     qword ptr [rax],rcx

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880045808af to fffff88004582ff0

STACK_TEXT:  
fffff880`06d208d0 fffff880`045808af : 00000000`00000000 fffffa80`081ff0c0 00000000`0000002e fffffa80`08307248 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa0
fffff880`06d20910 fffff880`0459a65d : 00000000`00000000 fffff8a0`01209660 fffffa80`00000000 fffffa80`082f7810 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`06d20ae0 fffff880`0459a398 : fffff800`00b96080 fffff880`04599d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`06d20cd0 fffff880`04599e96 : 00000000`00000000 fffffa80`081bdd50 00000000`00000080 fffffa80`07a22010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`06d20d00 fffff800`03569c06 : 00000000`02e8fa87 fffffa80`07885380 fffffa80`04ee9040 fffffa80`07885380 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`06d20d40 fffff800`032a3c26 : fffff800`0343fe80 fffffa80`07885380 fffff800`0344dc40 fffff880`0122c534 : nt!PspSystemThreadStartup+0x5a
fffff880`06d20d80 00000000`00000000 : fffff880`06d21000 fffff880`06d1b000 fffff880`06d20250 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff88006d1ff00 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0

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

Old drivers in need of updating
Code:
pcouffin.sys        fffff880`0fe70000    fffff880`0fe84380    0x00014380    0x457584a2    12/5/2006 10:39:30                        
000.fcl        fffff880`08f5e000    fffff880`08f89000    0x0002b000    0x48dcdf7a    9/26/2008 09:11:22                        
netr28x.sys        fffff880`10b58000    fffff880`10bf7000    0x0009f000    0x49a60631    2/25/2009 23:02:09                        
spldr.sys        fffff880`018ad000    fffff880`018b5000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`045e4000    fffff880`045f1000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`0111b000    fffff880`01126000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
LHidFilt.Sys        fffff880`06bda000    fffff880`06bed000    0x00013000    0x4a391ea3    6/17/2009 12:49:39                        
LMouFilt.Sys        fffff880`06800000    fffff880`06814000    0x00014000    0x4a391ea7    6/17/2009 12:49:43                        
LEqdUsb.Sys        fffff880`06bae000    fffff880`06bc5000    0x00017000    0x4a391eb2    6/17/2009 12:49:54                        
LHidEqd.Sys        fffff880`06bd2000    fffff880`06bda000    0x00008000    0x4a391eb4    6/17/2009 12:49:56                        
rtkio.sys        fffff880`08ff1000    fffff880`08ff9000    0x00008000    0x4a3c7af9    6/20/2009 02:00:25                        
LGPBTDD.sys        fffff880`06b95000    fffff880`06ba0000    0x0000b000    0x4a4baf58    7/1/2009 14:47:52
My System SpecsSystem Spec
13 Sep 2010   #3

Windows 7 Professional x64
 
 

sorry for the delayed response.. been out doing things. Do you have any recommended apps or locations to try to source the latest drivers?

I know there are heaps of driver update progs out there and a lot cause more problems than they fix so any suggestions would be very helpful.

Also which DVD authoring software are you referring to? DVDFab or PowerDVD or another one?

Thanks
My System SpecsSystem Spec
.


13 Sep 2010   #4

Windows 7 Professional x64
 
 

1-update the drivers below
pcouffin.sys 12/5/2006 10:39:30 Uninstalled Convertx
000.fcl 9/26/2008 09:11:22 Unsure of download location
netr28x.sys 2/25/2009 23:02:09 UPDATED new version 06/07/2010
spldr.sys 5/11/2009 12:56:27 Unsure where to download as is from Microsoft
GEARAspiWDM.sys 5/18/2009 08:17:04 Updated to 26/06/2010
amdxata.sys 5/19/2009 13:56:59 AMD? I think was associated with Convertx and is now uninstalled
LHidFilt.Sys 6/17/2009 12:49:39 Logitech Setpoint Mouse Updated new version 18/03/2010
LMouFilt.Sys 6/17/2009 12:49:43 Logitech Setpoint Mouse Updated new version 18/03/2010
LEqdUsb.Sys 6/17/2009 12:49:54 Logitech Setpoint Mouse Updated new version 18/03/2010 (i think)
LHidEqd.Sys 6/17/2009 12:49:56 Logitech Setpoint Mouse Updated new version 18/03/2010 (i think)
rtkio.sys 6/20/2009 02:00:25 Realtek driver.. unsure where to obtain latest driver
LGPBTDD.sys 7/1/2009 14:47:52 Logitech Game Panel Software Updated but Driver date is still 7/1/2009 downloaded from Logitech.

2-remove the dvd authoring sware
Unsure of which software you were referring to but have un-installed Convertx2DVD
3-update your video driver

Done as instructed
4-run a memory test
This is the interesting part... I ran Memtest earlier on the PC with all 3 sticks of RAM and it went through 4 passes with no dramas. Re-ran it just to check it off the list again. And Bam error central... I then tested each stick individually and nothing.. no errors at all(only on a quick 1 pass). Am running multiple passes with each stick individually now.

Will update with results after multiple passes on each stick to see what is goin on.
So any ideas on where I can grab the other drivers that appear outdated please
My System SpecsSystem Spec
Reply

 BSOD crashes... various different reasons.




Thread Tools



Similar help and support threads for2: BSOD crashes... various different reasons.
Thread Forum
irratic BSOD crashes, various reasons given BSOD Help and Support
a few BSOD, reasons for each appear not to be the same BSOD Help and Support
BSOD D3 Different Reasons BSOD Help and Support
Solved Random BSOD crashes with various reasons BSOD Help and Support
BSOD's and random crashes - Looking for reasons BSOD Help and Support
Windows 7: Four reasons to upgrade, four reasons to st News
Google Voice: 5 Reasons to Use It, 5 Reasons to Think T News

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 05:02 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33