Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD


13 Nov 2010   #1

win 7 x64
 
 
Random BSOD

Hey there lately i am getting Black screen at random times i cant really identify whats the problem is since i have changed many things added new programs updated drivers overclocked my pc etc. i am getting them in random times not when my pc is stressed so i think its not the overclocking.

i am getting these 2 different messages in the blue screens
0x000000A
and
0x00000D1

My System SpecsSystem Spec
.

13 Nov 2010   #2

Windows 7 Ultimate 32 bit
 
 

Hi lelos and welcome to the forum. Sorry you are having problems. Please follow the instructions in this tutorial so that we have additional system information to help us better help you: http://www.sevenforums.com/crashes-d...tructions.html

Both of your dumps blame Windows system drivers, which is most likely not the real cause of the crashes.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0220a000 PsLoadedModuleList = 0xfffff800`0243eeb0
Debug session time: Fri Nov 12 15:08:29.344 2010 (GMT-5)
System Uptime: 1 days 15:45:21.181
Loading Kernel Symbols
...............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {f48, 2, 0, fffff8000227d17b}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )

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

3: 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: 0000000000000f48, 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: fffff8000227d17b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800024a90e0
 0000000000000f48 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+13b
fffff800`0227d17b 488b42f8        mov     rax,qword ptr [rdx-8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  sqlservr.exe

TRAP_FRAME:  fffff880104d2890 -- (.trap 0xfffff880104d2890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000003
rdx=fffffa800889bc40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000227d17b rsp=fffff880104d2a20 rbp=fffff88001ecf2e8
 r8=ffffffffffffffff  r9=000000000000006b r10=fffff88001ecc180
r11=fffff88001ecc100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
nt!KiInsertTimerTable+0x13b:
fffff800`0227d17b 488b42f8        mov     rax,qword ptr [rdx-8] ds:fffffa80`0889bc38=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000226fae9 to fffff80002270580

STACK_TEXT:  
fffff880`104d2748 fffff800`0226fae9 : 00000000`0000000a 00000000`00000f48 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`104d2750 fffff800`0226e760 : 00000000`00000000 00000000`00000f48 00000000`00001f00 fffffa80`0876b120 : nt!KiBugCheckDispatch+0x69
fffff880`104d2890 fffff800`0227d17b : 00000008`00000003 fffff880`01ecc180 fffffa80`0876b060 fffff880`01e5c180 : nt!KiPageFault+0x260
fffff880`104d2a20 fffff800`022779b2 : fffffa80`0876b060 fffffa80`0876b060 00000000`00000000 fffff800`00000003 : nt!KiInsertTimerTable+0x13b
fffff880`104d2a80 fffff800`022799af : 00000000`0000027c 00000000`00000001 fffff880`0000006b fffff800`02274771 : nt!KiCommitThreadWait+0x332
fffff880`104d2b10 fffff800`0256acd2 : fffffa80`077eba00 fffffa80`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`104d2bb0 fffff800`0226f7d3 : fffffa80`0876b060 00000000`00000039 fffff880`104d2bf8 fffffa80`077bc6a0 : nt!NtWaitForSingleObject+0xb2
fffff880`104d2c20 00000000`7786fd9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0b47f158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7786fd9a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertTimerTable+13b
fffff800`0227d17b 488b42f8        mov     rax,qword ptr [rdx-8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertTimerTable+13b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c42e3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+13b

BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+13b

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

Debug session time: Sat Nov 13 12:07:19.176 2010 (GMT-5)
System Uptime: 0 days 20:57:42.369
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8004a27f7ae, 2, 8, fffff8004a27f7ae}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff8004a27f7ae, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8004a27f7ae, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800024a10e0
 fffff8004a27f7ae 

CURRENT_IRQL:  2

FAULTING_IP: 
+614d952f0198da38
fffff800`4a27f7ae ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  sqlservr.exe

TRAP_FRAME:  fffff8800fefe8e0 -- (.trap 0xfffff8800fefe8e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000008
rdx=fffffa8008134ae0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004a27f7ae rsp=fffff8800fefea70 rbp=fffffa8007430b60
 r8=fffff88001ed0700  r9=0000000000000000 r10=00000000000000e0
r11=fffff88001ecc180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff800`4a27f7ae ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002267ae9 to fffff80002268580

FAILED_INSTRUCTION_ADDRESS: 
+614d952f0198da38
fffff800`4a27f7ae ??              ???

STACK_TEXT:  
fffff880`0fefe798 fffff800`02267ae9 : 00000000`0000000a fffff800`4a27f7ae 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0fefe7a0 fffff800`02266760 : 00000000`00000008 fffff800`4a27f7ae fffffa80`00000000 fffffa80`07430b60 : nt!KiBugCheckDispatch+0x69
fffff880`0fefe8e0 fffff800`4a27f7ae : fffffa80`07430c68 fffffa80`07430b60 fffffa80`07430b60 00000000`00000008 : nt!KiPageFault+0x260
fffff880`0fefea70 fffffa80`07430c68 : fffffa80`07430b60 fffffa80`07430b60 00000000`00000008 fffff8a0`00000000 : 0xfffff800`4a27f7ae
fffff880`0fefea78 fffffa80`07430b60 : fffffa80`07430b60 00000000`00000008 fffff8a0`00000000 fffffa80`00000001 : 0xfffffa80`07430c68
fffff880`0fefea80 fffffa80`07430b60 : 00000000`00000008 fffff8a0`00000000 fffffa80`00000001 fffffa80`07430b60 : 0xfffffa80`07430b60
fffff880`0fefea88 00000000`00000008 : fffff8a0`00000000 fffffa80`00000001 fffffa80`07430b60 fffff800`0226cffa : 0xfffffa80`07430b60
fffff880`0fefea90 fffff8a0`00000000 : fffffa80`00000001 fffffa80`07430b60 fffff800`0226cffa 00000000`000003d4 : 0x8
fffff880`0fefea98 fffffa80`00000001 : fffffa80`07430b60 fffff800`0226cffa 00000000`000003d4 fffffa80`07430c68 : 0xfffff8a0`00000000
fffff880`0fefeaa0 fffffa80`07430b60 : fffff800`0226cffa 00000000`000003d4 fffffa80`07430c68 00000000`00000000 : 0xfffffa80`00000001
fffff880`0fefeaa8 fffff800`0226cffa : 00000000`000003d4 fffffa80`07430c68 00000000`00000000 00000000`00000000 : 0xfffffa80`07430b60
fffff880`0fefeab0 fffff800`0226c771 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiDeferredReadyThread+0x31a
fffff880`0fefeb30 fffff800`023822e2 : 00000000`00000001 fffff800`00000006 fffff880`0fefec01 fffffa80`08134b00 : nt!KeSetEvent+0x1e1
fffff880`0fefeba0 fffff800`022677d3 : fffffa80`07430b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtSignalAndWaitForSingleObject+0x192
fffff880`0fefec20 00000000`77c314ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0d50f3a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c314ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02266760 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c42e3

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

Followup: MachineOwner
---------
Quote:
Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

Error code D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL. Usual causes: Device driver
We really need the files provided by the tool in the link above to look in depth at your system.

To begin, uninstall your virtual CD program.
Quote:
Please uninstall any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dump, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Select delete; do not select reinstall.
Here is an alternative virtualization program that does not user the sptd.sys driver:
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
Next uninstall TuneUp Utilities. Win 7 does not need a tuneup utility. It is not like XP at all. At best a tuneup utility simply takes up resources; at worst thwy can actually harm your system. There is no tuneup utility out there anywhere that can improve Win 7's performance, at least not at this time. You cannot mange Win 7 as you did XP. Win 7 is a totally new operating system.

If you are overclocking anything, please stop and return to default values.

You have some out of date drivers loaded on your system. Outdated drivers can and do cause memory corruption and BSOD's.

Completely uninstall Eset using this removal tool:Tool. Eset is known to cause BSOD's on some Win 7 systems. Plus, you version is outdated. Download and install Microsoft Security Essentials in its place and make sure Windows Firewall is turned on.

Quote:
adfs.SYS Thu Jun 26 16:52:37 2008 - Adobe File System Driver, Adobe. See note below.

ATITool64.sys Wed Aug 08 12:42:26 2007 - Overclocking utility for ATI/nVidia cards - will only work on Windows 2000/XP/2003ATITool - Overclocking utility for ATI and NVIDIA cards. Uninstall this software completely.

Epfwndis.sys Thu Apr 09 08:43:20 2009 - EPFW Filter Driver, a part of ESET NOD32 Best Free Antivirus Software Trial: Free Home, Business and Gaming Download from ESET. Uninstall Eset as mentioned above.
Note   Note
As far as I know, there is no update for this driver; it is obsolete. Isuggest that you completely uninstall all of your Adobe software and download and install the latest versions which are compatible with Win 7. You can also do a search of your C: drive for adfs.sys, and rename every instance of it from .sys to .sys_. Reboot and this driver will not load. This method may break whichever Adobe program the driver is associated with. If it does, uninstall that program.


Follow these steps and run your system. Post back and let us know how your system is doing. If you get another BSOD, upload it to us. We will take a look and go from there. Don't forget to run the tool and upload the resulting files.
My System SpecsSystem Spec
13 Nov 2010   #3

Windows 7 Professional x64
 
 

Start by updating ESET to the latest version: Best Free Antivirus Software Trial: Free Home, Business and Gaming Download from ESET

Perhaps that is what is causing the BSODs while sqlservr.exe is running.

Also, remove Daemon Tools or any similar programs, as it is using SPTD. Remove SPTD when that's done: http://www.duplexsecure.com/download...t-v174-x64.exe

If the BSODs persist, enable driver verifier: Driver Verifier - Enable and Disable

After a few BSODs have occurred, upload a jcgriff2 report: http://www.sevenforums.com/crashes-d...tructions.html

...Summary of the dumps
Code:

Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Sat Nov 13 12:07:19.176 2010 (UTC - 5:00)
System Uptime: 0 days 20:57:42.369
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  sqlservr.exe
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Fri Nov 12 15:08:29.344 2010 (UTC - 5:00)
System Uptime: 1 days 15:45:21.181
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  sqlservr.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+13b
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
.


13 Nov 2010   #4

win 7 x64
 
 

first thanks for the really fast support, yeah i am not using latest version for eset il update it and il uninstall daemon tools aswell but i had installed these program before 1-2 years and i never had problems with bsod in the past

i uploaded aswell a jcgriff2 report.
il keep u updated
My System SpecsSystem Spec
13 Nov 2010   #5

Windows 7 Professional x64
 
 

My System SpecsSystem Spec
13 Nov 2010   #6

Windows 7 Ultimate x64
 
 

i know this is rude but could help me with my problem as well?
i'm desperate T_T

http://www.sevenforums.com/crashes-d..._or_equal.html
My System SpecsSystem Spec
13 Nov 2010   #7

Windows 7 Ultimate 32 bit
 
 

Hi Jason; we would be glad to help you. Please start a new thread and follow the instructions in this tutorial:

http://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
13 Nov 2010   #8

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by CarlTR6 View Post
Hi Jason; we would be glad to help you. Please start a new thread and follow the instructions in this tutorial:

http://www.sevenforums.com/crashes-d...tructions.html
so sorry i will just wait for u to reply
My System SpecsSystem Spec
13 Nov 2010   #9

win 7 x64
 
 

ATITool64.sys is a monitoring program for graphic card known as gpu-z i kinda need this
same goes with antivirus/firewall i really like it and i use it last 5 years i never had problems with this
about the adobe driver i dont know what is this
for tune up program i can remove this aswell i mostly use it manage my start up programs, uninstall programs etc and free space cause i have all these things in 1 place for now i updated the antivirus program like i said before and removed daemon tools. i was getting bsod really random so i have to wait for now, like 1 time per week.

and btw if i have any driver outdated i want to know which one so i can update it
My System SpecsSystem Spec
14 Nov 2010   #10

Windows 7 Ultimate 32 bit
 
 

The program that ATITool64.sys belongs to is obsolete. See if there is newer version that is compatible with Win 7. Win 7 is not an evolution from XP. It is a totally new OS. Much of what was designed for XP will not run on Win 7 except in the XP mode. Programs you used five years ago on XP are not going to work with Win 7. It is akin to trying to put a 60's era VW Beetle suspension system on a new Ferrari. Upgrade your software to Win 7 compatible software.

I found three outdated drivers and I listed them in the post above. Everything else looks pretty good.
My System SpecsSystem Spec
Reply

 Random BSOD




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 04:32 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33