BSOD; System Service Expectation and others!

B

Beth

Newcomer
Hello to all!

So I have recently bought a new gaming PC in Aug 09, and for the past 3 months I have been getting BSOD errors. I have re-formated and cleaninstalled windows 7(64bit) twice and updated all my drivers with no avail, I still would get random BSOD, but only when I would play games (Go figure, gaming comp not being able to run WoW?)
These were just some of the Errors;
Page Fault in non-page area
IRQL not less or equal
Driver IRQL not less or equal
Bad Pool Header.

So after many emails back and forth with the people I bought my comp from they said to clean-install vista (what it came with) and update all my drivers and such, and I did.. After about 3 hours of getting it back up and running with the same settings and software as it did when I bought it, I now get the following error less then 2 minutes of playing WoW.
System Service Error.

Could anyone give me any advice how to stop these errors? And also if anyone knows if they are to do with hardware, software or drivers.

I would be SO very thankful for any information you could supply.

~Beth
 
Nothing to do with your OS, you most likely have faulty RAM. I'd start looking at your hardware starting with the RAM, then move onto overheating issues with your GPU or CPU, then look at PSU issues.
 
It could be the PSU as well. Overheating too, though that is extremely unlikely unless the system is incredibly incompetently put together).

If it's a complete system and you aren't comfortable with swapping out the memory or PSU to test where the problem lies (or if you can't borrow any spares) why not just get it fixed under warranty?

BTW, before testing it out with games you will have to install windows again, because there are decent odds your present install is buggered.
 
Unlikely to be a software problem. Run memtest86 and memory tests come out clean check for overheating components: CPU and GPU. If you also run Linux and get internal GCC errors when compiling code your memory is definitely bad.
 
Unless there is a second post coming with actual brands it can't really be considered spam ... it would have to be some kind of dataminer bot trying to ... make a list of helpful people? Weird.
 
No, I'm not a bot :p

I just didn't expect to get a responce so quickly. I am about to go to bed right now but will try all suggestions as soon as I wake up. and thank you :p
 
Page fault in non-paged area means RAM or Hard Drive, 99 times out of 100. IRQL not less or equal can often mean a faulty video card.
 
Beth said:
No, I'm not a bot :p

I just didn't expect to get a responce so quickly. I am about to go to bed right now but will try all suggestions as soon as I wake up. and thank you :p
Click to expand...
Really? If you're not I'm impressed. :)

If you could list out your PC's hardware it would help us help you; what kind of motherboard, ram, CPU, graphics card, etc. Oh, and your power supply and what wattage ratings it has would be helpful too. (It's usually listed on the side of your power supply)
 
Sorry for the slow replys, have been busy over christmas and the new year. Sadly I'm still having computer troubles, but this time I have managed to get the debugger to work. Here is the info that it has given me on my -latest- crash

Loading Dump File [C:\Windows\Minidump\Mini010110-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:\Windows\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18000.amd64fre.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0xfffff800`01a0f000 PsLoadedModuleList = 0xfffff800`01bd4db0
Debug session time: Fri Jan 1 14:08:34.822 2010 (GMT+8)
System Uptime: 1 days 0:32:22.749
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffffa6006234171, fffffa600b23d0d0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\lvrs64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for lvrs64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvrs64.sys
Probably caused by : lvrs64.sys ( lvrs64+6171 )
Followup: MachineOwner
---------
1: 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: fffffa6006234171, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffa600b23d0d0, 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:
lvrs64+6171
fffffa60`06234171 ?? ???
CONTEXT: fffffa600b23d0d0 -- (.cxr 0xfffffa600b23d0d0)
rax=0000000000000000 rbx=fffffa8008c7f580 rcx=0000000000000003
rdx=0000000000000000 rsi=fffffa8008c31600 rdi=0000000000000000
rip=fffffa6006234171 rsp=fffffa600b23d930 rbp=fffffa800893c040
r8=fffffa80089560a8 r9=fffff80001a8c4f0 r10=0000000000000048
r11=fffffa600b23d7a8 r12=fffffa8008cddbd0 r13=0000000000000000
r14=00000000002f0003 r15=fffffa800888f060
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
lvrs64+0x6171:
fffffa60`06234171 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffffa8000000000 to fffffa6006234171
STACK_TEXT:
fffffa60`0b23d930 fffffa80`00000000 : fffffa80`08c7f580 fffffa80`0893c040 fffffa80`08c31600 fffffa60`0b23da00 : lvrs64+0x6171
fffffa60`0b23d938 fffffa80`08c7f580 : fffffa80`0893c040 fffffa80`08c31600 fffffa60`0b23da00 fffffa60`032b4a87 : 0xfffffa80`00000000
fffffa60`0b23d940 fffffa80`0893c040 : fffffa80`08c31600 fffffa60`0b23da00 fffffa60`032b4a87 fffffa80`08c31600 : 0xfffffa80`08c7f580
fffffa60`0b23d948 fffffa80`08c31600 : fffffa60`0b23da00 fffffa60`032b4a87 fffffa80`08c31600 00000000`00000000 : 0xfffffa80`0893c040
fffffa60`0b23d950 fffffa60`0b23da00 : fffffa60`032b4a87 fffffa80`08c31600 00000000`00000000 00000000`00000000 : 0xfffffa80`08c31600
fffffa60`0b23d958 fffffa60`032b4a87 : fffffa80`08c31600 00000000`00000000 00000000`00000000 fffffa60`0b23da00 : 0xfffffa60`0b23da00
fffffa60`0b23d960 fffffa60`032b47dd : 00000000`00000000 fffffa80`08c319e8 fffffa80`08c31a30 fffffa80`08cea7a0 : ksthunk!CKSThunkDevice::DispatchIoctl+0xcf
fffffa60`0b23d990 fffff800`01cea25a : fffffa80`08cddbd0 fffffa60`0b23dca0 fffffa80`00000000 00000000`00000001 : ksthunk!CKernelFilterDevice::DispatchIrp+0x11d
fffffa60`0b23d9f0 fffff800`01d02f76 : 00000000`01dbfa10 00000000`000002e5 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5da
fffffa60`0b23db40 fffff800`01a63e33 : fffffa80`08956060 00000000`01dbf9f8 fffffa60`0b23dbc8 00000000`01dbfc90 : nt!NtDeviceIoControlFile+0x56
fffffa60`0b23dbb0 00000000`77955aea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01dbfa08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77955aea

FOLLOWUP_IP:
lvrs64+6171
fffffa60`06234171 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: lvrs64+6171
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: lvrs64
IMAGE_NAME: lvrs64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4acc510f
STACK_COMMAND: .cxr 0xfffffa600b23d0d0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_lvrs64+6171
BUCKET_ID: X64_0x3B_lvrs64+6171
Followup: MachineOwner
---------
 
Oh. and here is my comp details.

DetailsName
DDR3gamingDDR3 GAMING SYSTEMCaseZonix Case with Heavy Duty 650w PSUMotherboardGigabyte P45T-UD3LR Intel ChipsetSound CardIntegrated 7.1 High Definition AudioProcessor (CPU)Intel Core 2 QUAD Q9400 2.6GhzGraphics CardGeforce nVidia 9600GT 512MbHard Disk DriveWD/Seagate 500Gig Hard DriveRAM (memory)8 Gigabytes 1333Mhz DDR3 (64Bit OS only)Card ReaderAll in One card Reader for your Digital CameraOperating SystemVista Premium 64 Bit with Windows 7 Upgrade
 
lvr64.sys belongs to the mixer of the microphone input on your webcam.

audiodg.exe belongs to the sound system in Vista and higher.

Debug your other minidumps to see if the error is consistently caused by these items.

If the causes vary, your RAM is still the most likely culprit. If lvr64.sys is always the problem, try detaching your webcam and see if the crashes persist. If they don't, try finding the latest driver for the device.
 
It doesnt seem to be the lvr64.sys popping up.. Not sure if I should post all of the errors, as there are 49, earliest one being the 21 Dec 09. (I had clean-installed Vista again on the 20th)
I really have no idea what any of this means.. and googling can only get you so far.
Here is a few more of my latest crashes.



Debug session time: Fri Jan 1 19:01:29.377 2010 (GMT+8)
System Uptime: 0 days 0:00:19.064
*******************************************************************************
* *
* 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: fffff80001ce3582, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffa6004e20280, 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!NtAlpcOpenSenderThread+42
fffff800`01ce3582 448ab853010000 mov r15b,byte ptr [rax+153h]
CONTEXT: fffffa6004e20280 -- (.cxr 0xfffffa6004e20280)
rax=0000000009f22060 rbx=fffffa8009f22060 rcx=0000000000d8fc20
rdx=0000000000000080 rsi=0000000000d8fbc8 rdi=0000000000d8fce0
rip=fffff80001ce3582 rsp=fffffa6004e20ae0 rbp=fffffa6004e20ca0
r8=0000000000d8fce0 r9=0000000000000000 r10=0000000000000080
r11=fffff80001aa6e10 r12=0000000000000015 r13=0000000000d8fc20
r14=0000000000000000 r15=00000000004b4730
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!NtAlpcOpenSenderThread+0x42:
fffff800`01ce3582 448ab853010000 mov r15b,byte ptr [rax+153h] ds:002b:00000000`09f221b3=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001aa6e33 to fffff80001ce3582
STACK_TEXT:
fffffa60`04e20ae0 fffff800`01aa6e33 : fffffa80`09f22060 fffffa60`04e20bc8 00000000`00000015 ffff4c1c`33d8bd48 : nt!NtAlpcOpenSenderThread+0x42
fffffa60`04e20bb0 00000000`775c628a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00d8fba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775c628a

FOLLOWUP_IP:
nt!NtAlpcOpenSenderThread+42
fffff800`01ce3582 448ab853010000 mov r15b,byte ptr [rax+153h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!NtAlpcOpenSenderThread+42
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7
STACK_COMMAND: .cxr 0xfffffa6004e20280 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!NtAlpcOpenSenderThread+42
BUCKET_ID: X64_0x3B_nt!NtAlpcOpenSenderThread+42
Followup: MachineOwner
---------


Debug session time: Fri Jan 1 22:06:59.931 2010 (GMT+8)
System Uptime: 0 days 2:03:23.430
*******************************************************************************
* *
* 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: fffffa900a0575c8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa6002f2d1b0, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c89080
fffffa900a0575c8
CURRENT_IRQL: 2
FAULTING_IP:
dxgkrnl!VidSchiSelectContextFromThisPriority+30
fffffa60`02f2d1b0 498bb4edd8050000 mov rsi,qword ptr [r13+rbp*8+5D8h]
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffffa600531c990 -- (.trap 0xfffffa600531c990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800a057000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6002f2d1b0 rsp=fffffa600531cb20 rbp=00000001fffffffe
r8=0000000000000000 r9=0000000000000001 r10=0000000000000003
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgkrnl!VidSchiSelectContextFromThisPriority+0x30:
fffffa60`02f2d1b0 498bb4edd8050000 mov rsi,qword ptr [r13+rbp*8+5D8h] ds:cbf0:00000010`000005c8=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001ab512e to fffff80001ab5390
STACK_TEXT:
fffffa60`0531c848 fffff800`01ab512e : 00000000`0000000a fffffa90`0a0575c8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0531c850 fffff800`01ab400b : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0a057000 : nt!KiBugCheckDispatch+0x6e
fffffa60`0531c990 fffffa60`02f2d1b0 : fffff880`059f2690 00000000`00000001 fffffa80`0a055000 fffffa60`02f295fb : nt!KiPageFault+0x20b
fffffa60`0531cb20 fffffa60`02f2d393 : fffffa80`0a057000 00000000`00000001 00000000`00000001 00000000`ffffffff : dxgkrnl!VidSchiSelectContextFromThisPriority+0x30
fffffa60`0531cb80 fffffa60`02f2ce1b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VidSchiSelectContext+0xef
fffffa60`0531cbf0 fffffa60`02fe7c8d : 00000000`00000000 fffffa80`07e2f5b0 00000000`00000080 fffffa80`0a050010 : dxgkrnl!VidSchiScheduleCommandToRun+0xbb
fffffa60`0531cd10 fffff800`01cd8de3 : fffffa80`09f82a60 fffff800`01aaf677 00000000`00000000 00000000`00000001 : dxgkrnl!VidSchiWorkerThread+0x95
fffffa60`0531cd50 fffff800`01aef536 : fffff800`01bd4680 fffffa80`09f82a60 fffff800`01bd9b80 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`0531cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!VidSchiSelectContextFromThisPriority+30
fffffa60`02f2d1b0 498bb4edd8050000 mov rsi,qword ptr [r13+rbp*8+5D8h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgkrnl!VidSchiSelectContextFromThisPriority+30
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 479193e6
FAILURE_BUCKET_ID: X64_0xD1_dxgkrnl!VidSchiSelectContextFromThisPriority+30
BUCKET_ID: X64_0xD1_dxgkrnl!VidSchiSelectContextFromThisPriority+30
Followup: MachineOwner
---------



Debug session time: Fri Jan 1 23:00:08.896 2010 (GMT+8)
System Uptime: 0 days 0:06:21.008
*******************************************************************************
* *
* 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: fffffa6002fdc740, The address that the exception occurred at
Arg3: fffffa6001b9a778, Exception Record Address
Arg4: fffffa6001b9a150, 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:
dxgkrnl!VIDMM_SEGMENT::TrimAllProcesses+1d8
fffffa60`02fdc740 483901 cmp qword ptr [rcx],rax
EXCEPTION_RECORD: fffffa6001b9a778 -- (.exr 0xfffffa6001b9a778)
ExceptionAddress: fffffa6002fdc740 (dxgkrnl!VIDMM_SEGMENT::TrimAllProcesses+0x00000000000001d8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000003c200
Attempt to read from address 000000000003c200
CONTEXT: fffffa6001b9a150 -- (.cxr 0xfffffa6001b9a150)
rax=0000000000010821 rbx=000000000000000c rcx=000000000003c200
rdx=fffffa8009eff910 rsi=fffff88009d4fb50 rdi=fffffa800acf83a0
rip=fffffa6002fdc740 rsp=fffffa6001b9a9b0 rbp=fffff88005a2c840
r8=0000000000000000 r9=0000000000000006 r10=fffff880081b8810
r11=0000000000000001 r12=fffff880081b8770 r13=00000000c01e0100
r14=fffff88009435220 r15=fffffa800a73e950
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgkrnl!VIDMM_SEGMENT::TrimAllProcesses+0x1d8:
fffffa60`02fdc740 483901 cmp qword ptr [rcx],rax ds:002b:00000000`0003c200=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: COMMON_SYSTEM_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: 000000000003c200
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c89080
000000000003c200
FOLLOWUP_IP:
dxgkrnl!VIDMM_SEGMENT::TrimAllProcesses+1d8
fffffa60`02fdc740 483901 cmp qword ptr [rcx],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa6002fdc8c3 to fffffa6002fdc740
STACK_TEXT:
fffffa60`01b9a9b0 fffffa60`02fdc8c3 : fffff880`05a2c840 00000000`c01e0100 00000000`00000000 fffffa80`fffff8d3 : dxgkrnl!VIDMM_SEGMENT::TrimAllProcesses+0x1d8
fffffa60`01b9aa60 fffffa60`02fc9c91 : 00000000`000000f9 fffffa60`01b9abb0 00000000`c01e0116 fffffa80`09efe000 : dxgkrnl!VIDMM_SEGMENT::MarkCandidateForEviction+0x7b
fffffa60`01b9aaa0 fffffa60`02fe51c8 : fffffa60`00000000 fffff880`098393d0 fffffa80`00000000 fffffa80`07e13f20 : dxgkrnl!VIDMM_GLOBAL::prepareDmaBuffer+0x539
fffffa60`01b9ab50 fffffa60`02fe4fa4 : fffffa60`017dbcc0 fffffa80`069c4c00 00000000`00000000 fffffa60`00000000 : dxgkrnl!VidSchiSubmitRenderCommand+0x1b0
fffffa60`01b9ace0 fffffa60`02fe4ca9 : 00000000`00000000 fffffa80`0746e750 00000000`00000080 fffffa80`09eb4540 : dxgkrnl!VidSchiSubmitQueueCommand+0x50
fffffa60`01b9ad10 fffff800`01cd8de3 : fffffa80`09e22060 fffff800`01aaf677 fffffa60`0221c850 00000000`00000001 : dxgkrnl!VidSchiWorkerThread+0xb1
fffffa60`01b9ad50 fffff800`01aef536 : fffffa60`017d8180 fffffa80`09e22060 fffffa60`017e1d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`01b9ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgkrnl!VIDMM_SEGMENT::TrimAllProcesses+1d8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 479193e6
STACK_COMMAND: .cxr 0xfffffa6001b9a150 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgkrnl!VIDMM_SEGMENT::TrimAllProcesses+1d8
BUCKET_ID: X64_0x7E_dxgkrnl!VIDMM_SEGMENT::TrimAllProcesses+1d8
Followup: MachineOwner
---------


Debug session time: Mon Jan 4 19:29:17.940 2010 (GMT+8)
System Uptime: 0 days 1:21:20.932
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904aa
Arg2: fffffa6009ba8098
Arg3: fffffa6009ba7a70
Arg4: fffffa60010eec03
Debugging Details:
------------------

EXCEPTION_RECORD: fffffa6009ba8098 -- (.exr 0xfffffa6009ba8098)
ExceptionAddress: fffffa60010eec03 (Ntfs!NtOfsSetLength+0x00000000000000c3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000009ba8330
Attempt to write to address 0000000009ba8330
CONTEXT: fffffa6009ba7a70 -- (.cxr 0xfffffa6009ba7a70)
rax=0000000030810000 rbx=fffff8800064f710 rcx=0000000009ba8330
rdx=fffffa800b2b84c0 rsi=00000000307a5268 rdi=fffff8800064f5e0
rip=fffffa60010eec03 rsp=fffffa6009ba82d0 rbp=fffffa6009ba8880
r8=0000000000000000 r9=fffffa80093bb380 r10=0000000000000000
r11=fffffa6009ba82a0 r12=00000000307a5200 r13=fffffa8007673290
r14=0000000000000000 r15=fffffa80093891e0
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
Ntfs!NtOfsSetLength+0xc3:
fffffa60`010eec03 488901 mov qword ptr [rcx],rax ds:002b:00000000`09ba8330=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: GSvr.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000009ba8330
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c71080
0000000009ba8330
FOLLOWUP_IP:
Ntfs!NtOfsSetLength+c3
fffffa60`010eec03 488901 mov qword ptr [rcx],rax
FAULTING_IP:
Ntfs!NtOfsSetLength+c3
fffffa60`010eec03 488901 mov qword ptr [rcx],rax
BUGCHECK_STR: 0x24
DEVICE_OBJECT: fffffa800896fa58
LAST_CONTROL_TRANSFER: from fffffa60010efa47 to fffffa60010eec03
STACK_TEXT:
fffffa60`09ba82d0 fffffa60`010efa47 : fffffa80`07673290 fffffa80`0760f180 fffffa80`07673290 00000000`00000058 : Ntfs!NtOfsSetLength+0xc3
fffffa60`09ba83d0 fffffa60`010ee654 : fffffa80`07673290 00000000`00000001 00000000`307a5210 fffffa80`085bb000 : Ntfs!NtOfsPutData+0x57
fffffa60`09ba8510 fffffa60`010ef8ee : fffffa80`07673290 fffffa60`09ba8800 fffffa80`07673310 00000000`00000001 : Ntfs!NtfsWriteFcbUsnRecordToJournal+0xa4
fffffa60`09ba85d0 fffffa60`01018837 : 00000000`00000000 fffffa80`0760f180 fffff880`0648c010 fffff880`0648c140 : Ntfs!NtfsWriteUsnJournalChanges+0x15e
fffffa60`09ba8650 fffffa60`0101b118 : fffffa80`07673290 fffffa80`0896f670 fffffa60`09ba8800 fffffa60`09ba8800 : Ntfs!NtfsCommonWrite+0xdd7
fffffa60`09ba8850 fffffa60`00a06e17 : fffffa80`0896fa10 fffffa80`0896f670 fffffa80`09e7ade0 fffffa80`085bb010 : Ntfs!NtfsFsdWrite+0x208
fffffa60`09ba8910 fffffa60`00a060dd : fffffa80`0896f670 fffffa80`0881e590 fffffa80`09e7ad01 fffffa60`09ba8af8 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`09ba8980 fffffa60`00aa6dd4 : fffffa80`0896f670 00000000`025ff8bc fffffa80`0896f670 00000000`00000001 : fltmgr!FltpDispatch+0xcd
fffffa60`09ba89e0 fffffa80`0896f670 : 00000000`025ff8bc fffffa80`0896f670 00000000`00000001 fffffa60`09ba8b48 : mfehidk+0x47dd4
fffffa60`09ba89e8 00000000`025ff8bc : fffffa80`0896f670 00000000`00000001 fffffa60`09ba8b48 fffffa80`09e7ade0 : 0xfffffa80`0896f670
fffffa60`09ba89f0 fffffa80`0896f670 : 00000000`00000001 fffffa60`09ba8b48 fffffa80`09e7ade0 fffffa80`093a1580 : 0x25ff8bc
fffffa60`09ba89f8 00000000`00000001 : fffffa60`09ba8b48 fffffa80`09e7ade0 fffffa80`093a1580 fffffa80`09e7ade0 : 0xfffffa80`0896f670
fffffa60`09ba8a00 fffffa60`09ba8b48 : fffffa80`09e7ade0 fffffa80`093a1580 fffffa80`09e7ade0 fffffa80`0896f670 : 0x1
fffffa60`09ba8a08 fffffa80`09e7ade0 : fffffa80`093a1580 fffffa80`09e7ade0 fffffa80`0896f670 fffffa80`0896fa10 : 0xfffffa60`09ba8b48
fffffa60`09ba8a10 fffffa80`093a1580 : fffffa80`09e7ade0 fffffa80`0896f670 fffffa80`0896fa10 ff0b0101`55555555 : 0xfffffa80`09e7ade0
fffffa60`09ba8a18 fffffa80`09e7ade0 : fffffa80`0896f670 fffffa80`0896fa10 ff0b0101`55555555 fffffa80`09389350 : 0xfffffa80`093a1580
fffffa60`09ba8a20 fffffa80`0896f670 : fffffa80`0896fa10 ff0b0101`55555555 fffffa80`09389350 fffffa80`0896f670 : 0xfffffa80`09e7ade0
fffffa60`09ba8a28 fffffa80`0896fa10 : ff0b0101`55555555 fffffa80`09389350 fffffa80`0896f670 fffff800`01d2c32c : 0xfffffa80`0896f670
fffffa60`09ba8a30 ff0b0101`55555555 : fffffa80`09389350 fffffa80`0896f670 fffff800`01d2c32c 00000000`00000001 : 0xfffffa80`0896fa10
fffffa60`09ba8a38 fffffa80`09389350 : fffffa80`0896f670 fffff800`01d2c32c 00000000`00000001 00000000`00000000 : 0xff0b0101`55555555
fffffa60`09ba8a40 fffffa80`0896f670 : fffff800`01d2c32c 00000000`00000001 00000000`00000000 fffffa80`093a3bc0 : 0xfffffa80`09389350
fffffa60`09ba8a48 fffff800`01d2c32c : 00000000`00000001 00000000`00000000 fffffa80`093a3bc0 00000000`00000003 : 0xfffffa80`0896f670
fffffa60`09ba8a50 fffff800`01d2b37f : fffffa80`0896fa58 00000000`00000000 fffffa80`0881e590 fffffa60`09ba8ca0 : nt!IopSynchronousServiceTail+0x13c
fffffa60`09ba8ab0 fffff800`01a9ce33 : 00000000`00000201 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x7ee
fffffa60`09ba8bb0 00000000`75033917 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0022f0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75033917

SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Ntfs!NtOfsSetLength+c3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 479190d1
STACK_COMMAND: .cxr 0xfffffa6009ba7a70 ; kb
FAILURE_BUCKET_ID: X64_0x24_INVALID_STACK_ACCESS_Ntfs!NtOfsSetLength+c3
BUCKET_ID: X64_0x24_INVALID_STACK_ACCESS_Ntfs!NtOfsSetLength+c3
Followup: MachineOwner
---------
 
Yeah seems all over the place.

Try taking out half your RAM and running with that for a while. Then put in the other half and see if it only errors with one of the combinations.
 
Thanks Florin, will try that for a while and let you know what happens n_n. Thankyou again for the help and suggestions. The people I bought it from have been less then helpful :love:
 
You must log in or register to reply here.

Similar threads

A
Mysterious crashes on a computer whose components all seem fine
2
Replies
29
Views
3K
Alexko
A
Rys
Reopening Architecture and Products + rules and guidelines changes
3 4 5
Replies
90
Views
16K
Shifty Geezer
Shifty Geezer
2
System service exception BSOD
Replies
7
Views
9K
ShaidarHaran
S
G
Samsung SyncMaster S27A850D Mini-review
Replies
2
Views
8K
Grall
G
G
Logitech G700 Mouse Review
2
Replies
20
Views
12K
Grall
G
Back
Top