 | |
| |
| 26 Aug 2010 | #1 |
| | multi-BSOD Hi, I had a multi-BSOD with a multi causes i don't know what the cause of the BSOD I bought this computer a week ago and it is a fresh install. OS Name Microsoft Windows 7 Ultimate Version 6.1.7600 Build 7600 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name AHMAD-PC System Manufacturer System manufacturer System Model System Product Name System Type x64-based PC Processor Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date American Megatrends Inc. 0805, 2/24/2010 SMBIOS Version 2.5 Windows Directory C:\Windows System Directory C:\Windows\system32 Boot Device \Device\HarddiskVolume3 Locale United States Hardware Abstraction Layer Version = "6.1.7600.16385" User Name Ahmad-PC\Ahmad Time Zone Arabian Standard Time Installed Physical Memory (RAM) 6.00 GB Total Physical Memory 5.99 GB Available Physical Memory 4.38 GB Total Virtual Memory 12.0 GB Available Virtual Memory 10.3 GB Page File Space 5.99 GB Page File C:\pagefile.sys ---------------------------------------------------- I ran a memory test "Windows Memory Diagnostic" ended with on error. |
My System Specs | |
| 27 Aug 2010 | #2 |
| | Hi and Welcome to SF! There are 2 things that I suspect from the dmp files. First of all is your graphic card since directX was blamed and the stop code is graphic card related. SO let's try to re-install the graphic card first 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. Secondly, Third party antivirus are notorious for causing BSODs. let's try to remove Norton/Symantec for testing purpose: Download and run the Norton Removal Tool to uninstall your Norton product Try MSE for now, it's free and well-known for BSODs free, good for testing: http://www.microsoft.com/security_essentials Are you overclocking anything? Please run system file check: SFC /SCANNOW Command - System File Checker Regard, Tuan |
| My System Specs |
| 27 Aug 2010 | #3 |
| | thank you Tuan I have remove my graphic card driver with Guru3D and reinstall the driver with a fresh copy from the official website. also removed NAV and install MSE. about the OC I didn't change any thing from the bios. Is there a way to know If I'm OCing? SFC Quote: Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. now i will see if I encounter any BSOD I will post the dmp file |
| My System Specs |
| . |
| |
| 27 Aug 2010 | #4 |
| | According to the dump, you're not overclocking anything. |
| My System Specs |
| 27 Aug 2010 | #5 |
| | thank you cluberti |
| My System Specs |
| 27 Aug 2010 | #6 |
| | 
Quote: Originally Posted by ahmadkb  Hi, I had a multi-BSOD with a multi causes i don't know what the cause of the BSOD I bought this computer a week ago and it is a fresh install. OS Name Microsoft Windows 7 Ultimate Version 6.1.7600 Build 7600 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name AHMAD-PC System Manufacturer System manufacturer System Model System Product Name System Type x64-based PC Processor Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date American Megatrends Inc. 0805, 2/24/2010 SMBIOS Version 2.5 Windows Directory C:\Windows System Directory C:\Windows\system32 Boot Device \Device\HarddiskVolume3 Locale United States Hardware Abstraction Layer Version = "6.1.7600.16385" User Name Ahmad-PC\Ahmad Time Zone Arabian Standard Time Installed Physical Memory (RAM) 6.00 GB Total Physical Memory 5.99 GB Available Physical Memory 4.38 GB Total Virtual Memory 12.0 GB Available Virtual Memory 10.3 GB Page File Space 5.99 GB Page File C:\pagefile.sys ---------------------------------------------------- I ran a memory test "Windows Memory Diagnostic" ended with on error. 1-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. 2- Replace 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. Let us know if you need further assistance. Ken J 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\082710-25630-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`02e1c000 PsLoadedModuleList = 0xfffff800`03059e50
Debug session time: Thu Aug 26 21:30:49.222 2010 (GMT-4)
System Uptime: 0 days 5:44:53.298
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800fe20ff3, fffff8800599c698, fffff8800599bf00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )
Followup: MachineOwner
---------
4: 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: fffff8800fe20ff3, The address that the exception occurred at
Arg3: fffff8800599c698, Exception Record Address
Arg4: fffff8800599bf00, 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+a3
fffff880`0fe20ff3 48894108 mov qword ptr [rcx+8],rax
EXCEPTION_RECORD: fffff8800599c698 -- (.exr 0xfffff8800599c698)
ExceptionAddress: fffff8800fe20ff3 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000000a3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800599bf00 -- (.cxr 0xfffff8800599bf00)
rax=fffffa8008c6e9e0 rbx=fffff8a001c0d610 rcx=7ffffa8008c25370
rdx=fffff8a001b1a700 rsi=fffffa8008c18680 rdi=fffffa8008563000
rip=fffff8800fe20ff3 rsp=fffff8800599c8d0 rbp=0000000000000000
r8=fffffa8008c186d0 r9=fffff8800599c901 r10=0000000000000000
r11=fffffa800843f1e0 r12=0000000000000008 r13=0000000000000000
r14=fffffa8008bf7860 r15=000000000000001b
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3:
fffff880`0fe20ff3 48894108 mov qword ptr [rcx+8],rax ds:002b:7ffffa80`08c25378=????????????????
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 fffff800030c40e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`0fe20ff3 48894108 mov qword ptr [rcx+8],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800fe1e8af to fffff8800fe20ff3
STACK_TEXT:
fffff880`0599c8d0 fffff880`0fe1e8af : 00000000`00000000 fffffa80`08b8f040 00000000`0000001b fffffa80`08c0d0c8 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3
fffff880`0599c910 fffff880`0fe3865d : fffffa80`00000000 fffff8a0`01b32ac0 fffffa80`00000000 fffffa80`08bf7860 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`0599cae0 fffff880`0fe38398 : fffff800`00b96080 fffff880`0fe37d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0599ccd0 fffff880`0fe37e96 : 00000000`00000000 fffffa80`085a9d50 00000000`00000080 fffffa80`0843f1e0 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0599cd00 fffff800`03130c06 : 00000000`033792a2 fffffa80`08446770 fffffa80`055719e0 fffffa80`08446770 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0599cd40 fffff800`02e6ac26 : fffff800`03006e80 fffffa80`08446770 fffff800`03014c40 fffff880`01254534 : nt!PspSystemThreadStartup+0x5a
fffff880`0599cd80 00000000`00000000 : fffff880`0599d000 fffff880`05997000 fffff880`0599c690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff8800599bf00 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
Followup: MachineOwner
--------- |
| My System Specs |
| 27 Aug 2010 | #7 |
| | Hi Ken J I'm running the memtest now and I got errors in every pass. about 3 to 4 errors in each pass I'm in the end of pass 4 and got 14 errors what should I do now?! thanks for replying edit: Just now I got a new BSOD Last edited by ahmadkb; 27 Aug 2010 at 08:27 PM.. |
| My System Specs |
| 28 Aug 2010 | #8 |
| | If memtest is dropping errors to the screen while running, it indicates something is wrong with memory. Second to poorly written drivers, bad hardware configurations are what we find most here as the cause for bluescreens, so if you're seeing memory errors when testing your memory, replace it. |
| My System Specs |
| 29 Aug 2010 | #9 |
| | Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots. |
| My System Specs |
| 08 Sep 2010 | #10 |
| | thank you guys I change the RAMs and everything work fine |
| My System Specs |
 |
multi-BSOD problems?
| Thread Tools | |
| Similar help and support threads for: multi-BSOD | ||||
| Thread | Forum | |||
| BSOD multi-tasking. | BSOD Help and Support | |||
 Multi-Machine, Multi-License? | Windows Updates & Activation | |||
| multi users, multi ini files | General Discussion | |||
| multi-display multi-touch | Hardware & Devices | |||
| Multi-BSOD Within 3 Days | BSOD Help and Support | |||
All times are GMT -5. The time now is 07:06 PM.
