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 playing LOL, system_service_exeption

10 Jan 2012   #21

Windows 7 Enterprise x64
 
 

Damn got a BSOD again, but it was first 15 min in this time... :P

ive attatched another dumpfile...


My System SpecsSystem Spec
.

10 Jan 2012   #22

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\011012-22791-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e5d000 PsLoadedModuleList = 0xfffff800`030a2670 Debug session time: Mon Jan 9 19:04:10.579 2012 (UTC - 7:00) System Uptime: 0 days 0:03:10.766 Loading Kernel Symbols ................................................. Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {3452, 7fefd443000, fffff700010811d8, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36103 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000003452, The subtype of the bugcheck. Arg2: 000007fefd443000 Arg3: fffff700010811d8 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_3452 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: SetPointII.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002f49233 to fffff80002ed9c40 STACK_TEXT: fffff880`07ddbfb8 fffff800`02f49233 : 00000000`0000001a 00000000`00003452 000007fe`fd443000 fffff700`010811d8 : nt!KeBugCheckEx fffff880`07ddbfc0 fffff800`02eab596 : fffffa80`06652b30 fffffa80`00000000 fffff8a0`00000045 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x36103 fffff880`07ddc870 fffff800`031afb1a : fffff8a0`027a9060 fffff880`07ddcc20 00000000`00000000 fffffa80`068cf060 : nt!MmCleanProcessAddressSpace+0x96 fffff880`07ddc8c0 fffff800`0319309d : 00000000`00000000 fffffa80`06652e01 000007ff`fffa8000 fffffa80`0667ab60 : nt!PspExitThread+0x56a fffff880`07ddc9c0 fffff800`02ecd3fa : 00000000`00000000 fffffa80`06652b30 00000000`00000000 00000000`00000001 : nt!PsExitSpecialApc+0x1d fffff880`07ddc9f0 fffff800`02ecd740 : 00000000`003698f0 fffff880`07ddca70 fffff800`03193010 00000000`00000001 : nt!KiDeliverApc+0x2ca fffff880`07ddca70 fffff800`02ed8f77 : fffffa80`068cf060 00000000`048bff38 00000000`00000000 00000980`00000000 : nt!KiInitiateUserApc+0x70 fffff880`07ddcbb0 00000000`76d72b5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c 00000000`048bff18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d72b5a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+36103 fffff800`02f49233 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36103 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+36103 BUCKET_ID: X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+36103 Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\011012-17378-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`03054670 Debug session time: Tue Jan 10 11:23:20.839 2012 (UTC - 7:00) System Uptime: 0 days 3:12:15.025 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8800fd8cfe8, fffff88004110698, fffff8800410fef0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98 ) 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: fffff8800fd8cfe8, The address that the exception occurred at Arg3: fffff88004110698, Exception Record Address Arg4: fffff8800410fef0, 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+98 fffff880`0fd8cfe8 48035020 add rdx,qword ptr [rax+20h] EXCEPTION_RECORD: fffff88004110698 -- (.exr 0xfffff88004110698) ExceptionAddress: fffff8800fd8cfe8 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x0000000000000098) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff8800410fef0 -- (.cxr 0xfffff8800410fef0) rax=6dfff8a001873a60 rbx=fffff8a007f7c4a0 rcx=fffffa8004725e80 rdx=0000000000000060 rsi=fffffa80046dfbd0 rdi=fffffa8005b3d000 rip=fffff8800fd8cfe8 rsp=fffff880041108d0 rbp=0000000000000000 r8=fffffa80046dfc20 r9=0000000000000001 r10=0000000000000000 r11=fffffa8005b3e3e0 r12=000000000000002d r13=0000000000000000 r14=fffffa8004639010 r15=0000000000000078 iopl=0 nv up ei pl nz ac po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010216 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98: fffff880`0fd8cfe8 48035020 add rdx,qword ptr [rax+20h] ds:002b:6dfff8a0`01873a80=???????????????? 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 fffff800030be100 ffffffffffffffff FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98 fffff880`0fd8cfe8 48035020 add rdx,qword ptr [rax+20h] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff8800fd8a8af to fffff8800fd8cfe8 STACK_TEXT: fffff880`041108d0 fffff880`0fd8a8af : 00000000`00000000 fffffa80`0463a168 00000000`00000078 fffffa80`0463c440 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98 fffff880`04110910 fffff880`0fda465d : 00000000`00000000 fffff8a0`01873a60 fffffa80`00000000 fffffa80`04639010 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b fffff880`04110ae0 fffff880`0fda4398 : fffff800`00b96080 fffff880`0fda3d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`04110cd0 fffff880`0fda3e96 : 00000000`00000000 fffffa80`03f9d9e0 00000000`00000080 fffffa80`059e2320 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`04110d00 fffff800`03126fee : 00000000`1d589725 fffffa80`05b3c060 fffffa80`039d4040 fffffa80`05b3c060 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`04110d40 fffff800`02e7d5e6 : fffff800`03001e80 fffffa80`05b3c060 fffff800`0300fcc0 fffff880`01215384 : nt!PspSystemThreadStartup+0x5a fffff880`04110d80 00000000`00000000 : fffff880`04111000 fffff880`0410b000 fffff880`04110680 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1 STACK_COMMAND: .cxr 0xfffff8800410fef0 ; kb FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98 BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98 Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\011012-15880-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01e63000 PsLoadedModuleList = 0xfffff800`020a8670 Debug session time: Tue Jan 10 12:24:29.034 2012 (UTC - 7:00) System Uptime: 0 days 0:14:26.690 Loading Kernel Symbols ............................................................... ............................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80001ecd24c, fffff8800471e140, 0} Probably caused by : ntkrnlmp.exe ( nt!NtFreeVirtualMemory+783 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80001ecd24c, Address of the instruction which caused the bugcheck Arg3: fffff8800471e140, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!NtFreeVirtualMemory+783 fffff800`01ecd24c 488b4008 mov rax,qword ptr [rax+8] CONTEXT: fffff8800471e140 -- (.cxr 0xfffff8800471e140) rax=53fffa80054dfe00 rbx=fffffa80054ad600 rcx=0000000000000000 rdx=0000000006de9000 rsi=0000000006de9000 rdi=0000000000000002 rip=fffff80001ecd24c rsp=fffff8800471eb20 rbp=fffff8800471eca0 r8=0000000000006e6f r9=fffffa8004a87060 r10=0000000000000000 r11=0000000000004000 r12=fffffa80054ad600 r13=fffffa8004a87660 r14=0000000006e2afff r15=53fffa80054dfe00 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!NtFreeVirtualMemory+0x783: fffff800`01ecd24c 488b4008 mov rax,qword ptr [rax+8] ds:002b:53fffa80`054dfe08=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: VipreRescueSca CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001edeed3 to fffff80001ecd24c STACK_TEXT: fffff880`0471eb20 fffff800`01edeed3 : ffffffff`ffffffff 00000000`0008e320 00000000`0008e318 fffffa80`00004000 : nt!NtFreeVirtualMemory+0x783 fffff880`0471ec20 00000000`76d414fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0008e2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d414fa FOLLOWUP_IP: nt!NtFreeVirtualMemory+783 fffff800`01ecd24c 488b4008 mov rax,qword ptr [rax+8] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!NtFreeVirtualMemory+783 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 STACK_COMMAND: .cxr 0xfffff8800471e140 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!NtFreeVirtualMemory+783 BUCKET_ID: X64_0x3B_nt!NtFreeVirtualMemory+783 Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\011012-18049-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`0304c670 Debug session time: Tue Jan 10 14:13:16.205 2012 (UTC - 7:00) System Uptime: 0 days 0:25:01.766 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002e98bcd, fffff88003b0bc40, 0} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002e98bcd, Address of the instruction which caused the bugcheck Arg3: fffff88003b0bc40, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!IopCompleteRequest+fd fffff800`02e98bcd 488b87b0000000 mov rax,qword ptr [rdi+0B0h] CONTEXT: fffff88003b0bc40 -- (.cxr 0xfffff88003b0bc40) rax=0000000000000000 rbx=fffffa80047de2d0 rcx=0000000000000000 rdx=fffffa80047f86d1 rsi=0000000000000000 rdi=00fffa8005b51970 rip=fffff80002e98bcd rsp=fffff88003b0c620 rbp=0000000000000000 r8=fffffa80047f86d0 r9=0000000000000000 r10=fffff88002f64120 r11=fffffa8004753210 r12=0000000000000000 r13=0000000000000000 r14=fffffa8005b50060 r15=fffff88003b0cc20 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!IopCompleteRequest+0xfd: fffff800`02e98bcd 488b87b0000000 mov rax,qword ptr [rdi+0B0h] ds:002b:00fffa80`05b51a20=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: csrss.exe CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002e98bcd STACK_TEXT: fffff880`03b0b378 fffff800`02e831e9 : 00000000`0000003b 00000000`c0000005 fffff800`02e98bcd fffff880`03b0bc40 : nt!KeBugCheckEx fffff880`03b0b380 fffff800`02e82b3c : fffff880`03b0c3e8 fffff880`03b0bc40 00000000`00000000 fffff960`002b1ea0 : nt!KiBugCheckDispatch+0x69 fffff880`03b0b4c0 fffff800`02eaf4fd : fffff960`002fa314 fffff960`002c5580 fffff960`00010000 fffff880`03b0c3e8 : nt!KiSystemServiceHandler+0x7c fffff880`03b0b500 fffff800`02eae2d5 : fffff800`02fce788 fffff880`03b0b578 fffff880`03b0c3e8 fffff800`02e07000 : nt!RtlpExecuteHandlerForException+0xd fffff880`03b0b530 fffff800`02ebf361 : fffff880`03b0c3e8 fffff880`03b0bc40 fffff880`00000000 00fffa80`05b51970 : nt!RtlDispatchException+0x415 fffff880`03b0bc10 fffff800`02e832c2 : fffff880`03b0c3e8 fffffa80`047de2d0 fffff880`03b0c490 00000000`00000000 : nt!KiDispatchException+0x135 fffff880`03b0c2b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiSystemServiceHandler+7c fffff800`02e82b3c b801000000 mov eax,1 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiSystemServiceHandler+7c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x3B_nt!KiSystemServiceHandler+7c BUCKET_ID: X64_0x3B_nt!KiSystemServiceHandler+7c Followup: MachineOwner ---------
The next step is to install all Windows Updates.

Also, tonight, an hour before you go to sleep, run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Let it run overnight after checking to make sure no errors exist before going to sleep.

Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. Run this overnight tomorrow night. Start an hour before sleep as with Memtest86+.
My System SpecsSystem Spec
10 Jan 2012   #23

Windows 7 Enterprise x64
 
 

Okay ill do that... Ill keep you updated on the prosses...
My System SpecsSystem Spec
.


10 Jan 2012   #24

Windows 7 Enterprise x64
 
 

After installing all windows updates ive had alot of problems with all kinds of programs crashing over and over... ill start my memtest thingy now...
My System SpecsSystem Spec
10 Jan 2012   #25

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by NassiC View Post
After installing all windows updates ive had alot of problems with all kinds of programs crashing over and over... ill start my memtest thingy now...
That's not good. Can you run through the steps for uploading the dmp files and logs again? I can take a look as to causes of crashes and see if anything pops out at me.
My System SpecsSystem Spec
11 Jan 2012   #26

Windows 7 Enterprise x64
 
 

Okay have been running the memtest, and there are a lot of errors in my ram... Ive tryed and move them around like the guide said, and both ram blocks seems to have errors... how do i know what ram to buy??
My System SpecsSystem Spec
11 Jan 2012   #27

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by NassiC View Post
Okay have been running the memtest, and there are a lot of errors in my ram... Ive tryed and move them around like the guide said, and both ram blocks seems to have errors... how do i know what ram to buy??
Is this a vendor built machine (Dell, Toshiba, Sony, HP, Lenovo, etc.) or custom built?
My System SpecsSystem Spec
11 Jan 2012   #28

Windows 7 Enterprise x64
 
 

Its custom build...
My System SpecsSystem Spec
11 Jan 2012   #29

Windows 7 Enterprise x64
 
 

My System SpecsSystem Spec
11 Jan 2012   #30

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by NassiC View Post
Its custom build...
What is the motherboard? Unfortunately, we have no way to determine whether it is the RAM or the slots on the motherboard that are bad.

It may be the RAM was not compatible with the motherboard. If you can list the motherboard model and the RAM information, that would be great.
My System SpecsSystem Spec
Reply

 BSOD playing LOL, system_service_exeption




Thread Tools



Similar help and support threads for2: BSOD playing LOL, system_service_exeption
Thread Forum
BSOD playing too long, watching a video and playing a game or gmod BSOD Help and Support
Solved BSOD randomly/ when playing LoL and playing a video on youtube BSOD Help and Support
Solved BSOD Whilst playing Browsing and Playing game's BSOD Help and Support
BSOD on a daily basis, mostly when playing playing Heroes of Newerth. BSOD Help and Support
BSOD randomly after playing games or playing movies ) BSOD Help and Support
BSOD Playing while Playing WoW or Watching Movies BSOD Help and Support
Random BSOD System_Service_Exeption 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 08:01 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