login to windows BSOD

The Carnage · 06 Jul 2011

been getting a BSOD as windows logs in and start up programs start, not sure if it's 1 of them or something else...
seems to only be after I have left the comp off for a while like when I go to bed-then work then turn it on, so like 15+ hours, it does not crash if I just restart...

I am running Intel smart response cache technology and the CPU is OC'd to 4G from 3.3G

windows slide show has been turned off as I have a G15 Keyboard and it was giving me errors...

I have also added the files stated would be of help from the "windows did not shut down properly" message I get after I do get into windows after the BSOD (Iknow there in the report but there in a separate folder in the zip anyway..

Thanx for any help any1...

Win 7 Pro x64
Intel Core i5-2500K
Gigabyte Z68X-UD7-B3
Gigabyte ATI HD5850OC 1GB GDDR5
G.Skill Ripjaws 2x2GB DDR3 (1600MHz)
Antec EarthWatts 750W
23.5" Samsung P2350 2ms LCD 16:9 (1920x1080)
Logitech G500
Logitech G15v2

yowanvista · 06 Jul 2011

Uninstall ATI Tools, it is causing issues on your system

Do a System Restore and remove that TunUP Utilities since it could have messed up your system
Windows 7 does not need any 'TuneUp' software or whatsoever related utilities
Run SFC /SCANNOW Command - System File Checker

Run a scan of Malwarebytes

Update your Kasperky product to version 2012
http://www.kaspersky.com/productupdates

Code:

TuneUpUtilitiesDriver64.sys        fffff880`0894d000    fffff880`08955000    0x00008000    0x4ab2238c    17/09/2009 15:54:52

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff87ffb5a4845, 0, fffffa80075a5418, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44891 )


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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebc100
 fffff87ffb5a4845 

FAULTING_IP: 
+0
fffffa80`075a5418 48813c1041544f4d cmp     qword ptr [rax+rdx],4D4F5441h

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  atitray.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009ddd690 -- (.trap 0xfffff88009ddd690)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffff000f845 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8800b595000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa80075a5418 rsp=fffff88009ddd820 rbp=fffffa8003f51350
 r8=00000000800dff00  r9=0000000000000000 r10=0000000000000020
r11=000000000000000e r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffffa80`075a5418 48813c1041544f4d cmp     qword ptr [rax+rdx],4D4F5441h ds:d7d0:fffff87f`fb5a4845=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c373cf to fffff80002c8cd00

STACK_TEXT:  
fffff880`09ddd528 fffff800`02c373cf : 00000000`00000050 fffff87f`fb5a4845 00000000`00000000 fffff880`09ddd690 : nt!KeBugCheckEx
fffff880`09ddd530 fffff800`02c8ae2e : 00000000`00000000 fffff87f`fb5a4845 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44891
fffff880`09ddd690 fffffa80`075a5418 : fffffa80`06d43f00 00000000`00000000 fffffa80`06d43f00 fffffa80`03f51280 : nt!KiPageFault+0x16e
fffff880`09ddd820 fffffa80`06d43f00 : 00000000`00000000 fffffa80`06d43f00 fffffa80`03f51280 00000000`20206f49 : 0xfffffa80`075a5418
fffff880`09ddd828 00000000`00000000 : fffffa80`06d43f00 fffffa80`03f51280 00000000`20206f49 00000000`00000001 : 0xfffffa80`06d43f00


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+44891
fffff800`02c373cf cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+44891

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+44891

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+44891

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