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's , 2 today


29 Dec 2009   #1

Windows 7 Ultimate x64
 
 
BSOD's , 2 today

Am getting BSOD's 1 yesterday and 2 today. The one yesterday just happened while I was browsing through windows explorer. First one today happened when loading some software (Celestia) and the second when exiting a game (rFactor)

I've attached mini dumps and a screenshot. Am guessing this is drivers? Something seems unstable anyway.


Any help? This is quite annoying, I got less BSOD's with Vista in nearly 3 years that I have in 2 days with 7.

My System SpecsSystem Spec
.

29 Dec 2009   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Jomox View Post
Am getting BSOD's 1 yesterday and 2 today. The one yesterday just happened while I was browsing through windows explorer. First one today happened when loading some software (Celestia) and the second when exiting a game (rFactor)

I've attached mini dumps and a screenshot. Am guessing this is drivers? Something seems unstable anyway.


Any help? This is quite annoying, I got less BSOD's with Vista in nearly 3 years that I have in 2 days with 7.

Hi and welcome

these 3 dmp have 3 different causes. Dirextx/video driver, and a bunch of really old drivers.

I would update the driver
dl and run memtestx86 for 5 passes
run a system file check to verify and repair your system files
type cmd in search>right click and run as admin>sfc /scannow
You might also want to dl cpu-z, and gpu-z free to keep track of the temps


Ken J+

Code:
secdrv.SYS        fffff880`05d4e000    fffff880`05d59000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
xusb21.sys        fffff880`04415000    fffff880`04429480    0x00014480    0x45d66bc3    2/16/2007 9:43:15 PM                        
000.fcl        fffff880`05d98000    fffff880`05dbd000    0x00025000    0x479872ae    1/24/2008 6:12:46 AM                        
emupia2k.sys        fffff880`04599000    fffff880`045e3000    0x0004a000    0x47e21d92    3/20/2008 3:17:22 AM                        
ctsfm2k.sys        fffff880`04346000    fffff880`0437e000    0x00038000    0x47e21d99    3/20/2008 3:17:29 AM                        
ctoss2k.sys        fffff880`04190000    fffff880`041c1000    0x00031000    0x47e21da4    3/20/2008 3:17:40 AM                        
ha10kx2k.sys        fffff880`04432000    fffff880`04599000    0x00167000    0x47e21dbe    3/20/2008 3:18:06 AM                        
ctaud2k.sys        fffff880`04048000    fffff880`040ed780    0x000a5780    0x47e21e15    3/20/2008 3:19:33 AM                        
ctprxy2k.sys        fffff880`041c1000    fffff880`041c9000    0x00008000    0x47e21e16    3/20/2008 3:19:34 AM                        
CTEDSPFX.SYS        fffff880`0775f000    fffff880`077a9000    0x0004a000    0x47e21e23    3/20/2008 3:19:47 AM                        
CTEDSPIO.SYS        fffff880`07711000    fffff880`0773c000    0x0002b000    0x47e21e29    3/20/2008 3:19:53 AM                        
CTEDSPSY.SYS        fffff880`076bb000    fffff880`07711000    0x00056000    0x47e21e2e    3/20/2008 3:19:58 AM                        
COMMONFX.SYS        fffff880`0773c000    fffff880`0775f000    0x00023000    0x47e21e32    3/20/2008 3:20:02 AM
Code:
122909-19765-01.dmp    12/29/2009 6:46:20 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    ffff8280`0d449510    00000000`00000002    00000000`00000000    fffff880`043eb840    mouclass.sys    mouclass.sys+4840                    
122809-22854-01.dmp    12/28/2009 6:44:52 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff900`d07b10e8    00000000`00000000    fffff960`0028c556    00000000`00000002    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122909-16270-01.dmp    12/29/2009 7:08:18 PM    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    ffffffff`c0000005    fffff880`041247ac    fffff880`031be788    fffff880`031bdfe0    dxgmms1.sys    dxgmms1.sys+23770
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\122909-16270-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Tue Dec 29 14:07:11.414 2009 (GMT-5)
System Uptime: 0 days 0:21:11.882
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880041247ac, fffff880031be788, fffff880031bdfe0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec )

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: fffff880041247ac, The address that the exception occurred at
Arg3: fffff880031be788, Exception Record Address
Arg4: fffff880031bdfe0, 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_MEMORY_SEGMENT::EvictResource+fec
fffff880`041247ac 488b11          mov     rdx,qword ptr [rcx]

EXCEPTION_RECORD:  fffff880031be788 -- (.exr 0xfffff880031be788)
ExceptionAddress: fffff880041247ac (dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x0000000000000fec)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880031bdfe0 -- (.cxr 0xfffff880031bdfe0)
rax=0000000000000000 rbx=0000000000000000 rcx=2000000000000000
rdx=fffff8a0091386e0 rsi=fffff8a0091386e0 rdi=0000000000000000
rip=fffff880041247ac rsp=fffff880031be9c0 rbp=fffffa8003d2d000
 r8=0000000000010000  r9=0000000000000000 r10=0000000000000001
r11=fffff8a0091387e8 r12=0000000000000000 r13=0000000000000001
r14=fffffa8003d3c6f0 r15=fffff8a0091387e8
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec:
fffff880`041247ac 488b11          mov     rdx,qword ptr [rcx] ds:002b:20000000`00000000=????????????????
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 fffff80002cc30e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
fffff880`041247ac 488b11          mov     rdx,qword ptr [rcx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800411425d to fffff880041247ac

STACK_TEXT:  
fffff880`031be9c0 fffff880`0411425d : fffffa80`03d3c6f0 fffff8a0`091386e0 fffffa80`02176400 fffffa80`03d2d000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec
fffff880`031beb30 fffff880`0410f358 : fffffa80`02af6cc0 00000000`00000000 00000000`00000000 fffff880`031beca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
fffff880`031bec50 fffff880`0412d16d : fffffa80`00000000 fffffa80`03ced010 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`031beca0 fffff880`0412c3f8 : fffff800`00b96080 fffffa80`024b8200 00000000`00000000 fffffa80`03ced010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`031becd0 fffff880`0412be96 : 00000000`00000000 fffffa80`024b8200 00000000`00000080 fffffa80`03ced010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`031bed00 fffff800`02d30166 : 00000000`02e8de6a fffffa80`03d0c8c0 fffffa80`01848890 fffffa80`03d0c8c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`031bed40 fffff800`02a6b486 : fffff800`02c05e80 fffffa80`03d0c8c0 fffff800`02c13c40 fffff880`01258534 : nt!PspSystemThreadStartup+0x5a
fffff880`031bed80 00000000`00000000 : fffff880`031bf000 fffff880`031b9000 fffff880`031bd9b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff880031bdfe0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec

Followup: MachineOwner
---------
My System SpecsSystem Spec
29 Dec 2009   #3

Windows 7 Ultimate x64
 
 

Thanks for the reply!

My system is 100% stable hardware wise, as in my temperatures and memory is fine. I use CPU-Z, HWMonitor and Prime to check for stability and never had stability or heat issue's on my past installs or heat issue's currently, and this is with the exact same hardware and bios settings.

What are the really old drivers you are talking about? This is a fresh install of 7 only a few days old now.

I will follow your steps tonight. I did have some driver issue's you might want to look at also here:
http://www.sevenforums.com/drivers/4...t-install.html

Thanks.
My System SpecsSystem Spec
.


29 Dec 2009   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Jomox View Post
Thanks for the reply!

My system is 100% stable hardware wise, as in my temperatures and memory is fine. I use CPU-Z, HWMonitor and Prime to check for stability and never had stability or heat issue's on my past installs or heat issue's currently, and this is with the exact same hardware and bios settings.

What are the really old drivers you are talking about? This is a fresh install of 7 only a few days old now.

I will follow your steps tonight. I did have some driver issue's you might want to look at also here:
http://www.sevenforums.com/drivers/4...t-install.html

Thanks.

check the list in the box. you have drivers from 2006, 2007, and 2008.


Ken
My System SpecsSystem Spec
29 Dec 2009   #5

Windows 7 Ultimate x64
 
 

Could be the driver's for my old network card and other old software I use, also my old studio sound card which has driver's from last year.

How do I determine which driver's they are from the debug?
My System SpecsSystem Spec
29 Dec 2009   #6

Windows 7 Ultimate x64
 
 

I uninstalled the Nvidia driver's in Device Manager and then run Driver Sweeper. Rebooted, driver's installed fine. This is the latest set from Nvidia.

Then run ccleaner to clean temp files ets and registry fixer with ccleaner.

Run memtestx86 for 5 passes. Done no mem error's.

Run a system file check, done and it said it found some corrupt files but could not fix some of them. CBS.log attached.

Old driver's, I don't have a clue which old driver's are causing this as I don't understand anything in the dump, the codes given like, secdrv.SYS I cannot find. However emupia2k.sys I might know what that is, it's my sound card driver's. I own a Emu 1820M and I need it for my music production and audio car sound work. The sound card is working fine though and I can't understand why the driver's would cause a BSOD, that's if the emupia2k.sys is the Emu 1820m drivers.

Thanks in advance.
My System SpecsSystem Spec
29 Dec 2009   #7

Windows 7 Ultimate x64
 
 

I was just chatting to a friend on windows messenger and I got another BSOD out of no where, am not happy at all now.

I've run XP 32bit for years on this system and never had one BSOD, and run Vista 32bit for 3 years on my other system and only experienced 1 BSOD. But now 4 in 2 days with 7

I've attched the lastest minidump. Please let me know what caused this latest BSOD as I was only chatting on messenger. The OS seems really unstable.
My System SpecsSystem Spec
29 Dec 2009   #8

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Jomox View Post
I was just chatting to a friend on windows messenger and I got another BSOD out of no where, am not happy at all now.

I've run XP 32bit for years on this system and never had one BSOD, and run Vista 32bit for 3 years on my other system and only experienced 1 BSOD. But now 4 in 2 days with 7

I've attched the lastest minidump. Please let me know what caused this latest BSOD as I was only chatting on messenger. The OS seems really unstable.

Hi and welcome

this crash was probably caused by your mouclass.sys mouse driver.


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\122909-19656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c4be50
Debug session time: Tue Dec 29 18:14:06.062 2009 (GMT-5)
System Uptime: 0 days 0:58:43.529
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffff82800d28f890, 2, 0, fffff8800f0be840}

Probably caused by : mouclass.sys ( mouclass!memmove+250 )

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

0: 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: ffff82800d28f890, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800f0be840, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb60e0
 ffff82800d28f890 

CURRENT_IRQL:  2

FAULTING_IP: 
mouclass!memmove+250
fffff880`0f0be840 488b440af8      mov     rax,qword ptr [rdx+rcx-8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Steam.exe

TRAP_FRAME:  fffff80000ba2c10 -- (.trap 0xfffff80000ba2c10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8002b7f7b0
rdx=ffff88000a7100e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f0be840 rsp=fffff80000ba2da8 rbp=00000000f6151438
 r8=00000000000000f0  r9=0000000000000007 r10=000000000000002c
r11=fffffa8002b7f6c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
mouclass!memmove+0x250:
fffff880`0f0be840 488b440af8      mov     rax,qword ptr [rdx+rcx-8] ds:0030:ffff8280`0d28f890=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7f469 to fffff80002a7ff00

STACK_TEXT:  
fffff800`00ba2ac8 fffff800`02a7f469 : 00000000`0000000a ffff8280`0d28f890 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba2ad0 fffff800`02a7e0e0 : 00000000`00000055 00000000`000000f0 fffffa80`018ae000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2c10 fffff880`0f0be840 : fffff880`0f0bc9bc 00000000`000000f0 fffffa80`02e93a00 fffffa80`02e93a00 : nt!KiPageFault+0x260
fffff800`00ba2da8 fffff880`0f0bc9bc : 00000000`000000f0 fffffa80`02e93a00 fffffa80`02e93a00 fffff880`0fddf452 : mouclass!memmove+0x250
fffff800`00ba2db0 fffff880`0fde52ea : fffffa80`02c01640 fffffa80`02e938b0 fffffa80`02c01801 fffff800`02bfbba0 : mouclass!MouseClassServiceCallback+0x164
fffff800`00ba2e30 fffff800`02a8b5dc : fffff800`02bf8e80 fffff800`0000000a fffffa80`02c014f0 fffffa80`02c01890 : i8042prt!I8042MouseIsrDpc+0x28e
fffff800`00ba2f00 fffff800`02a86065 : 00000000`00000000 fffffa80`03f62060 00000000`00000000 fffff880`0fde505c : nt!KiRetireDpcList+0x1bc
fffff800`00ba2fb0 fffff800`02a85e7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`061232c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mouclass!memmove+250
fffff880`0f0be840 488b440af8      mov     rax,qword ptr [rdx+rcx-8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  mouclass!memmove+250

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mouclass

IMAGE_NAME:  mouclass.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc116

FAILURE_BUCKET_ID:  X64_0xD1_mouclass!memmove+250

BUCKET_ID:  X64_0xD1_mouclass!memmove+250

Followup: MachineOwner
---------
My System SpecsSystem Spec
29 Dec 2009   #9

Windows 7 Ultimate x64
 
 

Thanks very much for your help again but the mouse don't need separate driver's installing, windows just recognizes it automatically. If 7 seriously crashed due to the mouse am really considering going back to XP. If we can't fix all this then I will probably try 32bit and see how that is and then if I still have stability issue's I will go back to XP 32bit which will be a big disappointment as I was going to upgrade to 8gb which I need and support for 64bit XP is not good either.


Can you try help me fix these issue's? Got any tips or anything to help?

Thanks again for your help, much appreciated.
My System SpecsSystem Spec
29 Dec 2009   #10

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Jomox View Post
Thanks very much for your help again but the mouse don't need separate driver's installing, windows just recognizes it automatically. If 7 seriously crashed due to the mouse am really considering going back to XP. If we can't fix all this then I will probably try 32bit and see how that is and then if I still have stability issue's I will go back to XP 32bit which will be a big dissapoitment as I was going to upgrade to 8gb which I need and support for 64bit XP is not good either.


Can you try help me fix these issue's? Got any tips or anything to help?

Thanks again for your help, much appreciated.

Jomox


32bit is much much better. of the last 500 BSOD's I have analyzed 440 were 64bit
My System SpecsSystem Spec
Reply

 BSOD's , 2 today




Thread Tools



Similar help and support threads for2: BSOD's , 2 today
Thread Forum
BSOD today twice BSOD Help and Support
Got a bsod today BSOD Help and Support
Solved 2 BSOD's today, please help BSOD Help and Support
BSOD Today.... BSOD Help and Support
Solved Third BSOD today. BSOD Help and Support
Solved New Bsod Today BSOD Help and Support
Quite a few BSOD's going today. 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:18 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