Help. New at this computer stuff. Can someone help

Cball444

New member
Local time
4:27 PM
Messages
9
I'm not really computer savvy. Could someone explain to me a easy way to fix my blue screen thing and to find my mini dump folder. Sorry if I'm posting in the wrong place I'm sort of new at this
 

My Computer

OS
Windows 7

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Systems by SmartEyeball
OS
8 Pro x64
CPU
i7 3770K 4.6GHz
Motherboard
ASUS P8Z77 WS
Memory
16GB G.Skill Trident X 2666mhz
Graphics Card(s)
x2 EVGA 780 Ti Superclocked SLI
Sound Card
SB X-FI Surround 5.1 PRO USB / ATH-AD900 Headphones
Monitor(s) Displays
x3 Dell U2410 / 58" Samsung
Screen Resolution
5760*1200/ 1920*1200
Hard Drives
2x Intel 520 240GB (RAID 0) * 2x WD Caviar Blacks 2TB (RAID 0) * 2TB WD Caviar Black * Sony Optirac DVD
PSU
Silverstone Strider Evolution 1200W
Case
Thermaltake Level 10 GT Snow Edition
Cooling
Noctua NH-D14
Keyboard
Topre Realforce // Ducky Shine MX Black // Filco Ninja TKL
Mouse
Thermaltake Theron (Highly Recommended) + Razer Imperator
Antivirus
MSE
Browser
IE, FF, WaterFox
Other Info
GT Extreme V2 Sim Racing Cockpit + 40" LCD and K/B Mouse stand ▼
Fanatec CSR Elite Wheel + Clubsport V1 Pedals + CSR shifter/7G-H ▼Saitek X52 Pro ▼ TrackIR 5 Pro
Buttkicker v2 Seat Rumbler with Dedicated 5.1 and Sub Woofer attached to frame ▼
=
Bloody Big Grin
How do I save the file into Documents?

The thing says searching for driver?
 

My Computer

OS
Windows 7
I need help with the fourth step. What do i do to make it a zip?
 

My Computer

OS
Windows 7
Is Windows 7 . . . - x64 - Dont know what OS means :o - Full retaul - What is the age of system (hardware)? Got it in 2011 - What is the age of OS installation (have you re-installed the OS?) No I dont think so

So I get BSOD and it sometimes says IQRL_Not_Less_Or_Equal

And did I do the zip okay?
 

My Computer

OS
Windows 7
Add on:
Code:
updater.exe	c:\program files (x86)\ask.com\updater\updater.exe	4780	8	200	1380	3/6/2012 10:33 PM	1.2.0.20007	1.33 MB (1,391,272 bytes)	1/3/2012 4:31 PM


Antivirus software:
Code:
mcagent.exe	c:\program files\mcafee.com\agent\mcagent.exe	4296	8	200	1380	3/6/2012 10:33 PM	10.5.216.0	1.42 MB (1,484,856 bytes)	9/30/2010 2:10 PM


Code:
[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Cball444\Windows_NT6_BSOD_jcgriff2\030612-29234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`046634c0?
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20826.amd64fre.win7_ldr.101026-1502
Machine Name:
Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03047eb0
Debug session time: Tue Mar  6 18:44:18.005 2012 (UTC - 7:00)
System Uptime: 0 days 0:16:53.067
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800a738060, fffff800046634d8, fffffa800c2646b0}

Unable to load image \SystemRoot\system32\DRIVERS\ks.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
Probably caused by : usbccgp.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800a738060, Physical Device Object of the stack
Arg3: fffff800046634d8, Functional Device Object of the stack
Arg4: fffffa800c2646b0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa800a735ce0

IMAGE_NAME:  usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9152cd

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff88007dc4000 usbccgp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`04663488 fffff800`02eef183 : 00000000`0000009f 00000000`00000003 fffffa80`0a738060 fffff800`046634d8 : nt!KeBugCheckEx
fffff800`04663490 fffff800`02e85836 : fffff800`046635c0 fffff800`046635c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x23880
fffff800`04663530 fffff800`02e84b26 : fffffa80`0b42e168 fffffa80`0b42e168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`046635a0 fffff800`02e8575e : 00000002`5bd5d7f4 fffff800`04663c18 00000000`0000fdab fffff800`02ff87e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04663bf0 fffff800`02e84e97 : fffff800`02ff4ec3 fffffa80`0000fdab 00000000`7ba01ba9 00000000`000000ab : nt!KiTimerExpiration+0x1be
fffff800`04663c90 fffff800`02e81efa : fffff800`02ff4e80 fffff800`03002cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04663d40 00000000`00000000 : fffff800`04664000 fffff800`0465e000 fffff800`04663d00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_usbccgp.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_usbccgp.sys

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

[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\Cball444\Windows_NT6_BSOD_jcgriff2\030612-32604-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20826.amd64fre.win7_ldr.101026-1502
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`0308ceb0
Debug session time: Tue Mar  6 18:27:01.665 2012 (UTC - 7:00)
System Uptime: 0 days 0:03:11.101
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000096, fffff80002e985fa, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+1ba )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff80002e985fa, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


OVERLAPPED_MODULE: Address regions for 'luafv' and 'RtsUStor.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
nt!KeStackAttachProcess+1ba
fffff800`02e985fa 0f22d8          mov     cr3,rax

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

BUGCHECK_STR:  0x1E_c0000096

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880088b57c8 -- (.exr 0xfffff880088b57c8)
ExceptionAddress: fffff80002e985fa (nt!KeStackAttachProcess+0x00000000000001ba)
   ExceptionCode: c0000096
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff880088b5870 -- (.trap 0xfffff880088b5870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800b8593a0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e985fa rsp=fffff880088b5a00 rbp=fffff880088b5b58
 r8=0000000000000000  r9=fffffa8004ee5450 r10=0000000000000001
r11=fffff800030bfbc0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeStackAttachProcess+0x1ba:
fffff800`02e985fa 0f22d8          mov     cr3,rax
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002eff7a9 to fffff80002ebe580

STACK_TEXT:  
fffff880`088b4ff8 fffff800`02eff7a9 : 00000000`0000001e ffffffff`c0000096 fffff800`02e985fa 00000000`00000000 : nt!KeBugCheckEx
fffff880`088b5000 fffff800`02ebdbc2 : fffff880`088b57c8 fffffa80`0b1fe040 fffff880`088b5870 fffffa80`0b8beba0 : nt!KiDispatchException+0x1b9
fffff880`088b5690 fffff800`02ebc4ca : fffff880`088b58b0 fffff8a0`02678920 00000000`000000a8 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`088b5870 fffff800`02e985fa : 00000000`00000000 fffffa80`0b1fe040 fffffa80`0b1fe040 fffff800`031925db : nt!KiGeneralProtectionFault+0x10a
fffff880`088b5a00 fffffa80`07e119a0 : fffff880`088b5b80 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeStackAttachProcess+0x1ba
fffff880`088b5a80 fffff880`088b5b80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07e119a0
fffff880`088b5a88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`088b5b80


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeStackAttachProcess+1ba
fffff800`02e985fa 0f22d8          mov     cr3,rax

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KeStackAttachProcess+1ba

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc792b2

FAILURE_BUCKET_ID:  X64_0x1E_c0000096_nt!KeStackAttachProcess+1ba

BUCKET_ID:  X64_0x1E_c0000096_nt!KeStackAttachProcess+1ba

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

[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\Cball444\Windows_NT6_BSOD_jcgriff2\030612-28579-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20826.amd64fre.win7_ldr.101026-1502
Machine Name:
Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`03099eb0
Debug session time: Tue Mar  6 17:05:23.278 2012 (UTC - 7:00)
System Uptime: 0 days 0:02:18.714
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffffa800b0745b6, fffff8800848aa28, fffff8800848a290}

Probably caused by : ntkrnlmp.exe ( nt!KxStartSystemThread+16 )

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

0: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffffa800b0745b6, The address that the exception occurred at
Arg3: fffff8800848aa28, Exception Record Address
Arg4: fffff8800848a290, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
+16
fffffa80`0b0745b6 ff              ???

EXCEPTION_RECORD:  fffff8800848aa28 -- (.exr 0xfffff8800848aa28)
ExceptionAddress: fffffa800b0745b6
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff8800848a290 -- (.cxr 0xfffff8800848a290)
rax=0000000000000081 rbx=000000000b07455b rcx=00000000000739f0
rdx=fffffa80090a7911 rsi=fffffa800b170040 rdi=00000000000739f0
rip=fffffa800b0745b6 rsp=fffff8800848ac68 rbp=fffff80003071658
 r8=fffff80003071670  r9=fffff8800848aca8 r10=0000000000000001
r11=fffffa800b170348 r12=fffffa800c55db80 r13=0000000000000001
r14=fffff8800848aca8 r15=0000000000000001
iopl=0         nv up di ng nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010086
fffffa80`0b0745b6 ff              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

LAST_CONTROL_TRANSFER:  from fffff80002ed8981 to fffffa800b0745b6

FAILED_INSTRUCTION_ADDRESS: 
+16
fffffa80`0b0745b6 ff              ???

STACK_TEXT:  
fffff880`0848ac68 fffff800`02ed8981 : fffffa80`0bd206f0 fffff800`02e71240 fffffa80`54515750 fffffa80`0b170040 : 0xfffffa80`0b0745b6
fffff880`0848ac70 fffff800`0316fb56 : 00000000`0fed73df fffffa80`0b170040 00000000`00000080 fffffa80`04ee5450 : nt!ExpWorkerThread+0x111
fffff880`0848ad00 fffff800`02ea8126 : fffff800`03046e80 fffffa80`0b170040 fffff800`03054cc0 fffff880`0141e2b4 : nt!PspSystemThreadStartup+0x5a
fffff880`0848ad40 00000000`00000000 : fffff880`0848b000 fffff880`08485000 fffff880`0848a770 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP: 
nt!KxStartSystemThread+16
fffff800`02ea8126 48c7c10e000000  mov     rcx,0Eh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KxStartSystemThread+16

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc792b2

STACK_COMMAND:  .cxr 0xfffff8800848a290 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_nt!KxStartSystemThread+16

BUCKET_ID:  X64_0x7E_BAD_IP_nt!KxStartSystemThread+16

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

[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\Cball444\Windows_NT6_BSOD_jcgriff2\030612-28392-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20826.amd64fre.win7_ldr.101026-1502
Machine Name:
Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`03048eb0
Debug session time: Tue Mar  6 16:57:31.227 2012 (UTC - 7:00)
System Uptime: 0 days 0:02:53.663
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {7710a, 2, 1, fffff80002e54555}

Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000007710a, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e54555, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b30e0
 000000000007710a 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeStackAttachProcess+115
fffff800`02e54555 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88008bd5870 -- (.trap 0xfffff88008bd5870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=fffffa800b5a7bc0
rdx=fffff88008bd5b58 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e54555 rsp=fffff88008bd5a00 rbp=fffff88008bd5b58
 r8=fffffa800b5a7bb0  r9=0000000000000130 r10=fffff880031650c0
r11=fffffa800b5a7b60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeStackAttachProcess+0x115:
fffff800`02e54555 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax ds:7430:00000000`000000dc=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e79ae9 to fffff80002e7a580

STACK_TEXT:  
fffff880`08bd5728 fffff800`02e79ae9 : 00000000`0000000a 00000000`0007710a 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08bd5730 fffff800`02e78760 : 00000000`00000001 00000000`0007710a 00000000`00000000 fffffa80`0b5a7b60 : nt!KiBugCheckDispatch+0x69
fffff880`08bd5870 fffff800`02e54555 : 00000000`00000000 fffffa80`0b5a7b60 fffffa80`0b5a7b60 fffff800`0314e5db : nt!KiPageFault+0x260
fffff880`08bd5a00 fffffa80`07e529a0 : fffff880`08bd5b80 fffffa80`07707a00 fffffa80`056e9b80 00000000`00000000 : nt!KeStackAttachProcess+0x115
fffff880`08bd5a80 fffff880`08bd5b80 : fffffa80`07707a00 fffffa80`056e9b80 00000000`00000000 00000000`00000000 : 0xfffffa80`07e529a0
fffff880`08bd5a88 fffffa80`07707a00 : fffffa80`056e9b80 00000000`00000000 00000000`00000000 fffffa80`0a9f4060 : 0xfffff880`08bd5b80
fffff880`08bd5a90 fffffa80`056e9b80 : 00000000`00000000 00000000`00000000 fffffa80`0a9f4060 00000000`00000003 : 0xfffffa80`07707a00
fffff880`08bd5a98 00000000`00000000 : 00000000`00000000 fffffa80`0a9f4060 00000000`00000003 fffff880`01b5553c : 0xfffffa80`056e9b80


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeStackAttachProcess+115
fffff800`02e54555 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeStackAttachProcess+115

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc792b2

FAILURE_BUCKET_ID:  X64_0xA_nt!KeStackAttachProcess+115

BUCKET_ID:  X64_0xA_nt!KeStackAttachProcess+115

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


[/list]
  1. This crash is due to the system sending a device driver the signal to turn itself off or turn itself on during a power cycle such as during sleep, hibernate, shut down, or startup. The device or device driver failed to respond to the signal and so the system crashed to force the power state. Could be caused by either the devices themselves or their drivers. Probably USB device related.
  2. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
    Thanks to JMH for helping with my understanding of this crash.
  3. Possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
  4. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.





If that is too much at once, we can narrow it down and do one step at a time.
 
Last edited:

My Computer

Computer Manufacturer/Model Number
HP Pavilion e9110t
OS
Windows 7 Home Premium 64 Bit
CPU
Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
Motherboard
Pegatron IPIEL-LA3
Memory
6.00 GB Hundai HMT125U6BFR8C-H9
Graphics Card(s)
ATI Radeon HD 4850
Sound Card
Realtek High Definition Audio/ATI High Definition Audio
Monitor(s) Displays
Acer AL2216W
Screen Resolution
1680x1050
Hard Drives
Hitachi HDP725050GLA360 ATA Device 500 GB
PSU
Unknown/installed by HP
Case
HP generic case
Cooling
Intel Stock Cooling
Keyboard
HP Keyboard
Mouse
HP Mouse
Internet Speed
Download: 19.15 Mbps Upload: 1.67 Mbps
Other Info
Network Adapter Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Network Adapter 802.11n Wireless PCI Express Card LAN Adapter
Im a little confused. Im to computer dumb to know this. Can you dumb it down for me?
 

My Computer

OS
Windows 7
Alright, I am going to leave that last post up so other helpers know what is going on. For you, I am going to simplify the steps a bit.

Remove the ask toolbar through Start Menu -> Control Panel -> Uninstall a program
  1. Click the Start Menu
  2. Click Control Panel (it is on the right in the third group of items)
  3. Click Uninstall a program (under Programs on the left hand side at the bottom)
  4. You will see a list in alphabetical order. You may have to give it 10-20 seconds to load completely.
  5. Choose the ask toolbar or ask.com or however it shows up (it will have "ask" in the name); choose by clicking on the item.
  6. Click the Uninstall button. If asked if you are sure, proceed acknowledging that you want to continue.
 

My Computer

Computer Manufacturer/Model Number
HP Pavilion e9110t
OS
Windows 7 Home Premium 64 Bit
CPU
Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
Motherboard
Pegatron IPIEL-LA3
Memory
6.00 GB Hundai HMT125U6BFR8C-H9
Graphics Card(s)
ATI Radeon HD 4850
Sound Card
Realtek High Definition Audio/ATI High Definition Audio
Monitor(s) Displays
Acer AL2216W
Screen Resolution
1680x1050
Hard Drives
Hitachi HDP725050GLA360 ATA Device 500 GB
PSU
Unknown/installed by HP
Case
HP generic case
Cooling
Intel Stock Cooling
Keyboard
HP Keyboard
Mouse
HP Mouse
Internet Speed
Download: 19.15 Mbps Upload: 1.67 Mbps
Other Info
Network Adapter Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Network Adapter 802.11n Wireless PCI Express Card LAN Adapter

My Computer

Computer Manufacturer/Model Number
HP Pavilion e9110t
OS
Windows 7 Home Premium 64 Bit
CPU
Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
Motherboard
Pegatron IPIEL-LA3
Memory
6.00 GB Hundai HMT125U6BFR8C-H9
Graphics Card(s)
ATI Radeon HD 4850
Sound Card
Realtek High Definition Audio/ATI High Definition Audio
Monitor(s) Displays
Acer AL2216W
Screen Resolution
1680x1050
Hard Drives
Hitachi HDP725050GLA360 ATA Device 500 GB
PSU
Unknown/installed by HP
Case
HP generic case
Cooling
Intel Stock Cooling
Keyboard
HP Keyboard
Mouse
HP Mouse
Internet Speed
Download: 19.15 Mbps Upload: 1.67 Mbps
Other Info
Network Adapter Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Network Adapter 802.11n Wireless PCI Express Card LAN Adapter
I got this when it restarted my computer
 

My Computer

OS
Windows 7

My Computer

Computer Manufacturer/Model Number
HP Pavilion e9110t
OS
Windows 7 Home Premium 64 Bit
CPU
Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
Motherboard
Pegatron IPIEL-LA3
Memory
6.00 GB Hundai HMT125U6BFR8C-H9
Graphics Card(s)
ATI Radeon HD 4850
Sound Card
Realtek High Definition Audio/ATI High Definition Audio
Monitor(s) Displays
Acer AL2216W
Screen Resolution
1680x1050
Hard Drives
Hitachi HDP725050GLA360 ATA Device 500 GB
PSU
Unknown/installed by HP
Case
HP generic case
Cooling
Intel Stock Cooling
Keyboard
HP Keyboard
Mouse
HP Mouse
Internet Speed
Download: 19.15 Mbps Upload: 1.67 Mbps
Other Info
Network Adapter Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Network Adapter 802.11n Wireless PCI Express Card LAN Adapter
Back
Top