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: BSOD stop 0x000000F9

29 Mar 2011   #1
bulletng

Windows 7 Pro x64
 
 
BSOD stop 0x0000009F

Hello everybody,

Thread title supposed to be 0x0000009F (not F9)
I'm having a BSOD after installing new hardware to my computer, but I cannot figure out what's exactly wrong.

I recently just bought two new WD hard drives to replace two of my old ones. I used Acronis to clone both hard drives, and everything was working fine until I started playing Assassins Creed II. There's no specific time when it happens, it just happens randomly in the middle of the game. STOP 0x000000F9

I have strong suspicions that it's a corrupt driver or something. I have my System Specs, Minidump bugcheck, and Event Viewer log, as well as Windows_NT6_BSOD_jcgriff2, Perfmon Log, and image attatched below.

Quote:
System specs:
Windows 7 Pro x64 (MSDNAA)
ASUS P6T Deluxe V2
Intel Core i7 920
Corsair XMS3 DDR3 (6GB Tri)
Corsair 850HX PSU
EVGA GTX 470 GPU


Recently re-installed OS about a year ago, hardware is a few years older than that(except HDD's and GPU).

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\032911-33150-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03261000 PsLoadedModuleList = 0xfffff800`0349ee50
Debug session time: Tue Mar 29 14:27:18.297 2011 (UTC - 4:00)
System Uptime: 0 days 6:31:26.467
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006321060, fffff80000ba2748, fffffa800581eb50}

Probably caused by : atapi.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: fffffa8006321060, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa800581eb50, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa80062dfe70

IMAGE_NAME:  atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc113

MODULE_NAME: atapi

FAULTING_MODULE: fffff88000e00000 atapi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  AssassinsCreed

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00ba26f8 fffff800`03340273 : 00000000`0000009f 00000000`00000003 fffffa80`06321060 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`032dd29e : fffff800`00ba28c0 fffff800`00ba28c0 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00ba27a0 fffff800`032dcdd6 : fffffa80`08933300 00000000`0016f8fd 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`032dd4be : 00000036`af0694a9 fffff800`00ba2e88 00000000`0016f8fd fffff800`03450228 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`032dccb7 : fffff800`0344bec8 fffffa80`0016f8fd fffffa80`06a43d38 00000000`000000fd : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`032d7865 : 00000000`00000000 fffffa80`089e3b60 00000000`00000000 fffff880`04018db0 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`032d767c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0a370be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_atapi.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_atapi.sys

Followup: MachineOwner
---------
Event Viewer log:
Code:
Error	3/29/2011 2:28:58 PM	BugCheck	1001
Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          3/29/2011 2:28:58 PM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      NATHAN-PC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa8006321060, 0xfffff80000ba2748, 0xfffffa800581eb50). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 032911-33150-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-03-29T18:28:58.000000000Z" />
    <EventRecordID>64695</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>NATHAN-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000009f (0x0000000000000003, 0xfffffa8006321060, 0xfffff80000ba2748, 0xfffffa800581eb50)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">032911-33150-01</Data>
  </EventData>
</Event>
Thanks!


My System SpecsSystem Spec
.
29 Mar 2011   #2
bulletng

Windows 7 Pro x64
 
 

Got this from my most recent minidump file:

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\032911-33150-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03261000 PsLoadedModuleList = 0xfffff800`0349ee50
Debug session time: Tue Mar 29 14:27:18.297 2011 (UTC - 4:00)
System Uptime: 0 days 6:31:26.467
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006321060, fffff80000ba2748, fffffa800581eb50}

Probably caused by : atapi.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: fffffa8006321060, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa800581eb50, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa80062dfe70

IMAGE_NAME:  atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc113

MODULE_NAME: atapi

FAULTING_MODULE: fffff88000e00000 atapi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  AssassinsCreed

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00ba26f8 fffff800`03340273 : 00000000`0000009f 00000000`00000003 fffffa80`06321060 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`032dd29e : fffff800`00ba28c0 fffff800`00ba28c0 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00ba27a0 fffff800`032dcdd6 : fffffa80`08933300 00000000`0016f8fd 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`032dd4be : 00000036`af0694a9 fffff800`00ba2e88 00000000`0016f8fd fffff800`03450228 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`032dccb7 : fffff800`0344bec8 fffffa80`0016f8fd fffffa80`06a43d38 00000000`000000fd : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`032d7865 : 00000000`00000000 fffffa80`089e3b60 00000000`00000000 fffff880`04018db0 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`032d767c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0a370be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_atapi.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_atapi.sys

Followup: MachineOwner
---------
My System SpecsSystem Spec
29 Mar 2011   #3
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by bulletng View Post
Hello everybody,

First off I'm new to these forums and yes I did a search for my specific stop error.
I'm having a BSOD after installing new hardware to my computer, but I cannot figure out what's exactly wrong.

I recently just bought two new WD hard drives to replace two of my old ones. I used Acronis to clone both hard drives, and everything was working fine until I started playing Assassins Creed II. There's no specific time when it happens, it just happens randomly in the middle of the game. STOP 0x000000F9

I have strong suspicions that it's a corrupt driver or something. I have my System Specs, Minidump bugcheck, and Event Viewer log, as well as Windows_NT6_BSOD_jcgriff2, Perfmon Log, and image attatched below.

Quote:
System specs:
Windows 7 Pro x64 (MSDNAA)
ASUS P6T Deluxe V2
Intel Core i7 920
Corsair XMS3 DDR3 (6GB Tri)
Corsair 850HX PSU
EVGA GTX 470 GPU


Recently re-installed OS about a year ago, hardware is a few years older than that(except HDD's and GPU).
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\032911-33150-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03261000 PsLoadedModuleList = 0xfffff800`0349ee50
Debug session time: Tue Mar 29 14:27:18.297 2011 (UTC - 4:00)
System Uptime: 0 days 6:31:26.467
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006321060, fffff80000ba2748, fffffa800581eb50}

Probably caused by : atapi.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: fffffa8006321060, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa800581eb50, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa80062dfe70

IMAGE_NAME:  atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc113

MODULE_NAME: atapi

FAULTING_MODULE: fffff88000e00000 atapi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  AssassinsCreed

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00ba26f8 fffff800`03340273 : 00000000`0000009f 00000000`00000003 fffffa80`06321060 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`032dd29e : fffff800`00ba28c0 fffff800`00ba28c0 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00ba27a0 fffff800`032dcdd6 : fffffa80`08933300 00000000`0016f8fd 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`032dd4be : 00000036`af0694a9 fffff800`00ba2e88 00000000`0016f8fd fffff800`03450228 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`032dccb7 : fffff800`0344bec8 fffffa80`0016f8fd fffffa80`06a43d38 00000000`000000fd : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`032d7865 : 00000000`00000000 fffffa80`089e3b60 00000000`00000000 fffff880`04018db0 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`032d767c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0a370be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_atapi.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_atapi.sys

Followup: MachineOwner
---------
Event Viewer log:
Code:
Error    3/29/2011 2:28:58 PM    BugCheck    1001
Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          3/29/2011 2:28:58 PM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      NATHAN-PC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa8006321060, 0xfffff80000ba2748, 0xfffffa800581eb50). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 032911-33150-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-03-29T18:28:58.000000000Z" />
    <EventRecordID>64695</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>NATHAN-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000009f (0x0000000000000003, 0xfffffa8006321060, 0xfffff80000ba2748, 0xfffffa800581eb50)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">032911-33150-01</Data>
  </EventData>
</Event>
Thanks!

Two problems


1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

Visit 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 (NOT 2005)

2-Old drivers needing updates
Code:
ASACPI.sys    3/27/2005 10:30:36 PM    fffff880`0451c000    fffff880`04524000    0x00008000    0x42476c4c                            
secdrv.SYS    9/13/2006 09:18:38 AM    fffff880`078d6000    fffff880`078e1000    0x0000b000    0x4508052e                            
regi.sys    4/16/2007 11:19:10 AM    fffff880`06fd9000    fffff880`06fe1000    0x00008000    0x462393ee                            
RivaTuner64.sys    7/17/2007 03:13:42 PM    fffff880`07d9c000    fffff880`07da3000    0x00007000    0x469d14e6                            
000.fcl    9/26/2008 09:11:22 AM    fffff880`07937000    fffff880`07962000    0x0002b000    0x48dcdf7a                            
spldr.sys    5/11/2009 12:56:27 PM    fffff880`015e1000    fffff880`015e9000    0x00008000    0x4a0858bb                            
spsys.sys    5/11/2009 01:20:58 PM    fffff880`07c00000    fffff880`07c71000    0x00071000    0x4a085e7a                            
GEARAspiWDM.sys    5/18/2009 08:17:04 AM    fffff880`044c4000    fffff880`044d1000    0x0000d000    0x4a1151c0                            
amdxata.sys    5/19/2009 01:56:59 PM    fffff880`010f2000    fffff880`010fd000    0x0000b000    0x4a12f2eb                            
yk62x64.sys    5/20/2009 04:14:06 AM    fffff880`0443d000    fffff880`044a1000    0x00064000    0x4a13bbce                            
ADIHdAud.sys    5/21/2009 04:21:06 AM    fffff880`05b46000    fffff880`05bbf000    0x00079000    0x4a150ef2                            
LHidFilt.Sys    6/17/2009 12:49:39 PM    fffff880`06a9a000    fffff880`06aad000    0x00013000    0x4a391ea3                            
LMouFilt.Sys    6/17/2009 12:49:43 PM    fffff880`06aba000    fffff880`06ace000    0x00014000    0x4a391ea7                            
PxHlpa64.sys    6/23/2009 07:16:35 PM    fffff880`0115d000    fffff880`01168e00    0x0000be00    0x4a416253
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
My System SpecsSystem Spec
.

29 Mar 2011   #4
bulletng

Windows 7 Pro x64
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post

Two problems


1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

Visit 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 (NOT 2005)

2-Old drivers needing updates
Code:
ASACPI.sys    3/27/2005 10:30:36 PM    fffff880`0451c000    fffff880`04524000    0x00008000    0x42476c4c                            
secdrv.SYS    9/13/2006 09:18:38 AM    fffff880`078d6000    fffff880`078e1000    0x0000b000    0x4508052e                            
regi.sys    4/16/2007 11:19:10 AM    fffff880`06fd9000    fffff880`06fe1000    0x00008000    0x462393ee                            
RivaTuner64.sys    7/17/2007 03:13:42 PM    fffff880`07d9c000    fffff880`07da3000    0x00007000    0x469d14e6                            
000.fcl    9/26/2008 09:11:22 AM    fffff880`07937000    fffff880`07962000    0x0002b000    0x48dcdf7a                            
spldr.sys    5/11/2009 12:56:27 PM    fffff880`015e1000    fffff880`015e9000    0x00008000    0x4a0858bb                            
spsys.sys    5/11/2009 01:20:58 PM    fffff880`07c00000    fffff880`07c71000    0x00071000    0x4a085e7a                            
GEARAspiWDM.sys    5/18/2009 08:17:04 AM    fffff880`044c4000    fffff880`044d1000    0x0000d000    0x4a1151c0                            
amdxata.sys    5/19/2009 01:56:59 PM    fffff880`010f2000    fffff880`010fd000    0x0000b000    0x4a12f2eb                            
yk62x64.sys    5/20/2009 04:14:06 AM    fffff880`0443d000    fffff880`044a1000    0x00064000    0x4a13bbce                            
ADIHdAud.sys    5/21/2009 04:21:06 AM    fffff880`05b46000    fffff880`05bbf000    0x00079000    0x4a150ef2                            
LHidFilt.Sys    6/17/2009 12:49:39 PM    fffff880`06a9a000    fffff880`06aad000    0x00013000    0x4a391ea3                            
LMouFilt.Sys    6/17/2009 12:49:43 PM    fffff880`06aba000    fffff880`06ace000    0x00014000    0x4a391ea7                            
PxHlpa64.sys    6/23/2009 07:16:35 PM    fffff880`0115d000    fffff880`01168e00    0x0000be00    0x4a416253
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Thank you!
I have updated the ASACPI.sys and it now says 2009.
I am curious about the other drivers though. Some of them I do not even use the programs anymore, and I've uninstalled those programs while ago.

I greatly appreciate the help, but do you mind me asking how did you manage to diagnose my problem? I've already learned a lot from this issue and I'd love to learn how you solved it. (I also wanted to know how so that I can check to see if I've updated all the drivers correctly and it isn't responding with further issues).
My System SpecsSystem Spec
Reply

 BSOD stop 0x000000F9




Thread Tools




Similar help and support threads
Thread Forum
BSOD random stop : stop 0x0000007A
I have bluescreen with that stop 0x0000007A (0x0000000000000020, 0xFFFFFFFFc000009D, 0xFFFFFFFFA8007CEF7C8, 0x0000000000000000) It happens randomly after sometime half an hour one hour whatever i'm doing on my computer. Do you have any solution to solve this problem. Thanks windows7 64 bit...
BSOD Help and Support
BSOD Stop 0x000000F9
I was having issues on my computer so I reinstalled my OS on my SSD. Installed all the required drivers but just had another BSOD. I tried putting the computer to sleep, returned 10 minutes later to see that it restarted due to this BSOD. It looks like it might have to do with the cdrom because...
BSOD Help and Support
BSOD random 0x000000f9
uploading my dmp file.. pls help this BSOD really bugs me thanks..
BSOD Help and Support
BSOD randomly STOP: 0x0000003B & STOP: 0X00000024
Hello i have had 2 BSOD's or more recently. I dont know why, i only saw 2 of them, but ive had around 3 - 4, the other 1 - 2 were seen by family members but they just turned the pc off and back on... anyhow here are some pictures ...
BSOD Help and Support
BSOD STOP: 0x3B atikmdag.sys/STOP: 0x7E dxgmms1.sys
Guys I'm at a loss I'm getting BSOD's all the time I really don't know what to do with it, and I'm not computer heavy so. If someone here could help me that would be appreciated. I've included a Dxdiag file with the rest.
BSOD Help and Support
BSOD stop 0x000000F9 again
Hello, I just had another BSOD for the first time in a long time... I'm surprised to see that it's the same error (STOP 0x000000F9) as before and I did the exact same thing that solved it before. I just want to make sure that there isn't anything else wrong. My most recent hardware upgrade...
BSOD Help and Support


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 08:54.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App