Solved BSOD + Stuck on Waking up from Sleep

moltenice · Dec 22, 2010

Hey guys!

Basically I've been having these BSODs whenever I wake my computer up from sleep mode. Used to be only BSODs everytime I wake my computer up and when I googled this issue most people said it's some driver problem.

I had updated (Windows Update had updated) the drivers for my Intel Wireless G adapter (built in into my laptop) but I restored the old Drivers that are found on the HP website.

Since then this issue seemed to be fixed but now sometimes it might BSOD and sometimes it gets stuck, meaning I cant move anything on my computer (no mouse no keyboard inputs either) and there is no hard disk being used light running. This also seems to happen after about 30 seconds (usually enough time for me to type my password so I can log in) and then either it gets stuck or first gets stuck and BSODs. THe error is always IRQL_LESS or something similar.

I have attached the dump data of one of these BSODs (I think it is on the same problem)

Here is some of the info on this dump:

Product
Windows

Problem
Shut down unexpectedly

Date
19/12/2010 06:49 PM

Status
Not Reported

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Files that help describe the problem
Mini121910-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 1000000a
BCP1: 1F817481
BCP2: 00000002
BCP3: 00000001
BCP4: 84EBCE64
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Rest is attached.

Do let me know what the problem is! Thanks a lot in advance

richc46 · Dec 22, 2010

Code:

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Dump%20File![1].zip\Mini121910-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x84e13000 PsLoadedModuleList = 0x84f2ac70
Debug session time: Sun Dec 19 13:43:05.172 2010 (GMT-5)
System Uptime: 0 days 11:49:59.021
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {1f817481, 2, 1, 84ebce64}
Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+1c3 )
Followup: MachineOwner
---------
0: 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: 1f817481, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 84ebce64, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 84f4a868
Unable to read MiSystemVaType memory at 84f2a420
 1f817481 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!KiTimerExpiration+1c3
84ebce64 890a            mov     dword ptr [edx],ecx
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
LAST_CONTROL_TRANSFER:  from 84ebd635 to 84ebce64
STACK_TEXT:  
8059df88 84ebd635 00000000 00000000 0029aac1 nt!KiTimerExpiration+0x1c3
8059dff4 84ebb2f5 bf85ad10 00000000 00000000 nt!KiRetireDpcList+0xba
8059dff8 bf85ad10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
84ebb2f5 00000000 0000001b 00c7850f bb830000 0xbf85ad10
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiTimerExpiration+1c3
84ebce64 890a            mov     dword ptr [edx],ecx
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!KiTimerExpiration+1c3
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4c0e557c
FAILURE_BUCKET_ID:  0xA_nt!KiTimerExpiration+1c3
BUCKET_ID:  0xA_nt!KiTimerExpiration+1c3
Followup: MachineOwner
---------

The reports that I analyze give clues not answers to the BSOD problem. You have had only one and there are not many clues. It appears to be a driver, but that is suspect. The driver given as the cause, is not the true cause but the one that is named in lieu of the actual culprit. Follow my instructions. When if you get other BSODs after that just post

These drivers must be updated

Code:

Aspi32.SYS   Fri Sep 10 19:46:10 1999
AFS.sys      Mon Feb 25 18:04:47 2002
windrvNT.sys Mon May 10 04:42:04 2004
lirsgt.sys   Sun Jan 29 06:06:18 2006
secdrv.SYS   Wed Sep 13 09:18:32 2006
peauth.sys   Mon Oct 23 04:55:32 2006
msahci.sys   Thu Nov 02 04:51:36 2006
crcdisk.sys  Thu Nov 02 04:52:27 2006
pcouffin.sys Tue Dec 05 09:39:53 2006
rimsptsk.sys Tue Jan 23 02:40:19 2007
rimmptsk.sys Sat Feb 24 00:42:21 2007
rixdptsk.sys Wed Mar 21 09:02:02 2007
lmimirr.sys  Tue Apr 10 18:32:11 2007
pstrip.sys   Tue May 08 05:51:01 2007
spldr.sys    Thu Jun 21 20:29:17 2007
btwavdt.sys  Thu Jul 12 19:04:57 2007
btwrchid.sys Thu Jul 12 19:06:31 2007
btwaudio.sys Tue Sep 04 15:38:00 2007
atksgt.sys   Fri Sep 14 08:13:09 2007
npf.sys      Tue Nov 06 15:09:15 2007
RaInfo.sys   Fri Jan 04 13:57:12 2008
RTKVHDA.sys  Tue Jan 15 06:18:36 2008

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command

How to Find Drivers
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 help you 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
- - 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: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
and here
http://www.edbott.com/weblog/the-vista-master-driver-list/
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
You can also locate information about your driver using this information
http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html

The normal procedure at this point would be to give a driver verifier test, I am trying to avoid that if possible.
YOu can take a memory test, just to be sure that its not memory. Bad memory can show up as driver problems.
http://www.geekstogo.com/forum/topic/246994-guide-to-using-memtest86/

moltenice · Dec 24, 2010

Hey Rich, thanks for your reply!

I think that since I've downgraded my Intel Wireless drivers I haven't gotten BSOD but my PC instead just stops working. meaning it just doesn't do anything. no keys work and the hard disk isn't responding. Also the fan seems to be working really hard. No choice but to restart the PC... I kept it like that for about 5 hours and nothing happened.

Also, at the moment seems like my explorer.exe is using up 95% of my CPU continuously... I dont get why? :S

I don't have any more BSOD reports to give you unfortunetely so please let me know on what can be done!

Thanks a lot again

richc46 · Dec 24, 2010

Try with a clean boot
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

Does this prevent the shut downs
Does this stop the high cpu usage.

If so follow the clean boot instructions
If not report back.

moltenice · Dec 27, 2010

Here is another BSOD (got on christmas... yaaay :P)

Product
Windows

Problem
Shut down unexpectedly

Date
25/12/2010 02:36 PM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Files that help describe the problem (some files may no longer be available)
Mini122510-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 9f
BCP1: 00000003
BCP2: 899E4DE0
BCP3: 8D109608
BCP4: 8D6AF0F0
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Server information: 4fc714c4-ba89-4af1-ada4-0dd0ef1c7697

I have attached the dump files etc.

I tried a clean boot but I think the problem is still there. Explorer.exe for some reason is always 50%+ and whenever I wake up from sleep now sometimes it crashes sometimes it doesn't (and sometimes it BSODs)

Finally, whenever I browse a folder with videos (avi/wmv) explorer.exe goes to 99% slowing my complete PC down! I kept it like that for hours and explorer.exe never went below 50%!

Do let me know what's happening with this BSOD.

Thanks!

richc46 · Dec 27, 2010

It came up driver again.
Take the driver verifier test

How to Find Drivers
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 help you 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
- - 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: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
and here
http://www.edbott.com/weblog/the-vista-master-driver-list/
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
You can also locate information about your driver using this information
http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html

Driver Verifier Inst
Since the driver that crashed you has not been listed you should run driver verifier
Please run Verifier with these settings:

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/Windows 7 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and 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.

Enable the driver verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

moltenice · Jan 2, 2011

Hey! Happy New year!

Sorry I've been really busy with the holidays and all, and will get to trying out your Driver Verifier Solution soon.

But luckily my PC BSODed! And it sort of happened after I tried to shut it down :\

Hopefully it can shed some light into the issue?

Here's the info (and the extra details attached):

Product
Windows

Problem
Shut down unexpectedly

Date
03/01/2011 01:47 AM

Status
Not Reported

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Files that help describe the problem
Mini010311-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 100000c5
BCP1: 0000A580
BCP2: 00000002
BCP3: 00000000
BCP4: 84F0D770
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

richc46 · Jan 2, 2011

Happy New Year.
STOP 0x000000C5: DRIVER_CORRUPTED_EXPOOL Usual causes: Device driver, ?Memory

Not really much of a help. It appears to be drivers, but its not telling which one. The verifier is suppose to make the bad drivers cause BSODs then we can tell.

C5 indicates can also be memory, Take the memory test first, its easier
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If passes try a good stick in each slot for 3 passes
If fails do the same for 8 passes.

moltenice · Jan 3, 2011

I will run that test in a bit... until then do have a look at this BSOD, it seems like this one had a different error code! My computer is filled with all kinds of errors

I really think it's just one driver or something, because I hardly ever BSODed!

I will run both your tests soon Richard, thanks for all your quick replies!

Here's the new dump files:

Product
Windows

Problem
Shut down unexpectedly

Date
03/01/2011 09:44 PM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Files that help describe the problem (some files may no longer be available)
Mini010311-03.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 1000007e
BCP1: C0000005
BCP2: 84EEE443
BCP3: 8F357BB0
BCP4: 8F3578AC
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Server information: 9da56410-b54a-4caa-8ece-a1166450a52f

Do let me know if this BSOD is also driver related and if it could be the same driver issue!

richc46 · Jan 3, 2011

Code:

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Dump%20FIles[1].zip\Mini010311-03.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x84e01000 PsLoadedModuleList = 0x84f18c70
Debug session time: Mon Jan  3 12:39:20.645 2011 (GMT-5)
System Uptime: 0 days 2:34:29.550
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 84eee443, 8f357bb0, 8f3578ac}
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+43d )
Followup: MachineOwner
---------
1: 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: c0000005, The exception code that was not handled
Arg2: 84eee443, The address that the exception occurred at
Arg3: 8f357bb0, Exception Record Address
Arg4: 8f3578ac, Context Record Address
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!ExFreePoolWithTag+43d
84eee443 0fb74ffa        movzx   ecx,word ptr [edi-6]
EXCEPTION_RECORD:  8f357bb0 -- (.exr 0xffffffff8f357bb0)
ExceptionAddress: 84eee443 (nt!ExFreePoolWithTag+0x0000043d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0000258a
Attempt to read from address 0000258a
CONTEXT:  8f3578ac -- (.cxr 0xffffffff8f3578ac)
eax=00000000 ebx=8c6c5a00 ecx=00000001 edx=00000000 esi=00002590 edi=00002590
eip=84eee443 esp=8f357c78 ebp=8f357cd0 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!ExFreePoolWithTag+0x43d:
84eee443 0fb74ffa        movzx   ecx,word ptr [edi-6]     ds:0023:0000258a=????
Resetting default scope
CUSTOMER_CRASH_COUNT:  3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  00000000
EXCEPTION_PARAMETER2:  0000258a
READ_ADDRESS: GetPointerFromAddress: unable to read from 84f38868
Unable to read MiSystemVaType memory at 84f18420
 0000258a 
FOLLOWUP_IP: 
nt!ExFreePoolWithTag+43d
84eee443 0fb74ffa        movzx   ecx,word ptr [edi-6]
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from 8503319d to 84eee443
STACK_TEXT:  
8f357cd0 8503319d 00002590 00000000 00000000 nt!ExFreePoolWithTag+0x43d
8f357d00 84e5ec2b 00000000 00000000 00000000 nt!MiSegmentDelete+0xd3
8f357d50 84e5edae 87f9c508 00000000 ffffffff nt!MiProcessDereferenceList+0x33
8f357d7c 84fd6c42 00000000 d4183b42 00000000 nt!MiDereferenceSegmentThread+0xc1
8f357dc0 84e3ff4e 84e5eceb 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!ExFreePoolWithTag+43d
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4c0e557c
STACK_COMMAND:  .cxr 0xffffffff8f3578ac ; kb
FAILURE_BUCKET_ID:  0x7E_nt!ExFreePoolWithTag+43d
BUCKET_ID:  0x7E_nt!ExFreePoolWithTag+43d
Followup: MachineOwner
---------

It gives a lead Microsoft Driver as the cause. The cause is actually a subordinate driver. Still a driver problem

moltenice · Jan 18, 2011

Hey sorry for not replying for ages. I ran the memory test... No problems found. Definetely a driver issue then right? *sigh*

I'll run the driver test in a few days and let you know about the results.

richc46 · Jan 18, 2011

Take your time, no rush. I wish you luck

moltenice · Mar 4, 2011

Hi Rich

Well after months I actually got free time so I ran the test and it worked! It BSODED with AFS.SYS.

Don't know what this is... what must I do now?

richc46 · Mar 4, 2011

If your diagnosis is correct this is the driver and company (below) that cause the problem

How to Find Drivers
search Google for the name of the driver (Idid this part for you)
- 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 help you 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
- - 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: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
and here
http://www.edbott.com/weblog/the-vista-master-driver-list/
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
You can also locate information about your driver using this information
http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html

Afs.sys file description
Productname:AFS Description:Audio File System
Company:Oak Technology Inc

moltenice · Mar 4, 2011

Thanks Rich, I had actually looked it up myself. Odd thing is that I have NEVER heard of this company until now, and it probably is some other company using the drivers of Oak Technology.

I don't really know how to find out WHICH hardware device is using this driver, and how to uninstall it or find an update if any at all.

Any help for this would be much appreciated

richc46 · Mar 4, 2011

Heres the story
Oak was taken over by Zorian industries and now it appears that Zorian was taken over; this means I cant find that driver.
This is what we do

Its an audio file system, so what can it be used for hmm. Maybe audio?
Go to search by the start button
type device manager.
Look for any yellow warnings
If none
go to the audio section, update that driver. Use the procedure in the tutorial that I gave you.
If that does not work, post back, and Ill give you part II.

moltenice · Mar 4, 2011

Haha, sorry Rich I forgot mentioning, I checked all Audio drivers and none of them seem to be using afs.sys

I was just hoping you had a way for figuring out if afs.sys was being used at all and for what hardware if not an Audio one!

Awaiting your reply.

richc46 · Mar 4, 2011

Its being used, since it was involed in your BSOD
If you are using Itunes, the driver is probably connected to that software.

But
If you go here
C-->Windows-->System 32-->drivers.
And change the .sys to .bup effectively you are destroying the driver. Use for a while in that condition and see what happens.

If you cannot find it go to control panel
Go to folder features
Untick hide protected os files
Tick show hidden files.

Dont forget to change the tick marks the way they were before making the change.
Furthermore, if that driver is hidden it is considered important.

richc46 · Mar 4, 2011

After posting the above, I had a thought. I questioned if AFS could indeed be the cause of your initial BSOD. I ran a list of all the drivers that could have caused the BSOD. Look at the age of AFS, it is on my initial list of drivers that had to be updated. You nailed it buddy.

Code:

000      000.fcl      Fri Sep 26 09:11:12 2008 (48DCDF70)
943e4000 943f1080   1394BUS  1394BUS.SYS  Sat Jan 19 00:53:27 2008 (47919057)
85f2b000 85f71000   acpi     acpi.sys     Sat Apr 11 00:19:03 2009 (49E01A37)
8459d000 845c23a0   afcdp    afcdp.sys    Fri Sep 11 12:19:52 2009 (4AAA78A8)
9659e000 965e6000   afd      afd.sys      Sat Apr 11 00:47:01 2009 (49E020C5)
8e106000 8e1127c0   AFS      [B]AFS.sys      Mon Feb 25 18:04:47 2002[/B] (3C7AC30F)
ae99a000 ae9a1000   ALSysIO  ALSysIO.sys  Fri Dec 19 17:20:06 2008 (494C1E16)
8e599000 8e5d2000   anobimnl anobimnl.SYS Tue Jul 14 17:12:41 2009 (4A5CF4C9)
96694000 966a8480   archlp   archlp.sys   Tue Jan 12 03:07:05 2010 (4B4C2DA9)
9668d000 96690e40   Aspi32   Aspi32.SYS   Fri Sep 10 19:46:10 1999 (37D99842)
8e0d7000 8e0df000   atapi    atapi.sys    Sat Apr 11 00:39:09 2009 (49E01EED)
8e0df000 8e0fd000   ataport  ataport.SYS  Sat Apr 11 00:39:10 2009 (49E01EEE)
8455a000 8459c600   atksgt   atksgt.sys   Fri Sep 14 08:13:09 2007 (46EA7AD5)
85fb2000 85fbc000   BATTC    BATTC.SYS    Sat Jan 19 00:32:45 2008 (47918B7D)
95bbd000 95bc4000   Beep     Beep.SYS     Sat Jan 19 00:49:10 2008 (47918F56)
80691000 80699000   BOOTVID  BOOTVID.dll  Sat Jan 19 02:27:15 2008 (4791A653)
832dd000 832f6000   bowser   bowser.sys   Sat Jan 19 00:28:26 2008 (47918A7A)
95cd4000 95cde000   BthEnum  BthEnum.sys  Sat Apr 11 00:43:09 2009 (49E01FDD)
95d3e000 95d4d000   bthmodem bthmodem.sys Sat Apr 11 00:43:10 2009 (49E01FDE)
95d1a000 95d34000   bthpan   bthpan.sys   Sat Jan 19 00:53:44 2008 (47919068)
9651e000 9659e000   bthport  bthport.sys  Sat Apr 11 00:43:09 2009 (49E01FDD)
96511000 9651e000   BTHUSB   BTHUSB.sys   Sat Apr 11 00:43:08 2009 (49E01FDC)
9660d000 9668d000   btwaudio btwaudio.sys Tue Sep 04 15:38:00 2007 (46DDB418)
95d64000 95dcb000   btwavdt  btwavdt.sys  Thu Jul 12 19:04:57 2007 (4696B399)
96691000 96693500   btwrchid btwrchid.sys Thu Jul 12 19:06:31 2007 (4696B3F7)
98cf0000 98cfe000   cdd      cdd.dll      Thu Sep 24 21:27:02 2009 (4ABC1C66)
ae904000 ae91a000   cdfs     cdfs.sys     Sat Jan 19 00:28:02 2008 (47918A62)
8e7cc000 8e7e4000   cdrom    cdrom.sys    Sat Apr 11 00:39:17 2009 (49E01EF5)
806da000 807ba000   CI       CI.dll       Sat Apr 11 02:25:22 2009 (49E037D2)
8e954000 8e975000   CLASSPNP CLASSPNP.SYS Sat Apr 11 00:39:05 2009 (49E01EE9)
80699000 806da000   CLFS     CLFS.SYS     Sat Apr 11 00:13:51 2009 (49E018FF)
936e9000 936ec780   CmBatt   CmBatt.sys   Sat Jan 19 00:32:47 2008 (47918B7F)
85faf000 85fb1900   compbatt compbatt.sys Sat Jan 19 00:32:47 2008 (47918B7F)
966a9000 966b6000   crashdmp crashdmp.sys Sat Apr 11 00:39:12 2009 (49E01EF0)
8e975000 8e97e000   crcdisk  crcdisk.sys  Thu Nov 02 04:52:27 2006 (4549B1CB)
95d4d000 95d64000   dfsc     dfsc.sys     Sat Apr 11 00:14:12 2009 (49E01914)
8e943000 8e954000   disk     disk.sys     Sat Apr 11 00:39:14 2009 (49E01EF2)
955db000 95600000   drmk     drmk.sys     Sat Jan 19 01:53:02 2008 (47919E4E)
966b6000 96784000   dump_iaStor dump_iaStor.sys Tue Apr 15 20:07:31 2008 (48054343)
96784000 9678e000   Dxapi    Dxapi.sys    Sat Jan 19 00:36:12 2008 (47918C4C)
94d4a000 94deb000   dxgkrnl  dxgkrnl.sys  Thu Sep 24 21:27:14 2009 (4ABC1C72)
8e91c000 8e943000   ecache   ecache.sys   Sat Apr 11 00:40:12 2009 (49E01F2C)
965f7000 965fb900   ElbyCDIO ElbyCDIO.sys Fri Jan 01 12:20:32 2010 (4B3E2EE0)
8e145000 8e155000   fileinfo fileinfo.sys Sat Jan 19 00:34:27 2008 (47918BE3)
8e113000 8e145000   fltmgr   fltmgr.sys   Sat Apr 11 00:13:59 2009 (49E01907)
95bad000 95bb6000   Fs_Rec   Fs_Rec.SYS   Sat Jan 19 00:27:57 2008 (47918A5D)
8e4ef000 8e50a000   fwpkclnt fwpkclnt.sys Sat Apr 11 00:45:42 2009 (49E02076)
851cc000 851ff000   hal      halmacpi.dll Sat Apr 11 00:13:13 2009 (49E018D9)
8446c000 84476000   hcmon    hcmon.sys    Fri May 21 01:53:58 2010 (4BF61FF6)
9375d000 937ea000   HDAudBus HDAudBus.sys Sat Apr 11 00:42:41 2009 (49E01FC1)
8e9b9000 8e9c9000   HIDCLASS HIDCLASS.SYS Sat Apr 11 00:42:47 2009 (49E01FC7)
943f4000 943fa380   HIDPARSE HIDPARSE.SYS Sat Jan 19 00:53:16 2008 (4791904C)
943fb000 943ff180   HpqKbFiltr HpqKbFiltr.sys Mon Jun 18 18:12:03 2007 (46770333)
943f2000 943f3c00   HpqRemHid HpqRemHid.sys Wed Jul 11 11:30:21 2007 (4694F78D)
83253000 832c0000   HTTP     HTTP.sys     Sat Feb 20 15:53:31 2010 (4B804BCB)
8e9c9000 8e9dc000   i8042prt i8042prt.sys Sat Jan 19 00:49:17 2008 (47918F5D)
8e009000 8e0d7000   iaStor   iaStor.sys   Tue Apr 15 20:07:31 2008 (48054343)
85fcb000 85fd2000   intelide intelide.sys Sat Jan 19 00:49:42 2008 (47918F76)
936f6000 93705000   intelppm intelppm.sys Sat Jan 19 00:27:20 2008 (47918A38)
8e9dc000 8e9e7000   kbdclass kbdclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
95594000 9559d000   kbdhid   kbdhid.sys   Sat Apr 11 00:38:40 2009 (49E01ED0)
80609000 80610000   kdcom    kdcom.dll    Sat Apr 11 02:25:29 2009 (49E037D9)
8da0f000 8df31000   kl1      kl1.sys      Wed Jun 09 09:24:39 2010 (4C0F9617)
95c24000 95c2a000   kl2      kl2.sys      Wed Jun 09 09:24:35 2010 (4C0F9613)
95b2a000 95bad000   klif     klif.sys     Fri Oct 01 03:30:11 2010 (4CA58E03)
965ef000 965f7000   klim6    klim6.sys    Thu Apr 22 11:07:20 2010 (4BD06628)
94df7000 94e00000   klmouflt klmouflt.sys Mon Nov 02 11:26:08 2009 (4AEF0820)
9551e000 95548000   ks       ks.sys       Sat Apr 11 00:38:47 2009 (49E01ED7)
8e155000 8e1c6000   ksecdd   ksecdd.sys   Mon Jun 15 08:48:53 2009 (4A364335)
845c3000 845c7680   lirsgt   lirsgt.sys   Sun Jan 29 06:06:18 2006 (43DCA1AA)
95dd7000 95de7000   lltdio   lltdio.sys   Sat Jan 19 00:55:03 2008 (479190B7)
94007000 94007c80   lmimirr  lmimirr.sys  Tue Apr 10 18:32:11 2007 (461C106B)
845ca000 845d4000   LMIRfsDriver LMIRfsDriver.sys Mon Jul 14 12:26:22 2008 (487B7E2E)
9679d000 967b8000   luafv    luafv.sys    Sat Jan 19 00:30:35 2008 (47918AFB)
80610000 80680000   mcupdate mcupdate.dll Sat Apr 11 02:23:19 2009 (49E03757)
95b13000 95b20000   modem    modem.sys    Sat Jan 19 00:57:16 2008 (4791913C)
95b20000 95b2a000   MODEMCSA MODEMCSA.sys Sat Jan 19 00:57:16 2008 (4791913C)
ae9a1000 ae9b0000   monitor  monitor.sys  Sat Jan 19 00:52:19 2008 (47919013)
8e9e7000 8e9f2000   mouclass mouclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
85fe0000 85ff0000   mountmgr mountmgr.sys Sat Jan 19 00:49:13 2008 (47918F59)
832f6000 8330b000   mpsdrv   mpsdrv.sys   Sat Jan 19 00:54:45 2008 (479190A5)
8330b000 8332c000   mrxdav   mrxdav.sys   Sat Apr 11 00:14:39 2009 (49E0192F)
8332c000 8334b000   mrxsmb   mrxsmb.sys   Tue Feb 23 06:10:12 2010 (4B83B794)
8334b000 83384000   mrxsmb10 mrxsmb10.sys Tue Feb 23 06:10:17 2010 (4B83B799)
83384000 8339c000   mrxsmb20 mrxsmb20.sys Tue Feb 23 06:10:12 2010 (4B83B794)
8e0fd000 8e106000   msahci   msahci.sys   Thu Nov 02 04:51:36 2006 (4549B198)
95be0000 95beb000   Msfs     Msfs.SYS     Sat Jan 19 00:28:08 2008 (47918A68)
85f71000 85f79000   msisadrv msisadrv.sys Sat Jan 19 00:32:51 2008 (47918B83)
8e378000 8e3a7000   msiscsi  msiscsi.sys  Sat Apr 11 00:40:07 2009 (49E01F27)
8e312000 8e33d000   msrpc    msrpc.sys    Sat Apr 11 00:37:32 2009 (49E01E8C)
95548000 95552000   mssmbios mssmbios.sys Sat Jan 19 00:32:55 2008 (47918B87)
8e90d000 8e91c000   mup      mup.sys      Sat Apr 11 00:14:12 2009 (49E01914)
8e207000 8e312000   ndis     ndis.sys     Sat Apr 11 00:45:52 2009 (49E02080)
8e5f3000 8e5fe000   ndistapi ndistapi.sys Sat Jan 19 00:56:24 2008 (47919108)
83236000 83240000   ndisuio  ndisuio.sys  Sat Jan 19 00:55:40 2008 (479190DC)
8e1c6000 8e1e9000   ndiswan  ndiswan.sys  Sat Apr 11 00:46:31 2009 (49E020A7)
9559d000 955ae000   NDProxy  NDProxy.SYS  Sat Jan 19 00:56:28 2008 (4791910C)
95c70000 95c7e000   netbios  netbios.sys  Sat Jan 19 00:55:45 2008 (479190E1)
95c3e000 95c70000   netbt    netbt.sys    Sat Apr 11 00:45:35 2009 (49E0206F)
8e33d000 8e378000   NETIO    NETIO.SYS    Sat Apr 11 00:46:21 2009 (49E0209D)
9400a000 94392000   NETw5v32 NETw5v32.sys Fri Aug 29 02:48:42 2008 (48B79BCA)
95005000 954fff80   nlndis   nlndis.sys   Fri Aug 27 07:21:06 2010 (4C779FA2)
96009000 96510900   nltdi    nltdi.sys    Fri Aug 27 07:21:06 2010 (4C779FA2)
845d4000 845dab00   npf      npf.sys      Tue Nov 06 15:09:15 2007 (4730C9EB)
95beb000 95bf9000   Npfs     Npfs.SYS     Sat Apr 11 00:14:01 2009 (49E01909)
95d34000 95d3e000   nsiproxy nsiproxy.sys Sat Jan 19 00:55:50 2008 (479190E6)
84e13000 851cc000   nt       ntkrpamp.exe Tue Jun 08 10:36:44 2010 (4C0E557C)
8e602000 8e712000   Ntfs     Ntfs.sys     Sat Apr 11 00:14:34 2009 (49E0192A)
95bb6000 95bbd000   Null     Null.SYS     Sat Jan 19 00:49:12 2008 (47918F58)
845db000 845e2500   nvflash  nvflash.sys  Fri May 23 14:11:38 2008 (483708DA)
94609000 94d49200   nvlddmkm nvlddmkm.sys Tue Feb 26 16:41:16 2008 (47C4877C)
ae948000 ae94f500   nvoclock nvoclock.sys Fri Jun 06 15:28:32 2008 (48498FE0)
8320c000 83236000   nwifi    nwifi.sys    Sat Apr 11 00:43:27 2009 (49E01FEF)
943d4000 943e3300   ohci1394 ohci1394.sys Sat Apr 11 00:43:04 2009 (49E01FD8)
85fa0000 85faf000   partmgr  partmgr.sys  Sat Apr 11 00:39:19 2009 (49E01EF7)
85f79000 85fa0000   pci      pci.sys      Sat Apr 11 00:19:16 2009 (49E01A44)
85fd2000 85fe0000   PCIIDEX  PCIIDEX.SYS  Sat Apr 11 00:39:09 2009 (49E01EED)
95500000 9550b900   pcouffin pcouffin.sys Tue Dec 05 09:39:53 2006 (457584B9)
ae800000 ae8de000   peauth   peauth.sys   Mon Oct 23 04:55:32 2006 (453C8384)
955ae000 955db000   portcls  portcls.sys  Sat Apr 11 00:42:48 2009 (49E01FC8)
80680000 80691000   PSHED    PSHED.dll    Sat Apr 11 02:25:32 2009 (49E037DC)
84476000 8447a860   pstrip   pstrip.sys   Tue May 08 05:51:01 2007 (46404805)
845c8000 845c9800   RaInfo   RaInfo.sys   Fri Jan 04 13:57:12 2008 (477E8188)
959f3000 959fc000   rasacd   rasacd.sys   Sat Jan 19 00:56:31 2008 (4791910F)
8e7e4000 8e7fb000   rasl2tp  rasl2tp.sys  Sat Jan 19 00:56:33 2008 (47919111)
8e3e8000 8e3f7000   raspppoe raspppoe.sys Sat Apr 11 00:46:30 2009 (49E020A6)
8e1e9000 8e1fd000   raspptp  raspptp.sys  Sat Jan 19 00:56:34 2008 (47919112)
807ba000 807cf000   rassstp  rassstp.sys  Sat Apr 11 00:46:40 2009 (49E020B0)
95cde000 95d1a000   rdbss    rdbss.sys    Sat Apr 11 00:14:26 2009 (49E01922)
95bd0000 95bd8000   RDPCDD   RDPCDD.sys   Sat Jan 19 01:01:08 2008 (47919224)
95bd8000 95be0000   rdpencdd rdpencdd.sys Sat Jan 19 01:01:09 2008 (47919225)
ae967000 ae99a000   RDPWD    RDPWD.SYS    Sat Apr 11 00:51:22 2009 (49E021CA)
95c98000 95cc1000   rfcomm   rfcomm.sys   Sat Apr 11 00:43:12 2009 (49E01FE0)
937ea000 937f9000   rimmptsk rimmptsk.sys Sat Feb 24 00:42:21 2007 (45DFD03D)
8e9a5000 8e9b9000   rimsptsk rimsptsk.sys Tue Jan 23 02:40:19 2007 (45B5BBE3)
8e74b000 8e79c000   rixdptsk rixdptsk.sys Wed Mar 21 09:02:02 2007 (46012CCA)
83240000 83253000   rspndr   rspndr.sys   Sat Jan 19 00:55:03 2008 (479190B7)
95800000 959f2940   RTKVHDA  RTKVHDA.sys  Tue Jan 15 06:18:36 2008 (478C968C)
94392000 943d4000   Rtlh86   Rtlh86.sys   Thu Mar 04 08:49:57 2010 (4B8FBA85)
85f05000 85f2b000   SCSIPORT SCSIPORT.SYS Sat Jan 19 00:49:44 2008 (47918F78)
8e98b000 8e9a5000   sdbus    sdbus.sys    Sat Apr 11 00:19:14 2009 (49E01A42)
ae8de000 ae8e8000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
95c2a000 95c3e000   smb      smb.sys      Sat Apr 11 00:45:22 2009 (49E02062)
95a07000 95b12880   smserial smserial.sys Tue May 05 08:15:42 2009 (4A002DEE)
8e8e6000 8e90c020   snapman  snapman.sys  Wed Nov 25 12:34:26 2009 (4B0D6AA2)
8e8de000 8e8e6000   spldr    spldr.sys    Thu Jun 21 20:29:17 2007 (467B17DD)
85e09000 85efc000   spqe     spqe.sys     Sun Oct 11 16:54:02 2009 (4AD245EA)
93600000 936b0000   spsys    spsys.sys    Tue Mar 10 13:10:28 2009 (49B69F04)
84406000 84454000   srv      srv.sys      Mon Sep 06 09:45:36 2010 (4C84F080)
8339c000 833c4000   srv2     srv2.sys     Mon Sep 06 09:45:21 2010 (4C84F071)
832c0000 832dd000   srvnet   srvnet.sys   Mon Sep 06 09:45:18 2010 (4C84F06E)
8e3a7000 8e3e8000   storport storport.sys Sat Apr 11 00:39:19 2009 (49E01EF7)
9551c000 9551d380   swenum   swenum.sys   Sat Jan 19 00:49:20 2008 (47918F60)
8e79c000 8e7cb380   SynTP    SynTP.sys    Fri Jun 20 19:05:26 2008 (485C37B6)
94600000 94606280   tap0901  tap0901.sys  Thu Jul 31 18:41:54 2008 (48923FB2)
8e405000 8e4ef000   tcpip    tcpip.sys    Wed Jun 16 09:45:41 2010 (4C18D585)
ae8e8000 ae8f4000   tcpipreg tcpipreg.sys Tue Dec 08 12:26:18 2009 (4B1E8C3A)
8e9f2000 8e9fd000   TDI      TDI.SYS      Sat Jan 19 00:57:10 2008 (47919136)
8e803000 8e8ddb00   tdrpm251 tdrpm251.sys Fri Jul 31 10:00:11 2009 (4A72F8EB)
ae950000 ae95b000   tdtcp    tdtcp.sys    Sat Jan 19 01:01:08 2008 (47919224)
807e6000 807fc000   tdx      tdx.sys      Sat Apr 11 00:45:56 2009 (49E02084)
9550c000 9551c000   termdd   termdd.sys   Sat Apr 11 00:51:14 2009 (49E021C2)
967b8000 967c1480   tifsfilt tifsfilt.sys Fri Sep 12 10:50:40 2008 (48CA81C0)
8e50a000 8e598140   timntr   timntr.sys   Fri Oct 30 16:06:07 2009 (4AEB472F)
98cd0000 98cd9000   TSDDD    TSDDD.dll    Sat Jan 19 01:01:09 2008 (47919225)
ae95b000 ae967000   tssecsrv tssecsrv.sys Sat Jan 19 01:01:15 2008 (4791922B)
936e0000 936e9000   tunmp    tunmp.sys    Sat Jan 19 00:55:40 2008 (479190DC)
936d5000 936e0000   tunnel   tunnel.sys   Thu Feb 18 06:28:13 2010 (4B7D244D)
95552000 9555f000   umbus    umbus.sys    Sat Jan 19 00:53:40 2008 (47919064)
807cf000 807e6000   usbccgp  usbccgp.sys  Sat Jan 19 00:53:29 2008 (47919059)
94005000 94006700   USBD     USBD.SYS     Sat Jan 19 00:53:17 2008 (4791904D)
9374e000 9375d000   usbehci  usbehci.sys  Sat Apr 11 00:42:52 2009 (49E01FCC)
9555f000 95594000   usbhub   usbhub.sys   Sat Apr 11 00:43:14 2009 (49E01FE2)
93710000 9374e000   USBPORT  USBPORT.SYS  Sat Apr 11 00:42:55 2009 (49E01FCF)
ae9b0000 ae9c5000   USBSTOR  USBSTOR.SYS  Sat Apr 11 00:42:55 2009 (49E01FCF)
93705000 93710000   usbuhci  usbuhci.sys  Sat Jan 19 00:53:20 2008 (47919050)
95c03000 95c23b80   usbvideo usbvideo.sys Sat Jan 19 00:53:38 2008 (47919062)
95bc4000 95bd0000   vga      vga.sys      Sat Jan 19 00:52:06 2008 (47919006)
8e5d2000 8e5f3000   VIDEOPRT VIDEOPRT.SYS Sat Jan 19 00:52:10 2008 (4791900A)
8447b000 8448aa00   vmci     vmci.sys     Fri May 21 01:21:04 2010 (4BF61840)
94000000 94004600   VMkbd    VMkbd.sys    Fri May 21 02:43:42 2010 (4BF62B9E)
967f2000 967f4f00   VMNET    VMNET.SYS    Mon Aug 10 08:03:57 2009 (4A800CAD)
967e4000 967f2000   vmnetbridge vmnetbridge.sys Mon Aug 10 08:05:29 2009 (4A800D09)
ae8f4000 ae8f8c80   vmnetuserif vmnetuserif.sys Fri May 21 02:07:27 2010 (4BF6231F)
8448b000 84559e00   vmx86    vmx86.sys    Fri May 21 03:30:41 2010 (4BF636A1)
85fbc000 85fcb000   volmgr   volmgr.sys   Sat Jan 19 00:49:51 2008 (47918F7F)
8dfb0000 8dffa000   volmgrx  volmgrx.sys  Sat Apr 11 00:39:25 2009 (49E01EFD)
8e712000 8e74b000   volsnap  volsnap.sys  Sat Apr 11 00:39:37 2009 (49E01F09)
ae8f9000 ae8fcd80   vstor2_ws60 vstor2-ws60.sys Tue Apr 27 19:16:24 2010 (4BD77048)
95cc1000 95cd4000   wanarp   wanarp.sys   Sat Jan 19 00:56:31 2008 (4791910F)
94deb000 94df7000   watchdog watchdog.sys Sat Apr 11 00:22:43 2009 (49E01B13)
8df31000 8dfa2000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8dfa2000 8dfb0000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
98ab0000 98cb3000   win32k   win32k.sys   Mon Oct 18 09:31:09 2010 (4CBC4C1D)
ae8fd000 ae903440   windrvNT windrvNT.sys Mon May 10 04:42:04 2004 (409F405C)
936ed000 936f6000   wmiacpi  wmiacpi.sys  Sat Jan 19 00:32:47 2008 (47918B7F)
85efc000 85f05000   WMILIB   WMILIB.SYS   Sat Jan 19 00:53:08 2008 (47919044)
965e6000 965ef000   ws2ifsl  ws2ifsl.sys  Sat Jan 19 00:56:49 2008 (47919121)
967c2000 967dc000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)

moltenice · Mar 6, 2011

Haha that's amazing how your list corresponded to my BSOD after the verifier

Just a quick question, is that list your list of drivers or mine?

Anyways, I don't know if this matters but that afs driver was named 'AFS.SYS' (all in capital) so I don't know if that would have caused a problem or not... I have renamed it to afs.bup as you recommended and will see if these errors occur anymore and get back to you if the problem was fixed or not

Solved BSOD + Stuck on Waking up from Sleep

Attachments

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

Attachments

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer