1.

Solve : Blue Screens of Death in Vista after a while?

Answer»

Hello, I am having some very annoying problems. My computer, a custom built pc, keeps getting the bsod after i leave it on for about 8 hours or so. It doesn't matter what programs I have running, it will just crash after a while. I have ran memtest86 on each individual stick of my RAM and have found no errors. The bsod is usually a 0x0000003B win32.sys or csrss.exe SYSTEM_SERVICE_EXCEPTION . I have ran hard drive tests on my main hard drive and have found nothing. I have installed a hard drive cooler on one of my hard drives with no effect towards system stability. I'm not quite sure what to do. Below are my pc specs and then I have the debugging information from the memory dump (a large one, not a minidump).

Specs:

CPU: Intel Q9450
Motherboard: Gigabyte EP35-DS3R
Memory: Two sets of CORSAIR DOMINATOR 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066
Power Supply: Antec TPQ-850 850W ATX12V / EPS12V Power Supply
Case: NZXT Zero Black/Silver Aluminum ATX Full Tower Computer Case
Graphics Card: MSI RX3870-T2D512E OC Radeon HD 3870 512MB 256-bit GDDR4 PCI Express 2.0
O/S: Windows Vista Ultimate 64-bit
Hard Drives: 1.Seagate 750gb SATA
                    2.Samsung 750gb SATA
                    3.Western Digital 500gb SATA
                    4. Western Digital 320 SATA (main hard drive with Windows Vista on it)

Debugging Information:

Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd3018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001a4815, fffffa60059c3ff0, 0}

Page a8310 not present in the dump file. Type ".hh dbgerr004" for details
Page a85a9 not present in the dump file. Type ".hh dbgerr004" for details
Page a85a9 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd3018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd3018).  Type ".hh dbgerr001" for details
Probably caused by : hardware ( win32k!memmove+5 )

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: fffff960001a4815, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffa60059c3ff0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

Page a85a9 not present in the dump file. Type ".hh dbgerr004" for details
Page a85a9 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd3018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd3018).  Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
win32k!memmove+5
fffff960`001a4815 d10f            ror     dword ptr [rdi],1

CONTEXT:  fffffa60059c3ff0 -- (.cxr 0xfffffa60059c3ff0)
rax=00000000ffffffff rbx=000002f60000014c rcx=fffff9600036e074
rdx=fffff900c00e537c rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001a4815 rsp=fffffa60059c4858 rbp=0000000000000000
 r8=0000000000000018  r9=0000000000000001 r10=0000000000000008
r11=fffff9600036e074 r12=0000000000000000 r13=fffffa800a353810
r14=fffff80002141700 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!memmove+0x5:
fffff960`001a4815 d10f            ror     dword ptr [rdi],1 ds:002b:00000000`00000000=??
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

MISALIGNED_IP:
win32k!memmove+5
fffff960`001a4815 d10f            ror     dword ptr [rdi],1

LAST_CONTROL_TRANSFER:  from fffff960001d32e6 to fffff960001a4815

STACK_TEXT: 
fffffa60`059c4858 fffff960`001d32e6 : 00000000`00000000 000002f6`0000014c fffffa80`0a353810 00000000`00000000 : win32k!memmove+0x5
fffffa60`059c4860 fffff960`001d39f1 : fffff900`c00e537c 00000000`0052ce47 fffff900`c00e52f0 fffff900`c00e52f0 : win32k!QueueMouseEvent+0x122
fffffa60`059c4890 fffff960`001d3789 : fffff900`c00e52f0 000002f6`0000014c fffffa80`0813fc88 00000000`00000246 : win32k!ProcessMouseInput+0x24d
fffffa60`059c4900 fffff800`01ecd5a0 : fffffa80`0a5c0890 fffffa80`0a5c0890 00000000`00000000 00000000`00000000 : win32k!InputApc+0xd5
fffffa60`059c4930 fffff800`01ea9121 : 00000000`00000000 00000000`00000000 fffff960`001d36b4 00000000`00000000 : nt!KiDeliverApc+0x420
fffffa60`059c49d0 fffff800`01ea8596 : 00000000`00000002 00000000`0000000f fffff960`00000002 fffffa80`00000009 : nt!KiSwapThread+0x491
fffffa60`059c4a40 fffff960`0016c1f2 : fffff900`00000002 fffff900`c00e75b0 fffffa60`00000001 fffffa60`0000000d : nt!KeWaitForMultipleObjects+0x2d6
fffffa60`059c4ac0 fffff960`0016c545 : 00000000`00000000 fffff900`c00e75b0 00000000`00000004 fffff960`0036d5e0 : win32k!xxxMsgWaitForMultipleObjects+0x102
fffffa60`059c4b40 fffff960`0013cb53 : fffffa80`00000001 fffffa60`0000000c fffffa80`0a5c0890 fffffa80`0a353810 : win32k!xxxDesktopThread+0x272
fffffa60`059c4bc0 fffff960`001b5046 : fffffa80`00000001 fffff960`0036d5e0 00000000`00000000 00000000`00000000 : win32k!xxxCreateSystemThreads+0x73
fffffa60`059c4bf0 fffff800`01ea2e33 : fffffa80`0a5c0890 00000000`00000004 000007fe`fd618b60 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffffa60`059c4c20 000007fe`fd56bbda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`009ff828 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd56bbda


FOLLOWUP_IP:
win32k!memmove+5
fffff960`001a4815 d10f            ror     dword ptr [rdi],1

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!memmove+5

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffffa60059c3ff0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Any help would be awesome. Thanks.This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

I found the information above for you ?

I suggest you update your drivers .

SOURCE : http://msdn.microsoft.com/en-us/library/ms793232.aspx

All drivers, including the graphics driver are up to date. Try reinstalling them.You wouldn't, by chance, have hibernation enabled...would you?

Make sure you have the latest Service packs and updates from Windows for this particular operating system.Hibernation is DISABLED and has been. I tested something last NIGHT and now I believe it only crashes if a program is running. I don't think it MATTERS which program, but I'm not 100% on this theory yet. I know it crashes when Utorrent is running, but it has also CRASHED with Window's DVD Maker. Also, I have recently disable Windows Sidebar so that could possibly have something to do with it. I will be testing all of these ideas. My graphics driver was updated to the newest version after this problem started so I don't really think reinstalling the driver for it will help, but I will try it. Thanks for you help.Is the operating system up to date?...as far as Service Packs and patches?Yes, the installation dvd came with SP1 on it and all patches/updates have been downloaded.Then, you're probably correct that another software program is causing it.  Could be a conflict with the Vista OS.  Seems to be a lot of that going around.

Keep us posted...



Discussion

No Comment Found