Blue Screens and Random Reboots

[jason786]

I've tried a lot of stuff already
sfc /scannow or whatever it is in cmd

I also left Memtest86 on overnight which ran over 8 passes but there were no memory errors detected

Not sure what else to do

Some help on this would be great

My System Specs are already available for you to see if that helps you guys out at all.

Thanks

 

[CarlTR6]

I will give it a look.

Wow, that is a bunch of dumps. This will take a few minutes.

I looked at the four most recent and I will look at the older ones. Three dmps gave the same error code of A. One gave a 1E error code.

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
BSOD Index


STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
BSOD Index

icrosoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Minidump.zip\Minidump\061310-16629-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c4be50
Debug session time: Sun Jun 13 15:40:40.061 2010 (GMT-4)
System Uptime: 0 days 0:14:47.000
Loading Kernel Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+62ff952f0201d7fc
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002f1b328 -- (.exr 0xfffff88002f1b328)
ExceptionAddress: fffff80002a82fa2 (nt!KiDeferredReadyThread+0x00000000000001c2)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f1b3d0 -- (.trap 0xfffff88002f1b3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff000002c06b80 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a82fa2 rsp=fffff88002f1b560 rbp=0000000000000002
 r8=0000000000000001  r9=000000000000003a r10=fffff80002a0e000
r11=fffff88002f1b5b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiDeferredReadyThread+0x1c2:
fffff800`02a82fa2 663b5048        cmp     dx,word ptr [rax+48h] ds:ffff0000`02c06bc8=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7632e to fffff80002a7e5d0

STACK_TEXT:  
fffff880`02f1a418 fffff800`02a7632e : 00000000`00000000 fffff880`02df09b4 fffff880`02f1ab90 fffff800`02aab524 : nt!KeBugCheck
fffff880`02f1a420 fffff800`02aa42ed : fffff800`02c8cb88 fffff800`02bc5a40 fffff800`02a0e000 fffff880`02f1b328 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1a450 fffff800`02aab950 : fffff800`02bcdb24 fffff880`02f1a4c8 fffff880`02f1b328 fffff800`02a0e000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1a480 fffff800`02ab88df : fffff880`02f1b328 fffff880`02f1ab90 fffff880`00000000 fffffa80`042ccb60 : nt!RtlDispatchException+0x410
fffff880`02f1ab60 fffff800`02a7dc42 : fffff880`02f1b328 fffff880`02f63180 fffff880`02f1b3d0 fffff880`009ec180 : nt!KiDispatchException+0x16f
fffff880`02f1b1f0 fffff800`02a7c54a : fffffa80`03f29c00 fffff880`0417a783 fffffa80`052a6d20 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f1b3d0 fffff800`02a82fa2 : ffffffff`ffb3b4c0 fffffa80`042cb238 00000000`00000000 fffffa80`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1b560 fffff800`02a89ab7 : fffffa80`07557c20 fffffa80`042ccc68 fffffa80`042ccc68 00000000`00000000 : nt!KiDeferredReadyThread+0x1c2
fffff880`02f1b5e0 fffff800`02a8a57e : 00000002`10b18efd fffff880`02f1bc58 00000000`0000de1a fffff880`009ee8c8 : nt!KiProcessExpiredTimerList+0x157
fffff880`02f1bc30 fffff800`02a89d97 : 00000000`7bf78bc3 00000000`0000de1a 00000000`7bf78ba6 00000000`0000001a : nt!KiTimerExpiration+0x1be
fffff880`02f1bcd0 fffff800`02a86dfa : fffff880`009ec180 fffff880`009f6fc0 00000000`00000000 fffff880`04156480 : nt!KiRetireDpcList+0x277
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02a7632e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Minidump.zip\Minidump\061310-21668-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50
Debug session time: Sun Jun 13 15:25:13.430 2010 (GMT-4)
System Uptime: 0 days 10:34:52.475
Loading Kernel Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {18, 2, 1, fffff80002ac8610}

Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+839 )

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

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: 0000000000000018, 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: fffff80002ac8610, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfb0e0
 0000000000000018 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeferredReadyThread+839
fffff800`02ac8610 48895008        mov     qword ptr [rax+8],rdx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff800040e23d0 -- (.trap 0xfffff800040e23d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000010 rbx=0000000000000000 rcx=fffff88002fd7700
rdx=fffffa8005a95100 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ac8610 rsp=fffff800040e2560 rbp=0000000000000003
 r8=0000000000000008  r9=0000000000000008 r10=fffff80002a53000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KiDeferredReadyThread+0x839:
fffff800`02ac8610 48895008        mov     qword ptr [rax+8],rdx ds:0080:00000000`00000018=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ac2b69 to fffff80002ac3600

STACK_TEXT:  
fffff800`040e2288 fffff800`02ac2b69 : 00000000`0000000a 00000000`00000018 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`040e2290 fffff800`02ac17e0 : fffffa80`063cc000 fffff880`02fd3180 fffff800`040e2c58 fffff800`02c40080 : nt!KiBugCheckDispatch+0x69
fffff800`040e23d0 fffff800`02ac8610 : 00000000`00000000 fffff800`02acf6a6 fffff800`040e2600 fffff800`040e2600 : nt!KiPageFault+0x260
fffff800`040e2560 fffff800`02aceab7 : fffffa80`05d03840 fffffa80`05d7cf40 fffffa80`05d7cf40 fffffa80`04b25c00 : nt!KiDeferredReadyThread+0x839
fffff800`040e25e0 fffff800`02acf57e : 00000058`b0e26e0e fffff800`040e2c58 00000000`00254251 fffff800`02c40ca8 : nt!KiProcessExpiredTimerList+0x157
fffff800`040e2c30 fffff800`02aced97 : 00000014`c9b228c2 00000014`00254251 00000014`c9b228a6 00000000`00000051 : nt!KiTimerExpiration+0x1be
fffff800`040e2cd0 fffff800`02acbdfa : fffff800`02c3de80 fffff800`02c4bc40 00000000`00000000 fffff880`03e81480 : nt!KiRetireDpcList+0x277
fffff800`040e2d80 00000000`00000000 : fffff800`040e3000 fffff800`040dd000 fffff800`040e2d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDeferredReadyThread+839
fffff800`02ac8610 48895008        mov     qword ptr [rax+8],rdx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiDeferredReadyThread+839

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+839

BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+839

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

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Minidump.zip\Minidump\061610-15600-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c4be50
Debug session time: Wed Jun 16 04:50:35.330 2010 (GMT-4)
System Uptime: 0 days 1:34:39.000
Loading Kernel Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {190, 2, 0, fffff80002a865db}

Probably caused by : cdrom.sys ( cdrom!RequestSendMcnRequest+5a )

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

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: 0000000000000190, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002a865db, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb60e0
 0000000000000190 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSearchForNewThread+26b
fffff800`02a865db 66453b9080010000 cmp     r10w,word ptr [r8+180h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031c46f0 -- (.trap 0xfffff880031c46f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000100 rbx=0000000000000000 rcx=fffff88002f67700
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a865db rsp=fffff880031c4880 rbp=0000000000000001
 r8=0000000000000010  r9=0000000000000008 r10=0000000000000000
r11=fffff80002bf8e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KiSearchForNewThread+0x26b:
fffff800`02a865db 66453b9080010000 cmp     r10w,word ptr [r8+180h] ds:00000000`00000190=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7db69 to fffff80002a7e600

STACK_TEXT:  
fffff880`031c45a8 fffff800`02a7db69 : 00000000`0000000a 00000000`00000190 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031c45b0 fffff800`02a7c7e0 : 00000000`00000004 00000000`00000000 fffffa80`05af77a0 fffffa80`05af7b01 : nt!KiBugCheckDispatch+0x69
fffff880`031c46f0 fffff800`02a865db : fffffa80`03957500 fffffa80`043fcb80 fffffa80`03957500 fffffa80`039561a0 : nt!KiPageFault+0x260
fffff880`031c4880 fffff800`02a856fc : 00000000`00000000 fffffa80`039df040 00000000`00000000 00000000`00000000 : nt!KiSearchForNewThread+0x26b
fffff880`031c48f0 fffff800`02a878af : 00000000`00000001 00000000`00000000 fffff880`00000000 00000000`002d0900 : nt!KiCommitThreadWait+0x17c
fffff880`031c4980 fffff880`00d5813a : fffffa80`0540a000 fffff880`00000000 fffffa80`051e8a00 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`031c4a20 fffff880`00d6d59f : fffffa80`051e8a20 fffffa80`00000000 00000000`00000000 fffff880`013da5d5 : Wdf01000!FxIoTarget::SubmitSync+0x2c2
fffff880`031c4ad0 fffff880`013f5012 : fffffa80`00000020 fffffa80`0540a020 fffffa80`051e8a20 fffffa80`051b3b80 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`031c4b20 fffff880`013ebdab : fffffa80`052a2aa0 0000057f`f97b2c68 00000000`00000000 fffff880`05122110 : cdrom!RequestSendMcnRequest+0x5a
fffff880`031c4b70 fffff880`00d8a6fb : 00000000`00000000 fffffa80`075ef440 fffffa80`051aec90 fffff800`02c235f8 : cdrom!RequestProcessSerializedIoctl+0x583
fffff880`031c4c50 fffff800`02d7b827 : fffffa80`051e8e20 fffffa80`075ef400 fffffa80`039df040 fffffa80`039df040 : Wdf01000!FxWorkItem::WorkItemThunk+0x113
fffff880`031c4c80 fffff800`02a8b861 : fffff800`02c23500 fffff800`02d7b804 fffffa80`039df040 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`031c4cb0 fffff800`02d23a86 : 00000000`00000000 fffffa80`039df040 00000000`00000080 fffffa80`039cd040 : nt!ExpWorkerThread+0x111
fffff880`031c4d40 fffff800`02a5cb06 : fffff880`02f63180 fffffa80`039df040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031c4d80 00000000`00000000 : fffff880`031c5000 fffff880`031bf000 fffff880`031c49f0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdrom!RequestSendMcnRequest+5a
fffff880`013f5012 8ad8            mov     bl,al

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  cdrom!RequestSendMcnRequest+5a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdrom

IMAGE_NAME:  cdrom.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11a

FAILURE_BUCKET_ID:  X64_0xA_cdrom!RequestSendMcnRequest+5a

BUCKET_ID:  X64_0xA_cdrom!RequestSendMcnRequest+5a

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

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Minidump.zip\Minidump\062010-16333-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50
Debug session time: Sun Jun 20 15:59:07.869 2010 (GMT-4)
System Uptime: 0 days 5:07:31.524
Loading Kernel Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002a7f213}

Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+433 )

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


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: 0000000000000000, 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: fffff80002a7f213, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb20e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeferredReadyThread+433
fffff800`02a7f213 4c8900          mov     qword ptr [rax],r8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  wlcomm.exe

TRAP_FRAME:  fffff880068db920 -- (.trap 0xfffff880068db920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8003bf32b0
rdx=fffff88002fd7710 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a7f213 rsp=fffff880068dbab0 rbp=0000000000000003
 r8=fffffa8003a33ab0  r9=0000000000000009 r10=fffff80002a0a000
r11=00000000001f0003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiDeferredReadyThread+0x433:
fffff800`02a7f213 4c8900          mov     qword ptr [rax],r8 ds:bbc8:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a79b69 to fffff80002a7a600

STACK_TEXT:  
fffff880`068db7d8 fffff800`02a79b69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`068db7e0 fffff800`02a787e0 : 00000000`00000001 fffff880`02fd3180 fffffa80`07784060 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`068db920 fffff800`02a7f213 : 00000000`00002000 00000000`73992450 00000000`73992450 00000000`075ff098 : nt!KiPageFault+0x260
fffff880`068dbab0 fffff800`02a91378 : 00000000`00000000 fffffa80`03a33a10 fffffa80`03a33b18 fffffa80`03a33b18 : nt!KiDeferredReadyThread+0x433
fffff880`068dbb30 fffff800`02d338ee : fffffa80`00000000 00000000`00000001 fffffa80`03a2d240 00000000`002a3500 : nt!KeReleaseSemaphore+0x228
fffff880`068dbbb0 fffff800`02a79853 : fffffa80`07784060 00000000`04e624a8 00000000`00000000 00000000`fff9e001 : nt!NtReleaseSemaphore+0x9e
fffff880`068dbc20 00000000`73992dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`075ff048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73992dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDeferredReadyThread+433
fffff800`02a7f213 4c8900          mov     qword ptr [rax],r8

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiDeferredReadyThread+433

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+433

BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+433

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

The first thing I recommend is to uninstall AVG using this tool: Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity Protection installed, uninstall it using this tool: Info > Tool. Install MSE for troubleshooting purposes. AVG has been know to cause BSOD's on some Win 7 systems. Reboot and see how your system runs.

 

[jason786]

I will give it a look.

Wow, that is a bunch of dumps. This will take a few minutes.

Thanks a lot

Yeah there are a few, they go back to my last format/clean installation

I'm sure there are a variety of BSoDs in the .dmps so I don't know what the problem is myself

 

[CarlTR6]

Jason, refresh your page to make sure you see what I have added.

 

[jason786]

Jason, refresh your page to make sure you see what I have added.

Thanks a lot for helping out,

I did actually uninstall AVG before and then went onto another free virus protection, but now I'm back on AVG now because I found it was best suited to me

However, I will install a different virus protection and report back with my status, thanks for help

Hmm, I installed security essentials, I think its working etc, but each time I open it, it just minimizes, I can't even get it to stay long enough to scan :S

 

[CarlTR6]

Did you use that AVG removal tool? You have to get all traces of it off of your system.

 

[jason786]

Did you use that AVG removal tool? You have to get all traces of it off of your system.

Yes I did

 

[CarlTR6]

Very good. What AV did you install?

 

[jason786]

Very good. What AV did you install?

The last time I did this I put Avast on

At the moment, I'm just running Microsoft Security Essentials

Ok the problem is resolved, I had a program called TrayIt running which seemed to interfere with Security Essentials and caused it to minimize.

I will run the system like this and will check for blue screens or restarts, thanks for your help

 

[CarlTR6]

You are welcome. Thanks for letting us know you resolved the MSE problem. Good detective work. Be sure to post back and let us know how your system is getting along.

 

[jason786]

This morning I decided to run a virus scan, and just now the computer just rebooted itself randomly

I have already disabled automatic restart on system failure but still I didn't receive a blue screen so I don't have a .dmp file

One thing I've noticed is that the blue screen/restarts mainly occur when the PC is under heavy load, like if I'm on a game, or watching a HD video on youtube, it doesn't happen 100% of the time, but usually this is the case

 

[ttran]

I'm guessing third party softwares are messing up your system. I saw that you mentioned something like 'trayit''...that interfere with MSE
Can you please go to Run-->Type in msconfig-->choose startup tab and turn off everything except system process and see if problem goes away

~Tuan

 

[jason786]

I'm guessing third party softwares are messing up your system. I saw that you mentioned something like 'trayit''...that interfere with MSE
Can you please go to Run-->Type in msconfig-->choose startup tab and turn off everything except system process and see if problem goes away

~Tuan

I have clean installed windows plenty of times and the only common software I use is AVG and Firefox (AVG now uninstalled)

However I just got another blue screen, I've attached it to this post, if someone could analyse it that would be great

 

[ttran]

I couldn't see a lot from the minidump file. Can you please enable Driver Verifier. It is driver stress test that will let us know if the BSODs caused by bad driver

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Reboot into Windows, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

 

[CarlTR6]

Your latest dump pointed to Tibia.exe as the cause. That does not necessarily mean it was the cause; it could have conflicted with something else. Tibia.exe belongs to the software Tibia Player or Adobe AIR by CipSoft GmbH. Try to udate this program, in fact make sure all of your Adobe software is updated.

I agree with Tuan, do run driver verifier until it causes a BSOD or for for 24 hours. Carry on your normal computer operations while it is running.

Do a CPU stress test as well, using Prime95.

 

[jason786]

Your latest dump pointed to Tibia.exe as the cause. That does not necessarily mean it was the cause; it could have conflicted with something else. Tibia.exe belongs to the software Tibia Player or Adobe AIR by CipSoft GmbH. Try to udate this program, in fact make sure all of your Adobe software is updated.

I agree with Tuan, do run driver verifier until it causes a BSOD or for for 24 hours. Carry on your normal computer operations while it is running.

Do a CPU stress test as well, using Prime95.

Ah, yeah I was playing Tibia at the time, although this isn't always running so the other blue screens shouldn't relate to this right, I will try the driver thing now and see what happens

 

[CarlTR6]

You are correct. It was running at the time and may not be the cause. Also I see that the driver spsys.sys was unloaded. SPSYS.SYS is the Windows Licensing System file; so I have to ask if your copy of Windows is validated and legitimate? This is not an accusation, just a question in the process of eliminating possibilities.

 

[jason786]

You are correct. It was running at the time and may not be the cause. Also I see that the driver spsys.sys was unloaded. SPSYS.SYS is the Windows Licensing System file; so I have to ask if your copy of Windows is validated and legitimate? This is not an accusation, just a question in the process of eliminating possibilities.

Yeah it's validated and legitimate, I even have the sticker on the side from where I got it built, also I've had this error for ages now and not only on this OS, I used to have Vista Home Premium x64 before and I had the problem on that too

Ok, I did driver verifier and here are the blue screens

Hope you guys can help

Edit: Thanks, will let you know if problems arise

 

[CarlTR6]

Both dmps are nearly identical and point to ASACPI.sys as the cause.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_062410-23634-01.zip\062410-23634-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a0b000 PsLoadedModuleList = 0xfffff800`02c48e50
Debug session time: Thu Jun 24 11:25:34.654 2010 (GMT-4)
System Uptime: 0 days 0:00:49.745

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 184, fffffa8007a34160, fffff880041e0257}

Unable to load image [COLOR=Red]ASACPI.sys[/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
[COLOR=Red]Probably caused by : ASACPI.sys[/COLOR] ( ASACPI+1257 )

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000184, Handle value being referenced.
Arg3: fffffa8007a34160, Address of the current process.
Arg4: fffff880041e0257, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  AiNap.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f053dc to fffff80002a7b600

STACK_TEXT:  
fffff880`087855b8 fffff800`02f053dc : 00000000`000000c4 00000000`000000f6 00000000`00000184 fffffa80`07a34160 : nt!KeBugCheckEx
fffff880`087855c0 fffff800`02f1aae4 : 00000000`00000184 fffffa80`07a34160 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`08785600 fffff800`02cd7580 : 00000000`00004c4e fffff880`08785830 00000000`00000000 fffffa80`046d4100 : nt!VfCheckUserHandle+0x1b4
fffff880`087856e0 fffff800`02d53425 : 00000000`00000000 fffff880`000f0001 00000000`00000000 fffffa80`00000000 : nt! ?? ::NNGAKEGL::`string'+0x20e1e
fffff880`087857b0 fffff800`02f1a878 : fffffa80`0625b968 fffff800`02f1dbcc fffffa80`046d4060 fffffa80`046d4060 : nt!ObReferenceObjectByHandle+0x25
fffff880`08785800 fffff880`041e0257 : fffff980`1592ecf0 00000000`00000002 fffffa80`046d41b0 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`08785850 fffff980`1592ecf0 : 00000000`00000002 fffffa80`046d41b0 00000000`00000000 fffffa80`046d41d8 : [COLOR=Red]ASACPI[/COLOR]+0x1257
fffff880`08785858 00000000`00000002 : fffffa80`046d41b0 00000000`00000000 fffffa80`046d41d8 00000000`00000000 : 0xfffff980`1592ecf0
fffff880`08785860 fffffa80`046d41b0 : 00000000`00000000 fffffa80`046d41d8 00000000`00000000 00000000`00000001 : 0x2
fffff880`08785868 00000000`00000000 : fffffa80`046d41d8 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`046d41b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ASACPI+1257
fffff880`041e0257 83462001        add     dword ptr [rsi+20h],1

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ASACPI+1257

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ASACPI

IMAGE_NAME:  [COLOR=Red]ASACPI.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0b72fd

FAILURE_BUCKET_ID:  X64_0xc4_f6_ASACPI+1257

BUCKET_ID:  X64_0xc4_f6_ASACPI+1257

Followup: MachineOwner

Here is a thread on the Asus site you can read about this driver and the utility.

ASUSTeK Computer Inc.-Forum- ATK0110 ACPI Utility Drivers

Although, I think you driver is current, I suggest that you reinstall it from the Asus site. Go to this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down). Download and install it.

Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010.

 

[jason786]

After I installed the driver again things seemed to be fine, however my computer just now randomly rebooted so I thought I'd run the driver verifier again

Guess what caused the blue screen :/

Do you have any more ideas for me? I know you suggested Prime95, and I haven't overlooked that, but I'm just wondering how excately it works, do I leave my computer on while it does a stress test? If so, I suppose I'd have to find a time for me to do it while I don't need the PC