Seemingly "Random" Bsods

Page 5 of 6 FirstFirst ... 3456 LastLast

  1. Gingermadman
    Posts : 75
    Windows 7
    Thread Starter
       New #41

    zigzag3143 said:
    Gingermadman said:
    memory corruption

    these crashes were caused by memory corruption. Because of which I would download memtestx86 for at least 5 passes

    Let us know the results

    Ken
    I did that, It found one error on pass 8. I'm not sure why it wouldn't of found an error before then. Unless it does it in slots at one time, in which case it would be the end of the second ram slot I'm using.
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #42

    Gingermadman said:
    zigzag3143 said:
    Gingermadman said:
    memory corruption

    these crashes were caused by memory corruption. Because of which I would download memtestx86 for at least 5 passes

    Let us know the results

    Ken
    I did that, It found one error on pass 8. I'm not sure why it wouldn't of found an error before then. Unless it does it in slots at one time, in which case it would be the end of the second ram slot I'm using.
    Often times the real problem may be heat, and that would explain why it didnt start failing till pass 8. If you can isolate the problem to a specific memory slot that would change the problem to a mobo one.

    Ken
      My Computer
    Quote Quote

  4. Gingermadman
    Posts : 75
    Windows 7
    Thread Starter
       New #43

    zigzag3143 said:
    Gingermadman said:
    zigzag3143 said:


    these crashes were caused by memory corruption. Because of which I would download memtestx86 for at least 5 passes

    Let us know the results

    Ken
    I did that, It found one error on pass 8. I'm not sure why it wouldn't of found an error before then. Unless it does it in slots at one time, in which case it would be the end of the second ram slot I'm using.
    Often times the real problem may be heat, and that would explain why it didnt start failing till pass 8. If you can isolate the problem to a specific memory slot that would change the problem to a mobo one.

    Ken
    It's unlikely it would be due to heat as I have great ventilation and the ram sticks have large heatsinks on them.

    Is there anything else I can do to test the motherboard memory slot?
      My Computer
    Quote Quote

  6. Gingermadman
    Posts : 75
    Windows 7
    Thread Starter
       New #44

    Another new BSOD today.
      My Computer
    Quote Quote

  7. Jonathan_King
    Posts : 13,354
    Windows 7 Professional x64
       New #45

    This one looks like your video card driver:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_7thapril.zip\040710-16192-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a00000 PsLoadedModuleList = 0xfffff800`02c3de50
Debug session time: Wed Apr  7 09:12:07.846 2010 (GMT-4)
System Uptime: 0 days 1:27:52.734
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a00ae40038, 1, fffff880041a7507, 0}

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys

Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f )

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: fffff8a00ae40038, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880041a7507, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ca80e0
 fffff8a00ae40038 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
fffff880`041a7507 488908          mov     qword ptr [rax],rcx

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  BFBC2Game.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007a5b480 -- (.trap 0xfffff88007a5b480)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a00ae40038 rbx=0000000000000000 rcx=fffff8a00ae40038
rdx=fffffa8006154000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880041a7507 rsp=fffff88007a5b610 rbp=0000000000000001
 r8=fffffa800619a3d8  r9=0000000000000001 r10=0000000000000030
r11=fffff88007a5b5e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x17f:
fffff880`041a7507 488908          mov     qword ptr [rax],rcx ds:fffff8a0`0ae40038=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002af11e4 to fffff80002a71f00

STACK_TEXT:  
fffff880`07a5b318 fffff800`02af11e4 : 00000000`00000050 fffff8a0`0ae40038 00000000`00000001 fffff880`07a5b480 : nt!KeBugCheckEx
fffff880`07a5b320 fffff800`02a6ffee : 00000000`00000001 fffffa80`047e5e20 00000000`00000000 fffff880`04191ee3 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`07a5b480 fffff880`041a7507 : fffffa80`047e5e20 fffffa80`047e5e20 fffff8a0`0ae44820 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`07a5b610 fffff880`0418decc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x17f
fffff880`07a5b6e0 fffff880`040cfc10 : 00000000`00000000 fffff8a0`08185000 fffff8a0`08185000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`07a5b710 00000000`00000000 : fffff8a0`08185000 fffff8a0`08185000 00000000`00000001 00000000`00000000 : dxgkrnl+0x37c10


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
fffff880`041a7507 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  8. Gingermadman
    Posts : 75
    Windows 7
    Thread Starter
       New #46

    Newest one brings up things i've not seen before.
      My Computer
    Quote Quote

  10. Jonathan_King
    Posts : 13,354
    Windows 7 Professional x64
       New #47

    Still looks like your video drivers. Uninstall them completely, and then install the driver only, NOT the Catalyst suite.

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_8thapril.zip\040810-17019-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 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: Thu Apr  8 11:10:17.874 2010 (GMT-4)
System Uptime: 0 days 3:03:59.763
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {7000000, fffffa8005fc5010, fffffa8003a35860, fffffa800419e7c0}

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )

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

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000007000000, The subtype of the bugcheck:
Arg2: fffffa8005fc5010
Arg3: fffffa8003a35860
Arg4: fffffa800419e7c0

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8800191c22f to fffff80002a7ff00

STACK_TEXT:  
fffff880`02ffb808 fffff880`0191c22f : 00000000`00000119 00000000`07000000 fffffa80`05fc5010 fffffa80`03a35860 : nt!KeBugCheckEx
fffff880`02ffb810 fffff880`04131318 : fffffa80`04a6a010 00000000`00000000 00000000`00000000 fffffa80`03a358c0 : watchdog!WdLogEvent5+0x11b
fffff880`02ffb860 fffff880`0413137a : fffffa80`0000378e fffffa80`03a358c0 00000000`00000000 fffffa80`05fc5010 : dxgmms1!VidSchiCheckConditionDeviceCommand+0x8c
fffff880`02ffb890 fffff880`0412d360 : fffffa80`045fca80 fffffa80`03a35860 fffffa80`05fd0000 fffffa80`05fd0000 : dxgmms1!VidSchiCheckPendingDeviceCommand+0x3e
fffff880`02ffb8d0 fffff880`0412c7da : fffffa80`00000001 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x438
fffff880`02ffb990 fffff880`0412be00 : fffffa80`00000000 fffffa80`05fc5010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff880`02ffba30 fffff880`0412bc4c : 00000000`00005c91 fffffa80`05fc5010 fffffa80`055e6000 fffffa80`053ec000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02ffba80 fffff880`040321cf : fffffa80`054ba480 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02ffbad0 fffffa80`054ba480 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl+0x31cf
fffff880`02ffbad8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`13ebdfcd : 0xfffffa80`054ba480


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiCheckConditionDeviceCommand+8c
fffff880`04131318 c744243071c8ffff mov     dword ptr [rsp+30h],0FFFFC871h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiCheckConditionDeviceCommand+8c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+8c

BUCKET_ID:  X64_0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+8c

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  11. Gingermadman
    Posts : 75
    Windows 7
    Thread Starter
       New #48

    I have Nvidia, there shouldn't be any ATi remnants left on my machine.
      My Computer
    Quote Quote

  12. Jonathan_King
    Posts : 13,354
    Windows 7 Professional x64
       New #49

    How much RAM are you using? Look in the Performance tab of Task Manager.
      My Computer
    Quote Quote

  13. Gingermadman
    Posts : 75
    Windows 7
    Thread Starter
       New #50

    Not sure if you mean memory overall, or memory at one time/idle

      My Computer
    Quote Quote

 
Page 5 of 6 FirstFirst ... 3456 LastLast

  Related Discussions
Seemingly random "crash"?
in General Discussion

I'm not really sure what I would call my problem so please forgive me if I have labelled it incorrectly. I've had my computer for 3 years now and never had a problem with it, however recently, I've been getting this problem. If I leave my computer on and alone for too long, (the shortest it has...
I'm having ALOT of problems right now... Most annoying and disrupting problem are the random BSOD's. I downloaded Whocrashed and alot of crashes seem to be "memory management" . Sometimes it's 3rd party programs.. The BSOD lasts for 1/2 a second and computer immediately reboots so it's hard...
I have been getting these "Bad Pool Header" and "System Service Exception" BSODs for about a day now (the "Bad Pool Header" one tends to pop up more often then the other btw). I ran a registry cleaner which didn't work and ran memtest this morning and it showed that my memory was fine. The BSODs...
Hi A few days ago I did a new hardware build and installed W7 64 ultimate. I included a Corsair SSD as my boot drive for the speed advantage. I have done some investigation and tried to track down the cause of the BSOD but to no avail. Currently they are happening once\ twice or more...
Well... I never thought I'd see the day when I actually need others' advice on figuring out computers errors, but here I am! :p First off, a big thanks to all of the great advice/suggestions on the forum. I think I've narrowed it down, but I figure I'd let the experts take a quick peak and either...
Our Sites
Site Links
About 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 02:17.
Find Us