BSOD 0x00000124 Need Assistance

coldshiver · Jun 20, 2009

Hey guys ive been having some trouble on my pc since about 2-3 months i'd say, can't think of anything new round that time cept win7 version updates. Got this PC since Feb 2009 so warranty on the components is still good, i bought the parts seperately but all at one shop though. Now i'm curious to know what the dumps point to, i myself am a semi-expert if thats the right word i know my way around the pc specially windows but have never read into dumps and sorts. As you might see in my post i have searched and tried allot of stuff but since 124 STOP errors seem to be hardware related mostly i think the dumps are my best shot at seeing whats broke at this point.

Problem:
* BSOD's - STOP: 0x00000124 during intense gaming 99% of the time.

Suspicion:
* Since the problem occured in the last 2 months i don't think its a software error even though i have updated Win7 in that period.
* Graphics Card is broke
* Processor is doing something wrong

Attachements:
* BSOD Screenshot
* 2 Minidumps
* Windows 7 i7 Chipset and Raid Drivers x64 & x86 Win7 RC
* Bios Settings 1 Bios2 Bios3 Bios4
* CPU-Z Shots

System:
Windows 7 Ultimate x64 (Build 7201)
Asus P6T Deluxe Mobo (v1) Mobo
Intel i7 920 CPU
6GB (3x2GB) OCZ Tripple-Channel Gold Series (1600mhz 8-8-8-24) Mem
Ati 4870 (1GB) Club3D OC edition GPU
Creative X-fi XtremeMusic PCI card Soundcard
Enermax Liberty ELT500AWT 500 Watt, 24 Pins (had this one since start 2008) PSU
Logitech G5 2007 Gaming mouse
Other: Iphone in Dock usb connected.
*EDIT* HD: SATA 4x 250GB (2 sets, 500GB in RAID-0 for speed)
* Onboard soundcard = disabled in bios
* So is my 2nd LAN ehternet port in bios

Software that should be noted:
AV: Avira Antivir Free
FireW: Windows 7 Firewall

Circumstances:
* Nothing is overclocked nor has it ever been. I even underclocked the GPU memory 25 Mhz since this card keeps flickering the screen every 15 seconds.
* After 20 mins or 2 hours and anywhere between that of gaming on either Left4Dead or Prototype i'm getting this blue screen.
* NOT had this error yet in the few other games i play like: SWAT4, Call of Duty 4... though i did cap cod4 at 100 frames per sec while it can perform upto 110-115 average, so the game will never realy stress the gpu 100% and swat 4 is not a very demanding game nowadays.
* Now in-game ive had the BSOD like 30 times now already but in the desktop only 1 time while i pulled out an old USB drive of mine i got a blue screen again. (not realy sure if it was the same BSOD code but i'm guessing it is since all the other times it was)
* I use the logitech drivers and ive played on 500Hz and 1000Hz response time.

Tried and not resolved the matter:
* Ran Memtest86+ (v2.11) for 10 hours more or less, did 10 passes, no errors
* Ran 3DMark twice Vantage v1.01 didn't see anything weird anomolies though it could not calculate the score at the end gave a flash script error (seems to be vantage since more people are having it since v1.0)
* Changed ATI drivers to older WDM ones and tried updating to the latest ones
* Clean Win7 install 7201 isntead of updated from 7100 to 7201 like i had before.
* Installed Vistax64 next to my Win7 and tried the game prototype on there with latest ati drivers.
* ATI manual Fan speed upto 85% constantly, temps seem ok no higher then 80 degrees peeked in Ati control panel
* Running Prototype with all other apps closed/disabled inlcuding Avira antivirus
* Disabled Bios - Advanced Processor Halt (C1E alike)
* Set my mem settings manually in bios since it auto detected on 9-9-9-24
* Updated my chipset drivers for Win7 for i7 Chipset 64bit which Intel released on their own site (Link)
* Set windows Power Management to Peformance and checked if Link State Power Management was off for PCI express.
* CPU temp seems ok too haven't seen higher then 65 degrees in speedfan

******* eXtreme Power Supply Calculator Lite v2.5 *******
System Type: 1 physical CPU
Motherboard: High End - Desktop
CPU: Intel Core i7 920 2667 MHz Bloomfield
CPU Utilization (TDP): 85% TDP
RAM: 3 Sticks DDR3 SDRAM
Video Card: ATI Radeon HD 4870
Video Type: Single Card
Regular SATA: 4 HDDs
DVD-RW/DVD+RW Drive: 1 Drive
Sound Blaster - All Models: Yes
USB: 3 Devices (Phone,mouse,keyboard and sometimes usb drive)
Fans
Regular: 2 Fans 120mm;
Keyboard and mouse: Yes
System Load: 90 %
Capacitor Aging (+ W %): 30 %

Recommended Wattage: 468 Watts

Cannot Try:
* Make sure the 32 bit access is enabled on the HDD in the BIOS. I coudn't find that function in my P6T Deluxe bios.

Possible last resort options:
* Update Mobo Bios even though everything worked fine before the 2 months.
* Update ATI firmware.
* Return the ATI inside my warranty but must be sure if its the one giving me the blues.

Replied suggestions already tried:
* SFC /scannow - Check integrity of System files - Windows Resource Protection did not find any integrity violations.
* Set Constant GPU Clock Speed - Used RivaTuner, and speeds are now not switching back & forth.

Todo status:
* Set manual volt settings - Voltage CPU on 1.3v now
* Update Mobo bios - Qued
(In bios EZ Flash with my fat32 usb stick.)

Updates:
1. Got CPU Voltage around 1.29v now, cpu-z shows 1.28v. I did allot of prototype and had no crashes yet, but the mobo is still idling on 46c and peaking round 50c.

2. Moved my ATI card all the way down (as far as it could anyway) and i placed my Creative Soundcard 2 slots above the ati instead of just under it blocking the fan. My current temps are:
System: 38c
CPU: 42c
GPU: 48c
Never been so cool haha

the soundcard blocking the fan realy stopped the heat from getting away and it made the mobo warmer too (or it was like ontop of the sensor or something). Have to check if stability is up though.

3. No more BSOD's, problem seems fixed! Hazaaah! thank you all guys much appreciated, if my pc stays stable i should donate.

aww yeah, playing: SkyMarshall Arts - Forever Gamer (Listen)

4. Correction, still have the BSOD's but VERY infrequent i can play for hours and hours or a whole day or 2 without. (still only happens in heavy games, like in anno 1404 this last time). If the crashes start to get to me i'm prolly do a firmware upgrade on Mobo bios then try the GPU firm if there is any.

5. Ok its been a while since i edited, and i have not had any issues with BSo'ds anymore.. so i guess the voltage fixed or atleast severely dimished my blue screens, thanks a bunch i will donate soon!

I donated a while ago through paypal. Thanks everyone, and hopefully i'l never have to be back

(no more pc problems hehe) cold out

zigzag3143 · Jun 20, 2009

Bsod

coldshiver said:
Hey guys ive been having some trouble on my pc since about 2-3 months i'd say, can't think of anything new round that time cept win7 version updates. Got this PC since Feb 2009 so warranty on the components is still good, i bought the parts seperately but all at one shop though. Now i'm curious to know what the dumps point to, i myself am a semi-expert if thats the right word i know my way around the pc specially windows but have never read into dumps and sorts. As you might see in my post i have searched and tried allot of stuff but since 124 STOP errors seem to be hardware related mostly i think the dumps are my best shot at seeing whats broke at this point.

Problem:
* BSOD's - STOP: 0x00000124 during intense gaming 99% of the time.

Suspicion:
* Since the problem occured in the last 2 months i don't think its a software error even though i have updated Win7 in that period.
* Graphics Card is broke
* Processor is doing something wrong

Attachements:
* BSOD Screenshot
* 2 Minidumps
* Windows 7 i7 Chipset and Raid Drivers x64 & x86 Win7 RC

System:
Windows 7 Ultimate x64 (Build 7201)
Asus P6T Deluxe Mobo (v1) Mobo
Intel i7 920 CPU
6GB (3x2GB) OCZ Tripple-Channel Gold Series (1600mhz 8-8-8-24) Mem
Ati 4870 (1GB) Club3D OC edition GPU
Creative X-fi XtremeMusic PCI card Soundcard
Enermax Liberty ELT500AWT 500 Watt, 24 Pins (had this one since start 2008) PSU
Logitech G5 2007 Gaming mouse
Other: Iphone in Dock usb connected.
* Onboard soundcard = disabled in bios
* So is my 2nd LAN ehternet port in bios

Software that should be noted:
AV: Avira Antivir Free
FireW: Windows 7 Firewall

Circumstances:
* Nothing is overclocked nor has it ever been. I even underclocked the memory 25 Mhz since this card keeps flickering the screen every 15 seconds.
* After 20 mins or 2 hours and anywhere between that of gaming on either Left4Dead or Prototype i'm getting this blue screen.
* NOT had this error yet in the few other games i play like: SWAT4, Call of Duty 4... though i did cap cod4 at 100 frames per sec while it can perform upto 110-115 average, so the game will never realy stress the gpu 100% and swat 4 is not a very demanding game nowadays.
* Now in-game ive had the BSOD like 30 times now already but in the desktop only 1 time while i pulled out an old USB drive of mine i got a blue screen again. (not realy sure if it was the same BSOD code but i'm guessing it is since all the other times it was)
* I use the logitech drivers and ive played on 500Hz and 1000Hz response time.

Tried and not resolved the matter:
* Ran Memtest86+ (v2.11) for 10 hours more or less, did 10 passes, no errors
* Ran 3DMark twice Vantage v1.01 didn't see anything weird anomolies though it could not calculate the score at the end gave a flash script error (seems to be vantage since more people are having it since v1.0)
* Changed ATI drivers to older WDM ones and tried updating to the latest ones
* Clean Win7 install 7201 isntead of updated from 7100 to 7201 like i had before.
* Installed Vistax64 next to my Win7 and tried the game prototype on there with latest ati drivers.
* ATI manual Fan speed upto 85% constantly, temps seem ok no higher then 80 degrees peeked in Ati control panel
* Running Prototype with all other apps closed/disabled inlcuding Avira antivirus
* Disabled Bios - Advanced Processor Halt (C1E alike)
* Set my mem settings manually in bios since it auto detected on 9-9-9-24
* Updated my chipset drivers for Win7 for i7 Chipset 64bit which Intel released on their own site (Link)
* Set windows Power Management to Peformance and checked if Link State Power Management was off for PCI express.
* CPU temp seems ok too haven't seen higher then 65 degrees in speedfan

Cannot Try:
* Make sure the 32 bit access is enabled on the HDD in the BIOS. I coudn't find that function in my P6T Deluxe bios.

Possible last resort options:
* Update Mobo Bios even though everything worked fine before the 2 months.
* Return the ATI inside my warranty but must be sure if its the one giving me the blues.

If i forgot anything i'm sorry and i will correct it
Now i sit and wait to be saved because i don't know what todo at this point :|

Hi and welcome to sevenforums
This is an awesome first post. consise, detailed, thorough. We have a resident expert on BSOD's. You might want to tap his expertise. His username is usamsa, and if anyone can help you he can. you might want to PM him and ask if he would be interested in taking a look

Hope this helps somewhat and welcome again

Ken

Dzomlija · Jun 20, 2009

I experienced the same thing months back with Vista x64, and originally thought it to be a hardware failure, because the 0x124 stop error usually occured after some intense disk activity.

And this is going to sound like a really odd solution, but it worked for me, and if your BIOS has settings to do so, it may very well work for you too.

Turn on your computer and go into the BIOS. Then find the entries pertaining to your hard disk controllers (IDE and SATA), then if a settings is available to change, make sure that "32-bit Disk Access" is turned on for all controller ports.

Like I said, and odd solution, but it worked, as you can see from the post I made in August 2007 on the Vista Forums: Solution to STOP 0x00000124

Orbital Shark · Jun 20, 2009

Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7201 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c9ae50
Debug session time: Sat Jun 20 00:31:27.022 2009 (GMT+1)
System Uptime: 0 days 1:47:27.959

You could also try running Command Prompt as Admin (Start, type CMD, right-click CMD and 'Run as Administrator).

From there type SFC /scannow

it looks like the ntoskrnl.exe file has something to do with it, and the SFC app will scan all system files for integrity errors and retore them to their former glory.

Hope this helps

P.S i wish ALL posts were as detailed as yours

Jeff

Frostbite · Jun 20, 2009

I had a similar problem a few months ago on my ATI 4870 which got fixed by installing a firmware upgrade. The problem was caused by ATI powerplay switching the speed of the graphics card mid game and locking up. Using ATI Tray Tools and setting the GPU to run at a set (full) speed also fixed it before I upgraded the firmware. May be something worth looking into.

coldshiver · Jun 20, 2009

Wow thanks for the compliments and replies so quickly

, i will try all of the solutions except the 32-bit access, since as i said in my first post

it is nowhere to be found in my bios settings. The firmware upgrade sounds familiar, i will try the ATI Tray tools first then since i'm not fan of flashing anything if not nessecary and i'l try the scanning of my system files (though like i said i have installed Vista aswell and that did not resolve the issue so i doubt its the system files though), i will also give usamsa a message

i'l keep you posted.

PS: Dzomlija, i have seen your thread

thats where i got the idea too hehe.

smarteyeball · Jun 20, 2009

Even though you're not overclocking, double check your vcore settings. If it's on auto, set it manually.

I was getting a lot of 0x124 errors because my volts were just a tad too low. Mine was because I was overclocking, but the symptoms sound similar to yours.

coldshiver · Jun 20, 2009

smarteyeball said:
Even though you're not overclocking, double check your vcore settings. If it's on auto, set it manually.

I was getting a lot of 0x124 errors because my volts were just a tad too low. Mine was because I was overclocking, but the symptoms sound similar to yours.

They are on auto, almost sure of it. But how do i know what manual volt settings i should set? I never messed with voltage before.

***** and ***

Frostbite said:
I had a similar problem a few months ago on my ATI 4870 which got fixed by installing a firmware upgrade. The problem was caused by ATI powerplay switching the speed of the graphics card mid game and locking up. Using ATI Tray Tools and setting the GPU to run at a set (full) speed also fixed it before I upgraded the firmware. May be something worth looking into.

Ok i got Ati Tray Tools running, now how do i force it to one speed? ive been looking around but nothing clear, could you point me through the right menus?
EDIT: Do i need to disable ATI Overdrive? or uninstall CCC entirely?

Frostbite · Jun 20, 2009

No need to un-install CCC. Can't remember if setting it in ATI Overdrive stopped the GPU from going back to 500 MHz on idle. Could try that first and watch the current clock settings and make sure it stays at the higher value you set it at when at the desktop.
I have posted a screenshot for the menu options for overclocking in ATI tray tools, just set the values at the normal clock settings for your card.

Make sure you tick 'Include clocks in Profile' and 'Load selected profile at startup' if you want to keep the settings for each program startup. Then hit the save button at the bottom to save a profile.

Warning

The two screenshots values are just for reference. Set them to your normal graphics card clocks.

smarteyeball · Jun 20, 2009

coldshiver said:
They are on auto, almost sure of it. But how do i know what manual volt settings i should set? I never messed with voltage before.

With the i7, you can no longer use software to identify your VID (the voltage that each chip reports it needs to run at stock). Each chip is different but between 1.12-1.2V is the average stock voltage.

Before adjusting the voltages, download CPU-Z and see what it's currently running at:

CPUID

(If you still have speedstep enabled, the voltages should still be fluctuating)

usasma · Jun 20, 2009

STOP 0x124 is a hardware error BUT there are different interpretations of what a hardware error is (and technically, all STOP errors are hardware errors).
In this case, a hardware error can be:
- busted hardware
- incompatible hardware
- hardware that needs a firmware update
- hardware that needs an adjustment (the RAM voltage issues)
- driver issues (least likely IME)

The point here is that the STOP 0x124 error is difficult to troubleshoot, and BSOD's rarely mention anything significant. The STOP 0x124 error is an error that's generated by the CPU (not by Windows as is usually the case), so it has different rules for it's analysis (and I don't understand them). But, as with any BSOD, the user's description is the critical thing to determine the cause.

Here's a link on how to generate the reports - and at the bottom is a link to a post where I described what I go through (in general) when looking through an analysis: Diagnosing Bsod's (originally posted 02Oct08) - Vox

In this case, the error occurs while gaming - which indicates to me that it's during a stressful situation that it happens. FYI - I have basically the identical system (512 mB on the same video card, RAID5 instead of RAID 0, and 12 gB of RAM). When building my system I considered a 650 watt PSU for the system, and wasn't satisfied that it would handle the load - so I opted for a 1000 watt PSU. While your requirements may vary, I wonder if 500 watts is enough to power all that stuff.

Try this power supply calculator and let us know what it says: eXtreme Power Supply Calculator Lite v2.5

Here's a summary of the dump files:

Code:

.
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Jun 19 16:17:33.988 2009 (GMT-4)
System Uptime: 0 days 2:02:29.924
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 124, {0, fffffa80072fe028, fe200040, 60114a}
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
Probably caused by : hardware
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Jun 19 19:31:27.022 2009 (GMT-4)
System Uptime: 0 days 1:47:27.959
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 124, {0, fffffa80072ec028, fe000000, 40014a}
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
Probably caused by : hardware
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
.
fffff880`045d8000 fffff880`045e0000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`0470e000 fffff880`04719000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`045d8000 fffff880`045e0000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`0470e000 fffff880`04719000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
fffff880`03dcd000 fffff880`03dd8000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`04591000 fffff880`04599000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`04591000 fffff880`04599000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`03dcd000 fffff880`03dd8000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)

Please note above the very outdated ASACPI.SYS driver - that could very well be an issue here. Please update that one ASAP.

Here's the actual analysis'. As is usual with STOP 0x124 errors, there isn't much info to go on. Also, because Win7 is still being developed, the errors about missing/incorrect symbols are not surprising.

Code:

Opened log file 'C:\Users\FUBAR-RC1-Desktop\TempDUMP\DATA\$99-dbug.txt'

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


Loading Dump File [C:\Users\FUBAR-RC1-Desktop\TempDUMP\DATA\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: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7201 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a5e000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Fri Jun 19 16:17:33.988 2009 (GMT-4)
System Uptime: 0 days 2:02:29.924
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80072fe028, fe200040, 60114a}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : hardware

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

1: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;.logclose;q
GetPointerFromAddress: unable to read from fffff80002d07000
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_ETHREAD                                   ***
***                                                                   ***
*************************************************************************
fffff880009fd0c0: Unable to get thread contents
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80072fe028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe200040, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000060114a, Low order 32-bits of the MCi_STATUS value.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  

Use '!findthebuild' command to search for the target build information.

If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80002a5e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`009fab58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x734c0


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

BUCKET_ID:  WRONG_SYMBOLS

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

rax=0000000000000000 rbx=00000000fe200040 rcx=0000000000000124
rdx=0000000000000000 rsi=0000000000000003 rdi=fffffa80072fe148
rip=fffff80002ad14c0 rsp=fffff880009fab58 rbp=fffffa8007097c29
 r8=fffffa80072fe028  r9=00000000fe200040 r10=000000000060114a
r11=0000000000000002 r12=fffff80002a15000 r13=fffffa8007097bd0
r14=fffffa800548d028 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
nt+0x734c0:
fffff800`02ad14c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff880`009fab60=????????????????
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`009fab58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x734c0
start             end                 module name
fffff800`00bcb000 fffff800`00bd5000   kdcom    kdcom.dll    Mon Jun 01 23:53:16 2009 (4A24A22C)
fffff800`02a15000 fffff800`02a5e000   hal      hal.dll      Mon Jun 01 23:50:01 2009 (4A24A169)
fffff800`02a5e000 fffff800`0303c000   nt       ntoskrnl.exe Mon Jun 01 22:01:18 2009 (4A2487EE)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jun 01 23:54:36 2009 (4A24A27C)
fffff880`00cc0000 fffff880`00ce1000   WudfPf   WudfPf.sys   Mon Jun 01 22:36:40 2009 (4A249038)
fffff880`00cea000 fffff880`00d2e000   mcupdate mcupdate.dll Mon Jun 01 23:51:07 2009 (4A24A1AB)
fffff880`00d2e000 fffff880`00d42000   PSHED    PSHED.dll    Mon Jun 01 23:54:44 2009 (4A24A284)
fffff880`00d42000 fffff880`00da0000   CLFS     CLFS.SYS     Mon Jun 01 21:50:15 2009 (4A248557)
fffff880`00da0000 fffff880`00dfc000   volmgrx  volmgrx.sys  Mon Jun 01 21:50:45 2009 (4A248575)
fffff880`00e00000 fffff880`00e57000   ACPI     ACPI.sys     Mon Jun 01 21:50:15 2009 (4A248557)
fffff880`00e57000 fffff880`00e60000   WMILIB   WMILIB.SYS   Mon Jun 01 21:50:14 2009 (4A248556)
fffff880`00e60000 fffff880`00e6a000   msisadrv msisadrv.sys Mon Jun 01 21:49:48 2009 (4A24853C)
fffff880`00e6a000 fffff880`00e9d000   pci      pci.sys      Mon Jun 01 21:50:09 2009 (4A248551)
fffff880`00e9d000 fffff880`00eaa000   vdrvroot vdrvroot.sys Mon Jun 01 22:32:17 2009 (4A248F31)
fffff880`00eaa000 fffff880`00ebf000   partmgr  partmgr.sys  Mon Jun 01 21:50:24 2009 (4A248560)
fffff880`00ebf000 fffff880`00ed4000   volmgr   volmgr.sys   Mon Jun 01 21:50:19 2009 (4A24855B)
fffff880`00ed4000 fffff880`00edb000   pciide   pciide.sys   Mon Jun 01 21:50:12 2009 (4A248554)
fffff880`00edb000 fffff880`00eeb000   PCIIDEX  PCIIDEX.SYS  Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`00ef9000 fffff880`00f9d000   Wdf01000 Wdf01000.sys Mon Jun 01 21:53:29 2009 (4A248619)
fffff880`00f9d000 fffff880`00fac000   WDFLDR   WDFLDR.SYS   Mon Jun 01 21:50:16 2009 (4A248558)
fffff880`00fac000 fffff880`00fc6000   mountmgr mountmgr.sys Mon Jun 01 21:50:17 2009 (4A248559)
fffff880`00fc6000 fffff880`00fd8000   umbus    umbus.sys    Mon Jun 01 22:37:45 2009 (4A249079)
fffff880`00fd8000 fffff880`00ff3000   avgntflt avgntflt.sys Tue Mar 24 10:00:46 2009 (49C8E78E)
fffff880`01000000 fffff880`01014000   fileinfo fileinfo.sys Mon Jun 01 22:05:35 2009 (4A2488EF)
fffff880`01014000 fffff880`01043000   SCSIPORT SCSIPORT.SYS Mon Jun 01 22:32:00 2009 (4A248F20)
fffff880`01049000 fffff880`01167000   iaStorV  iaStorV.sys  Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`01167000 fffff880`01170000   atapi    atapi.sys    Mon Jun 01 21:50:10 2009 (4A248552)
fffff880`01170000 fffff880`0119a000   ataport  ataport.SYS  Mon Jun 01 21:50:14 2009 (4A248556)
fffff880`0119a000 fffff880`011a5000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`011a5000 fffff880`011f1000   fltmgr   fltmgr.sys   Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`01230000 fffff880`0124e000   tdx      tdx.sys      Mon Jun 01 21:51:23 2009 (4A24859B)
fffff880`01259000 fffff880`013fc000   Ntfs     Ntfs.sys     Mon Jun 01 21:51:21 2009 (4A248599)
fffff880`01400000 fffff880`0143a000   rdyboost rdyboost.sys Mon Jun 01 22:05:46 2009 (4A2488FA)
fffff880`0143a000 fffff880`01474000   fvevol   fvevol.sys   Mon Jun 01 21:52:12 2009 (4A2485CC)
fffff880`01474000 fffff880`0148a000   disk     disk.sys     Mon Jun 01 21:50:21 2009 (4A24855D)
fffff880`014a0000 fffff880`014fe000   msrpc    msrpc.sys    Mon Jun 01 21:51:39 2009 (4A2485AB)
fffff880`014fe000 fffff880`01518000   ksecdd   ksecdd.sys   Mon Jun 01 21:51:06 2009 (4A24858A)
fffff880`01518000 fffff880`0158b000   cng      cng.sys      Mon Jun 01 22:20:05 2009 (4A248C55)
fffff880`0158b000 fffff880`0159c000   pcw      pcw.sys      Mon Jun 01 21:49:33 2009 (4A24852D)
fffff880`0159c000 fffff880`015a6000   Fs_Rec   Fs_Rec.sys   Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`015a6000 fffff880`015f2000   volsnap  volsnap.sys  Mon Jun 01 21:50:29 2009 (4A248565)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Mon Jun 01 22:21:02 2009 (4A248C8E)
fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Mon Jun 01 21:51:17 2009 (4A248595)
fffff880`01675000 fffff880`01685000   vmstorfl vmstorfl.sys Mon Jun 01 22:13:37 2009 (4A248AD1)
fffff880`01685000 fffff880`0168d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0168d000 fffff880`0169f000   mup      mup.sys      Mon Jun 01 21:53:54 2009 (4A248632)
fffff880`016a2000 fffff880`01794000   ndis     ndis.sys     Mon Jun 01 21:52:00 2009 (4A2485C0)
fffff880`01794000 fffff880`017f4000   NETIO    NETIO.SYS    Mon Jun 01 21:52:17 2009 (4A2485D1)
fffff880`017f4000 fffff880`017fd000   hwpolicy hwpolicy.sys Mon Jun 01 21:49:28 2009 (4A248528)
fffff880`01801000 fffff880`019ff000   tcpip    tcpip.sys    Mon Jun 01 21:55:19 2009 (4A248687)
fffff880`02a00000 fffff880`02ac8000   HTTP     HTTP.sys     Mon Jun 01 21:52:01 2009 (4A2485C1)
fffff880`02adc000 fffff880`02af4000   rspndr   rspndr.sys   Mon Jun 01 22:39:47 2009 (4A2490F3)
fffff880`02af4000 fffff880`02b12000   bowser   bowser.sys   Mon Jun 01 21:53:58 2009 (4A248636)
fffff880`02b12000 fffff880`02b2a000   mpsdrv   mpsdrv.sys   Mon Jun 01 22:39:19 2009 (4A2490D7)
fffff880`02b2a000 fffff880`02b56000   mrxsmb   mrxsmb.sys   Mon Jun 01 21:54:11 2009 (4A248643)
fffff880`02b56000 fffff880`02ba3000   mrxsmb10 mrxsmb10.sys Mon Jun 01 21:54:18 2009 (4A24864A)
fffff880`02ba3000 fffff880`02bc6000   mrxsmb20 mrxsmb20.sys Mon Jun 01 21:54:11 2009 (4A248643)
fffff880`02c00000 fffff880`02c11000   Npfs     Npfs.SYS     Mon Jun 01 21:50:21 2009 (4A24855D)
fffff880`02c11000 fffff880`02c1e000   TDI      TDI.SYS      Mon Jun 01 21:51:25 2009 (4A24859D)
fffff880`02c1e000 fffff880`02d3c000   dump_iaStorV dump_iaStorV.sys Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`02d3c000 fffff880`02d51000   lltdio   lltdio.sys   Mon Jun 01 22:39:46 2009 (4A2490F2)
fffff880`02d55000 fffff880`02d7f000   cdrom    cdrom.sys    Mon Jun 01 21:50:16 2009 (4A248558)
fffff880`02d7f000 fffff880`02d88000   Null     Null.SYS     Mon Jun 01 21:50:09 2009 (4A248551)
fffff880`02d88000 fffff880`02d8f000   Beep     Beep.SYS     Mon Jun 01 22:30:54 2009 (4A248EDE)
fffff880`02d8f000 fffff880`02d9d000   vga      vga.sys      Mon Jun 01 22:09:45 2009 (4A2489E9)
fffff880`02d9d000 fffff880`02dc2000   VIDEOPRT VIDEOPRT.SYS Mon Jun 01 22:09:49 2009 (4A2489ED)
fffff880`02dc2000 fffff880`02dd2000   watchdog watchdog.sys Mon Jun 01 22:08:37 2009 (4A2489A5)
fffff880`02dd2000 fffff880`02ddb000   RDPCDD   RDPCDD.sys   Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02ddb000 fffff880`02de4000   rdpencdd rdpencdd.sys Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02de4000 fffff880`02ded000   rdprefmp rdprefmp.sys Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02ded000 fffff880`02df8000   Msfs     Msfs.SYS     Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`04000000 fffff880`04051000   rdbss    rdbss.sys    Mon Jun 01 21:54:20 2009 (4A24864C)
fffff880`04054000 fffff880`040de000   afd      afd.sys      Mon Jun 01 21:51:45 2009 (4A2485B1)
fffff880`040de000 fffff880`04123000   netbt    netbt.sys    Mon Jun 01 21:51:26 2009 (4A24859E)
fffff880`04123000 fffff880`0412c000   wfplwf   wfplwf.sys   Mon Jun 01 22:40:25 2009 (4A249119)
fffff880`0412c000 fffff880`04152000   pacer    pacer.sys    Mon Jun 01 22:40:39 2009 (4A249127)
fffff880`04152000 fffff880`04161000   netbios  netbios.sys  Mon Jun 01 22:40:25 2009 (4A249119)
fffff880`04161000 fffff880`0417c000   wanarp   wanarp.sys   Mon Jun 01 22:41:24 2009 (4A249154)
fffff880`0417c000 fffff880`041ba000   truecrypt truecrypt.sys Sun May 10 14:48:02 2009 (4A072162)
fffff880`041ba000 fffff880`041ce000   termdd   termdd.sys   Mon Jun 01 22:47:14 2009 (4A2492B2)
fffff880`041ce000 fffff880`041da000   nsiproxy nsiproxy.sys Mon Jun 01 21:51:17 2009 (4A248595)
fffff880`041da000 fffff880`041e5000   mssmbios mssmbios.sys Mon Jun 01 22:02:07 2009 (4A24881F)
fffff880`041e5000 fffff880`041ef000   ElbyCDIO ElbyCDIO.sys Tue Feb 17 12:11:23 2009 (499AEFBB)
fffff880`041ef000 fffff880`041fe000   discache discache.sys Mon Jun 01 22:08:24 2009 (4A248998)
fffff880`04200000 fffff880`0420f000   kbdclass kbdclass.sys Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`0420f000 fffff880`0421e000   mouclass mouclass.sys Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`0421e000 fffff880`0422d000   VClone   VClone.sys   Fri May 22 19:08:37 2009 (4A173075)
fffff880`0422d000 fffff880`042b0000   csc      csc.sys      Mon Jun 01 21:54:46 2009 (4A248666)
fffff880`042b0000 fffff880`042ce000   dfsc     dfsc.sys     Mon Jun 01 21:53:55 2009 (4A248633)
fffff880`042ce000 fffff880`042df000   blbdrive blbdrive.sys Mon Jun 01 22:07:03 2009 (4A248947)
fffff880`042df000 fffff880`04305000   tunnel   tunnel.sys   Mon Jun 01 22:40:35 2009 (4A249123)
fffff880`04305000 fffff880`0431b000   intelppm intelppm.sys Mon Jun 01 21:50:10 2009 (4A248552)
fffff880`0431b000 fffff880`0437e000   yk62x64  yk62x64.sys  Mon Feb 23 10:02:27 2009 (49A2BA83)
fffff880`0437e000 fffff880`043ad000   ndiswan  ndiswan.sys  Mon Jun 01 22:41:13 2009 (4A249149)
fffff880`043ad000 fffff880`043ce000   raspptp  raspptp.sys  Mon Jun 01 22:41:18 2009 (4A24914E)
fffff880`043ce000 fffff880`043e8000   rassstp  rassstp.sys  Mon Jun 01 22:41:24 2009 (4A249154)
fffff880`043e8000 fffff880`043f3000   rdpbus   rdpbus.sys   Mon Jun 01 22:48:31 2009 (4A2492FF)
fffff880`04400000 fffff880`04410000   CompositeBus CompositeBus.sys Mon Jun 01 22:31:16 2009 (4A248EF4)
fffff880`04410000 fffff880`04426000   AgileVpn AgileVpn.sys Mon Jun 01 22:41:23 2009 (4A249153)
fffff880`04426000 fffff880`0444a000   rasl2tp  rasl2tp.sys  Mon Jun 01 22:41:13 2009 (4A249149)
fffff880`0444a000 fffff880`0444b480   swenum   swenum.sys   Mon Jun 01 22:31:01 2009 (4A248EE5)
fffff880`04451000 fffff880`044f6700   ctaud2k  ctaud2k.sys  Thu Apr 09 05:46:11 2009 (49DDC3E3)
fffff880`044f7000 fffff880`04534000   portcls  portcls.sys  Mon Jun 01 22:37:24 2009 (4A249064)
fffff880`04534000 fffff880`04556000   drmk     drmk.sys     Mon Jun 01 23:32:19 2009 (4A249D43)
fffff880`04556000 fffff880`04599000   ks       ks.sys       Mon Jun 01 22:31:10 2009 (4A248EEE)
fffff880`04599000 fffff880`045ca000   ctoss2k  ctoss2k.sys  Thu Apr 09 05:44:01 2009 (49DDC361)
fffff880`045ca000 fffff880`045d2000   ctprxy2k ctprxy2k.sys Thu Apr 09 05:46:13 2009 (49DDC3E5)
fffff880`045d2000 fffff880`045d7200   ksthunk  ksthunk.sys  Mon Jun 01 22:31:00 2009 (4A248EE4)
fffff880`045d8000 fffff880`045e0000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`045e0000 fffff880`045eb000   GEARAspiWDM GEARAspiWDM.sys Thu Mar 19 11:34:13 2009 (49C265F5)
fffff880`045eb000 fffff880`045f4000   wmiacpi  wmiacpi.sys  Mon Jun 01 22:02:00 2009 (4A248818)
fffff880`045f4000 fffff880`04600000   ndistapi ndistapi.sys Mon Jun 01 22:41:02 2009 (4A24913E)
fffff880`04668000 fffff880`0470e000   peauth   peauth.sys   Mon Jun 01 23:32:21 2009 (4A249D45)
fffff880`0470e000 fffff880`04719000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`04719000 fffff880`0472b000   tcpipreg tcpipreg.sys Mon Jun 01 22:40:46 2009 (4A24912E)
fffff880`0472b000 fffff880`04758000   srvnet   srvnet.sys   Mon Jun 01 21:55:00 2009 (4A248674)
fffff880`04758000 fffff880`047c1000   srv2     srv2.sys     Mon Jun 01 21:55:03 2009 (4A248677)
fffff880`04800000 fffff880`04824000   HDAudBus HDAudBus.sys Mon Jun 01 22:37:12 2009 (4A249058)
fffff880`04824000 fffff880`04831000   usbuhci  usbuhci.sys  Mon Jun 01 22:37:21 2009 (4A249061)
fffff880`04831000 fffff880`04887000   USBPORT  USBPORT.SYS  Mon Jun 01 22:37:25 2009 (4A249065)
fffff880`04887000 fffff880`04898000   usbehci  usbehci.sys  Mon Jun 01 22:37:25 2009 (4A249065)
fffff880`048a0000 fffff880`04ea4000   atikmdag atikmdag.sys Fri May 15 23:52:53 2009 (4A0E3895)
fffff880`04ea4000 fffff880`04f98000   dxgkrnl  dxgkrnl.sys  Mon Jun 01 22:09:50 2009 (4A2489EE)
fffff880`04f98000 fffff880`04fde000   dxgmms1  dxgmms1.sys  Mon Jun 01 22:09:33 2009 (4A2489DD)
fffff880`04fde000 fffff880`04ff9000   raspppoe raspppoe.sys Mon Jun 01 22:41:19 2009 (4A24914F)
fffff880`05200000 fffff880`052ae000   ctac32k  ctac32k.sys  Wed Jul 02 04:38:22 2008 (486B3E7E)
fffff880`052ae000 fffff880`052d1000   luafv    luafv.sys    Mon Jun 01 21:56:03 2009 (4A2486B3)
fffff880`052d3000 fffff880`0532d000   usbhub   usbhub.sys   Mon Jun 01 22:37:51 2009 (4A24907F)
fffff880`0532d000 fffff880`05342000   NDProxy  NDProxy.SYS  Mon Jun 01 22:41:05 2009 (4A249141)
fffff880`05342000 fffff880`05362000   AtiHdmi  AtiHdmi.sys  Tue Apr 28 13:31:58 2009 (49F73D8E)
fffff880`05362000 fffff880`0539a000   ctsfm2k  ctsfm2k.sys  Thu Apr 09 05:43:48 2009 (49DDC354)
fffff880`0539a000 fffff880`053cf000   CT20XUT  CT20XUT.SYS  Thu Apr 09 05:47:24 2009 (49DDC42C)
fffff880`053cf000 fffff880`053e2000   LHidFilt LHidFilt.Sys Fri Dec 19 02:38:04 2008 (494B4F5C)
fffff880`053e2000 fffff880`053f6000   LMouFilt LMouFilt.Sys Fri Dec 19 02:38:09 2008 (494B4F61)
fffff880`05c0b000 fffff880`05d8c000   ha20x2k  ha20x2k.sys  Thu Apr 09 05:45:37 2009 (49DDC3C1)
fffff880`05d8c000 fffff880`05dd6000   emupia2k emupia2k.sys Thu Apr 09 05:43:41 2009 (49DDC34D)
fffff880`05dd6000 fffff880`05df1000   CTHWIUT  CTHWIUT.SYS  Thu Apr 09 05:47:27 2009 (49DDC42F)
fffff880`05df1000 fffff880`05dff000   monitor  monitor.sys  Mon Jun 01 22:09:46 2009 (4A2489EA)
fffff880`05e00000 fffff880`05e0e000   kbdhid   kbdhid.sys   Mon Jun 01 22:31:03 2009 (4A248EE7)
fffff880`05e0e000 fffff880`05e2b000   usbccgp  usbccgp.sys  Mon Jun 01 22:37:33 2009 (4A24906D)
fffff880`05e37000 fffff880`05f94000   CTEXFIFX CTEXFIFX.SYS Thu Apr 09 05:47:19 2009 (49DDC427)
fffff880`05f94000 fffff880`05fa0000   Dxapi    Dxapi.sys    Mon Jun 01 22:09:23 2009 (4A2489D3)
fffff880`05fa0000 fffff880`05fae000   crashdmp crashdmp.sys Mon Jun 01 22:31:55 2009 (4A248F1B)
fffff880`05fae000 fffff880`05fc1000   dump_dumpfve dump_dumpfve.sys Mon Jun 01 21:52:00 2009 (4A2485C0)
fffff880`05fc1000 fffff880`05fcf000   hidusb   hidusb.sys   Mon Jun 01 22:37:17 2009 (4A24905D)
fffff880`05fcf000 fffff880`05fe8000   HIDCLASS HIDCLASS.SYS Mon Jun 01 22:37:16 2009 (4A24905C)
fffff880`05fe8000 fffff880`05ff0080   HIDPARSE HIDPARSE.SYS Mon Jun 01 22:37:15 2009 (4A24905B)
fffff880`05ff1000 fffff880`05ff2f00   USBD     USBD.SYS     Mon Jun 01 22:37:19 2009 (4A24905F)
fffff880`05ff3000 fffff880`06000000   mouhid   mouhid.sys   Mon Jun 01 22:31:03 2009 (4A248EE7)
fffff880`08433000 fffff880`084cb000   srv      srv.sys      Mon Jun 01 21:55:19 2009 (4A248687)
fffff880`0853c000 fffff880`08547000   asyncmac asyncmac.sys Mon Jun 01 22:41:12 2009 (4A249148)
fffff960`000a0000 fffff960`003af000   win32k   win32k.sys   Mon Jun 01 22:11:46 2009 (4A248A62)
fffff960`00580000 fffff960`0058a000   TSDDD    TSDDD.dll    Mon Jun 01 22:47:14 2009 (4A2492B2)
fffff960`00740000 fffff960`00767000   cdd      cdd.dll      Mon Jun 01 23:48:29 2009 (4A24A10D)

Unloaded modules:
fffff880`084cb000 fffff880`0853c000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0148a000 fffff880`01498000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02c24000 fffff880`02d42000   dump_iaStorV
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02d42000 fffff880`02d55000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
start             end                 module name
fffff880`00e00000 fffff880`00e57000   ACPI     ACPI.sys     Mon Jun 01 21:50:15 2009 (4A248557)
fffff880`04054000 fffff880`040de000   afd      afd.sys      Mon Jun 01 21:51:45 2009 (4A2485B1)
fffff880`04410000 fffff880`04426000   AgileVpn AgileVpn.sys Mon Jun 01 22:41:23 2009 (4A249153)
fffff880`0119a000 fffff880`011a5000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`045d8000 fffff880`045e0000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`0853c000 fffff880`08547000   asyncmac asyncmac.sys Mon Jun 01 22:41:12 2009 (4A249148)
fffff880`01167000 fffff880`01170000   atapi    atapi.sys    Mon Jun 01 21:50:10 2009 (4A248552)
fffff880`01170000 fffff880`0119a000   ataport  ataport.SYS  Mon Jun 01 21:50:14 2009 (4A248556)
fffff880`05342000 fffff880`05362000   AtiHdmi  AtiHdmi.sys  Tue Apr 28 13:31:58 2009 (49F73D8E)
fffff880`048a0000 fffff880`04ea4000   atikmdag atikmdag.sys Fri May 15 23:52:53 2009 (4A0E3895)
fffff880`00fd8000 fffff880`00ff3000   avgntflt avgntflt.sys Tue Mar 24 10:00:46 2009 (49C8E78E)
fffff880`02d88000 fffff880`02d8f000   Beep     Beep.SYS     Mon Jun 01 22:30:54 2009 (4A248EDE)
fffff880`042ce000 fffff880`042df000   blbdrive blbdrive.sys Mon Jun 01 22:07:03 2009 (4A248947)
fffff880`02af4000 fffff880`02b12000   bowser   bowser.sys   Mon Jun 01 21:53:58 2009 (4A248636)
fffff960`00740000 fffff960`00767000   cdd      cdd.dll      Mon Jun 01 23:48:29 2009 (4A24A10D)
fffff880`02d55000 fffff880`02d7f000   cdrom    cdrom.sys    Mon Jun 01 21:50:16 2009 (4A248558)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jun 01 23:54:36 2009 (4A24A27C)
fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`00d42000 fffff880`00da0000   CLFS     CLFS.SYS     Mon Jun 01 21:50:15 2009 (4A248557)
fffff880`01518000 fffff880`0158b000   cng      cng.sys      Mon Jun 01 22:20:05 2009 (4A248C55)
fffff880`04400000 fffff880`04410000   CompositeBus CompositeBus.sys Mon Jun 01 22:31:16 2009 (4A248EF4)
fffff880`05fa0000 fffff880`05fae000   crashdmp crashdmp.sys Mon Jun 01 22:31:55 2009 (4A248F1B)
fffff880`0422d000 fffff880`042b0000   csc      csc.sys      Mon Jun 01 21:54:46 2009 (4A248666)
fffff880`0539a000 fffff880`053cf000   CT20XUT  CT20XUT.SYS  Thu Apr 09 05:47:24 2009 (49DDC42C)
fffff880`05200000 fffff880`052ae000   ctac32k  ctac32k.sys  Wed Jul 02 04:38:22 2008 (486B3E7E)
fffff880`04451000 fffff880`044f6700   ctaud2k  ctaud2k.sys  Thu Apr 09 05:46:11 2009 (49DDC3E3)
fffff880`05e37000 fffff880`05f94000   CTEXFIFX CTEXFIFX.SYS Thu Apr 09 05:47:19 2009 (49DDC427)
fffff880`05dd6000 fffff880`05df1000   CTHWIUT  CTHWIUT.SYS  Thu Apr 09 05:47:27 2009 (49DDC42F)
fffff880`04599000 fffff880`045ca000   ctoss2k  ctoss2k.sys  Thu Apr 09 05:44:01 2009 (49DDC361)
fffff880`045ca000 fffff880`045d2000   ctprxy2k ctprxy2k.sys Thu Apr 09 05:46:13 2009 (49DDC3E5)
fffff880`05362000 fffff880`0539a000   ctsfm2k  ctsfm2k.sys  Thu Apr 09 05:43:48 2009 (49DDC354)
fffff880`042b0000 fffff880`042ce000   dfsc     dfsc.sys     Mon Jun 01 21:53:55 2009 (4A248633)
fffff880`041ef000 fffff880`041fe000   discache discache.sys Mon Jun 01 22:08:24 2009 (4A248998)
fffff880`01474000 fffff880`0148a000   disk     disk.sys     Mon Jun 01 21:50:21 2009 (4A24855D)
fffff880`04534000 fffff880`04556000   drmk     drmk.sys     Mon Jun 01 23:32:19 2009 (4A249D43)
fffff880`05fae000 fffff880`05fc1000   dump_dumpfve dump_dumpfve.sys Mon Jun 01 21:52:00 2009 (4A2485C0)
fffff880`02c1e000 fffff880`02d3c000   dump_iaStorV dump_iaStorV.sys Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`05f94000 fffff880`05fa0000   Dxapi    Dxapi.sys    Mon Jun 01 22:09:23 2009 (4A2489D3)
fffff880`04ea4000 fffff880`04f98000   dxgkrnl  dxgkrnl.sys  Mon Jun 01 22:09:50 2009 (4A2489EE)
fffff880`04f98000 fffff880`04fde000   dxgmms1  dxgmms1.sys  Mon Jun 01 22:09:33 2009 (4A2489DD)
fffff880`041e5000 fffff880`041ef000   ElbyCDIO ElbyCDIO.sys Tue Feb 17 12:11:23 2009 (499AEFBB)
fffff880`05d8c000 fffff880`05dd6000   emupia2k emupia2k.sys Thu Apr 09 05:43:41 2009 (49DDC34D)
fffff880`01000000 fffff880`01014000   fileinfo fileinfo.sys Mon Jun 01 22:05:35 2009 (4A2488EF)
fffff880`011a5000 fffff880`011f1000   fltmgr   fltmgr.sys   Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`0159c000 fffff880`015a6000   Fs_Rec   Fs_Rec.sys   Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`0143a000 fffff880`01474000   fvevol   fvevol.sys   Mon Jun 01 21:52:12 2009 (4A2485CC)
fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Mon Jun 01 21:51:17 2009 (4A248595)
fffff880`045e0000 fffff880`045eb000   GEARAspiWDM GEARAspiWDM.sys Thu Mar 19 11:34:13 2009 (49C265F5)
fffff880`05c0b000 fffff880`05d8c000   ha20x2k  ha20x2k.sys  Thu Apr 09 05:45:37 2009 (49DDC3C1)
fffff800`02a15000 fffff800`02a5e000   hal      hal.dll      Mon Jun 01 23:50:01 2009 (4A24A169)
fffff880`04800000 fffff880`04824000   HDAudBus HDAudBus.sys Mon Jun 01 22:37:12 2009 (4A249058)
fffff880`05fcf000 fffff880`05fe8000   HIDCLASS HIDCLASS.SYS Mon Jun 01 22:37:16 2009 (4A24905C)
fffff880`05fe8000 fffff880`05ff0080   HIDPARSE HIDPARSE.SYS Mon Jun 01 22:37:15 2009 (4A24905B)
fffff880`05fc1000 fffff880`05fcf000   hidusb   hidusb.sys   Mon Jun 01 22:37:17 2009 (4A24905D)
fffff880`02a00000 fffff880`02ac8000   HTTP     HTTP.sys     Mon Jun 01 21:52:01 2009 (4A2485C1)
fffff880`017f4000 fffff880`017fd000   hwpolicy hwpolicy.sys Mon Jun 01 21:49:28 2009 (4A248528)
fffff880`01049000 fffff880`01167000   iaStorV  iaStorV.sys  Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`04305000 fffff880`0431b000   intelppm intelppm.sys Mon Jun 01 21:50:10 2009 (4A248552)
fffff880`04200000 fffff880`0420f000   kbdclass kbdclass.sys Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`05e00000 fffff880`05e0e000   kbdhid   kbdhid.sys   Mon Jun 01 22:31:03 2009 (4A248EE7)
fffff800`00bcb000 fffff800`00bd5000   kdcom    kdcom.dll    Mon Jun 01 23:53:16 2009 (4A24A22C)
fffff880`04556000 fffff880`04599000   ks       ks.sys       Mon Jun 01 22:31:10 2009 (4A248EEE)
fffff880`014fe000 fffff880`01518000   ksecdd   ksecdd.sys   Mon Jun 01 21:51:06 2009 (4A24858A)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Mon Jun 01 22:21:02 2009 (4A248C8E)
fffff880`045d2000 fffff880`045d7200   ksthunk  ksthunk.sys  Mon Jun 01 22:31:00 2009 (4A248EE4)
fffff880`053cf000 fffff880`053e2000   LHidFilt LHidFilt.Sys Fri Dec 19 02:38:04 2008 (494B4F5C)
fffff880`02d3c000 fffff880`02d51000   lltdio   lltdio.sys   Mon Jun 01 22:39:46 2009 (4A2490F2)
fffff880`053e2000 fffff880`053f6000   LMouFilt LMouFilt.Sys Fri Dec 19 02:38:09 2008 (494B4F61)
fffff880`052ae000 fffff880`052d1000   luafv    luafv.sys    Mon Jun 01 21:56:03 2009 (4A2486B3)
fffff880`00cea000 fffff880`00d2e000   mcupdate mcupdate.dll Mon Jun 01 23:51:07 2009 (4A24A1AB)
fffff880`05df1000 fffff880`05dff000   monitor  monitor.sys  Mon Jun 01 22:09:46 2009 (4A2489EA)
fffff880`0420f000 fffff880`0421e000   mouclass mouclass.sys Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`05ff3000 fffff880`06000000   mouhid   mouhid.sys   Mon Jun 01 22:31:03 2009 (4A248EE7)
fffff880`00fac000 fffff880`00fc6000   mountmgr mountmgr.sys Mon Jun 01 21:50:17 2009 (4A248559)
fffff880`02b12000 fffff880`02b2a000   mpsdrv   mpsdrv.sys   Mon Jun 01 22:39:19 2009 (4A2490D7)
fffff880`02b2a000 fffff880`02b56000   mrxsmb   mrxsmb.sys   Mon Jun 01 21:54:11 2009 (4A248643)
fffff880`02b56000 fffff880`02ba3000   mrxsmb10 mrxsmb10.sys Mon Jun 01 21:54:18 2009 (4A24864A)
fffff880`02ba3000 fffff880`02bc6000   mrxsmb20 mrxsmb20.sys Mon Jun 01 21:54:11 2009 (4A248643)
fffff880`02ded000 fffff880`02df8000   Msfs     Msfs.SYS     Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`00e60000 fffff880`00e6a000   msisadrv msisadrv.sys Mon Jun 01 21:49:48 2009 (4A24853C)
fffff880`014a0000 fffff880`014fe000   msrpc    msrpc.sys    Mon Jun 01 21:51:39 2009 (4A2485AB)
fffff880`041da000 fffff880`041e5000   mssmbios mssmbios.sys Mon Jun 01 22:02:07 2009 (4A24881F)
fffff880`0168d000 fffff880`0169f000   mup      mup.sys      Mon Jun 01 21:53:54 2009 (4A248632)
fffff880`016a2000 fffff880`01794000   ndis     ndis.sys     Mon Jun 01 21:52:00 2009 (4A2485C0)
fffff880`045f4000 fffff880`04600000   ndistapi ndistapi.sys Mon Jun 01 22:41:02 2009 (4A24913E)
fffff880`0437e000 fffff880`043ad000   ndiswan  ndiswan.sys  Mon Jun 01 22:41:13 2009 (4A249149)
fffff880`0532d000 fffff880`05342000   NDProxy  NDProxy.SYS  Mon Jun 01 22:41:05 2009 (4A249141)
fffff880`04152000 fffff880`04161000   netbios  netbios.sys  Mon Jun 01 22:40:25 2009 (4A249119)
fffff880`040de000 fffff880`04123000   netbt    netbt.sys    Mon Jun 01 21:51:26 2009 (4A24859E)
fffff880`01794000 fffff880`017f4000   NETIO    NETIO.SYS    Mon Jun 01 21:52:17 2009 (4A2485D1)
fffff880`02c00000 fffff880`02c11000   Npfs     Npfs.SYS     Mon Jun 01 21:50:21 2009 (4A24855D)
fffff880`041ce000 fffff880`041da000   nsiproxy nsiproxy.sys Mon Jun 01 21:51:17 2009 (4A248595)
fffff800`02a5e000 fffff800`0303c000   nt       ntoskrnl.exe Mon Jun 01 22:01:18 2009 (4A2487EE)
fffff880`01259000 fffff880`013fc000   Ntfs     Ntfs.sys     Mon Jun 01 21:51:21 2009 (4A248599)
fffff880`02d7f000 fffff880`02d88000   Null     Null.SYS     Mon Jun 01 21:50:09 2009 (4A248551)
fffff880`0412c000 fffff880`04152000   pacer    pacer.sys    Mon Jun 01 22:40:39 2009 (4A249127)
fffff880`00eaa000 fffff880`00ebf000   partmgr  partmgr.sys  Mon Jun 01 21:50:24 2009 (4A248560)
fffff880`00e6a000 fffff880`00e9d000   pci      pci.sys      Mon Jun 01 21:50:09 2009 (4A248551)
fffff880`00ed4000 fffff880`00edb000   pciide   pciide.sys   Mon Jun 01 21:50:12 2009 (4A248554)
fffff880`00edb000 fffff880`00eeb000   PCIIDEX  PCIIDEX.SYS  Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`0158b000 fffff880`0159c000   pcw      pcw.sys      Mon Jun 01 21:49:33 2009 (4A24852D)
fffff880`04668000 fffff880`0470e000   peauth   peauth.sys   Mon Jun 01 23:32:21 2009 (4A249D45)
fffff880`044f7000 fffff880`04534000   portcls  portcls.sys  Mon Jun 01 22:37:24 2009 (4A249064)
fffff880`00d2e000 fffff880`00d42000   PSHED    PSHED.dll    Mon Jun 01 23:54:44 2009 (4A24A284)
fffff880`04426000 fffff880`0444a000   rasl2tp  rasl2tp.sys  Mon Jun 01 22:41:13 2009 (4A249149)
fffff880`04fde000 fffff880`04ff9000   raspppoe raspppoe.sys Mon Jun 01 22:41:19 2009 (4A24914F)
fffff880`043ad000 fffff880`043ce000   raspptp  raspptp.sys  Mon Jun 01 22:41:18 2009 (4A24914E)
fffff880`043ce000 fffff880`043e8000   rassstp  rassstp.sys  Mon Jun 01 22:41:24 2009 (4A249154)
fffff880`04000000 fffff880`04051000   rdbss    rdbss.sys    Mon Jun 01 21:54:20 2009 (4A24864C)
fffff880`043e8000 fffff880`043f3000   rdpbus   rdpbus.sys   Mon Jun 01 22:48:31 2009 (4A2492FF)
fffff880`02dd2000 fffff880`02ddb000   RDPCDD   RDPCDD.sys   Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02ddb000 fffff880`02de4000   rdpencdd rdpencdd.sys Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02de4000 fffff880`02ded000   rdprefmp rdprefmp.sys Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`01400000 fffff880`0143a000   rdyboost rdyboost.sys Mon Jun 01 22:05:46 2009 (4A2488FA)
fffff880`02adc000 fffff880`02af4000   rspndr   rspndr.sys   Mon Jun 01 22:39:47 2009 (4A2490F3)
fffff880`01014000 fffff880`01043000   SCSIPORT SCSIPORT.SYS Mon Jun 01 22:32:00 2009 (4A248F20)
fffff880`0470e000 fffff880`04719000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`01685000 fffff880`0168d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`08433000 fffff880`084cb000   srv      srv.sys      Mon Jun 01 21:55:19 2009 (4A248687)
fffff880`04758000 fffff880`047c1000   srv2     srv2.sys     Mon Jun 01 21:55:03 2009 (4A248677)
fffff880`0472b000 fffff880`04758000   srvnet   srvnet.sys   Mon Jun 01 21:55:00 2009 (4A248674)
fffff880`0444a000 fffff880`0444b480   swenum   swenum.sys   Mon Jun 01 22:31:01 2009 (4A248EE5)
fffff880`01801000 fffff880`019ff000   tcpip    tcpip.sys    Mon Jun 01 21:55:19 2009 (4A248687)
fffff880`04719000 fffff880`0472b000   tcpipreg tcpipreg.sys Mon Jun 01 22:40:46 2009 (4A24912E)
fffff880`02c11000 fffff880`02c1e000   TDI      TDI.SYS      Mon Jun 01 21:51:25 2009 (4A24859D)
fffff880`01230000 fffff880`0124e000   tdx      tdx.sys      Mon Jun 01 21:51:23 2009 (4A24859B)
fffff880`041ba000 fffff880`041ce000   termdd   termdd.sys   Mon Jun 01 22:47:14 2009 (4A2492B2)
fffff880`0417c000 fffff880`041ba000   truecrypt truecrypt.sys Sun May 10 14:48:02 2009 (4A072162)
fffff960`00580000 fffff960`0058a000   TSDDD    TSDDD.dll    Mon Jun 01 22:47:14 2009 (4A2492B2)
fffff880`042df000 fffff880`04305000   tunnel   tunnel.sys   Mon Jun 01 22:40:35 2009 (4A249123)
fffff880`00fc6000 fffff880`00fd8000   umbus    umbus.sys    Mon Jun 01 22:37:45 2009 (4A249079)
fffff880`05e0e000 fffff880`05e2b000   usbccgp  usbccgp.sys  Mon Jun 01 22:37:33 2009 (4A24906D)
fffff880`05ff1000 fffff880`05ff2f00   USBD     USBD.SYS     Mon Jun 01 22:37:19 2009 (4A24905F)
fffff880`04887000 fffff880`04898000   usbehci  usbehci.sys  Mon Jun 01 22:37:25 2009 (4A249065)
fffff880`052d3000 fffff880`0532d000   usbhub   usbhub.sys   Mon Jun 01 22:37:51 2009 (4A24907F)
fffff880`04831000 fffff880`04887000   USBPORT  USBPORT.SYS  Mon Jun 01 22:37:25 2009 (4A249065)
fffff880`04824000 fffff880`04831000   usbuhci  usbuhci.sys  Mon Jun 01 22:37:21 2009 (4A249061)
fffff880`0421e000 fffff880`0422d000   VClone   VClone.sys   Fri May 22 19:08:37 2009 (4A173075)
fffff880`00e9d000 fffff880`00eaa000   vdrvroot vdrvroot.sys Mon Jun 01 22:32:17 2009 (4A248F31)
fffff880`02d8f000 fffff880`02d9d000   vga      vga.sys      Mon Jun 01 22:09:45 2009 (4A2489E9)
fffff880`02d9d000 fffff880`02dc2000   VIDEOPRT VIDEOPRT.SYS Mon Jun 01 22:09:49 2009 (4A2489ED)
fffff880`01675000 fffff880`01685000   vmstorfl vmstorfl.sys Mon Jun 01 22:13:37 2009 (4A248AD1)
fffff880`00ebf000 fffff880`00ed4000   volmgr   volmgr.sys   Mon Jun 01 21:50:19 2009 (4A24855B)
fffff880`00da0000 fffff880`00dfc000   volmgrx  volmgrx.sys  Mon Jun 01 21:50:45 2009 (4A248575)
fffff880`015a6000 fffff880`015f2000   volsnap  volsnap.sys  Mon Jun 01 21:50:29 2009 (4A248565)
fffff880`04161000 fffff880`0417c000   wanarp   wanarp.sys   Mon Jun 01 22:41:24 2009 (4A249154)
fffff880`02dc2000 fffff880`02dd2000   watchdog watchdog.sys Mon Jun 01 22:08:37 2009 (4A2489A5)
fffff880`00ef9000 fffff880`00f9d000   Wdf01000 Wdf01000.sys Mon Jun 01 21:53:29 2009 (4A248619)
fffff880`00f9d000 fffff880`00fac000   WDFLDR   WDFLDR.SYS   Mon Jun 01 21:50:16 2009 (4A248558)
fffff880`04123000 fffff880`0412c000   wfplwf   wfplwf.sys   Mon Jun 01 22:40:25 2009 (4A249119)
fffff960`000a0000 fffff960`003af000   win32k   win32k.sys   Mon Jun 01 22:11:46 2009 (4A248A62)
fffff880`045eb000 fffff880`045f4000   wmiacpi  wmiacpi.sys  Mon Jun 01 22:02:00 2009 (4A248818)
fffff880`00e57000 fffff880`00e60000   WMILIB   WMILIB.SYS   Mon Jun 01 21:50:14 2009 (4A248556)
fffff880`00cc0000 fffff880`00ce1000   WudfPf   WudfPf.sys   Mon Jun 01 22:36:40 2009 (4A249038)
fffff880`0431b000 fffff880`0437e000   yk62x64  yk62x64.sys  Mon Feb 23 10:02:27 2009 (49A2BA83)

Unloaded modules:
fffff880`084cb000 fffff880`0853c000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0148a000 fffff880`01498000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02c24000 fffff880`02d42000   dump_iaStorV
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02d42000 fffff880`02d55000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`072fe028 00000000`fe200040 00000000`0060114a
Closing open log file C:\Users\FUBAR-RC1-Desktop\TempDUMP\DATA\$99-dbug.txt

.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
.
Opened log file 'C:\Users\FUBAR-RC1-Desktop\TempDUMP\DATA\$99-dbug.txt'

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


Loading Dump File [C:\Users\FUBAR-RC1-Desktop\TempDUMP\DATA\02.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: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7201 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c9ae50
Debug session time: Fri Jun 19 19:31:27.022 2009 (GMT-4)
System Uptime: 0 days 1:47:27.959
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80072ec028, fe000000, 40014a}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : hardware

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

4: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;.logclose;q
GetPointerFromAddress: unable to read from fffff80002d05000
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_ETHREAD                                   ***
***                                                                   ***
*************************************************************************
fffffa8009812060: Unable to get thread contents
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80072ec028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000040014a, Low order 32-bits of the MCi_STATUS value.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  

Use '!findthebuild' command to search for the target build information.

If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80002a5c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`009bab58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x734c0


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

BUCKET_ID:  WRONG_SYMBOLS

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

rax=0000000000000000 rbx=00000000fe000000 rcx=0000000000000124
rdx=0000000000000000 rsi=0000000000000003 rdi=fffffa80072ec148
rip=fffff80002acf4c0 rsp=fffff880009bab58 rbp=fffffa8007091c29
 r8=fffffa80072ec028  r9=00000000fe000000 r10=000000000040014a
r11=0000000000000002 r12=fffff80002a13000 r13=fffffa8007091bd0
r14=fffffa8005df3900 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206
nt+0x734c0:
fffff800`02acf4c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff880`009bab60=????????????????
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`009bab58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x734c0
start             end                 module name
fffff800`00ba1000 fffff800`00bab000   kdcom    kdcom.dll    Mon Jun 01 23:53:16 2009 (4A24A22C)
fffff800`02a13000 fffff800`02a5c000   hal      hal.dll      Mon Jun 01 23:50:01 2009 (4A24A169)
fffff800`02a5c000 fffff800`0303a000   nt       ntoskrnl.exe Mon Jun 01 22:01:18 2009 (4A2487EE)
fffff880`00c00000 fffff880`00c2f000   SCSIPORT SCSIPORT.SYS Mon Jun 01 22:32:00 2009 (4A248F20)
fffff880`00c43000 fffff880`00c87000   mcupdate mcupdate.dll Mon Jun 01 23:51:07 2009 (4A24A1AB)
fffff880`00c87000 fffff880`00c9b000   PSHED    PSHED.dll    Mon Jun 01 23:54:44 2009 (4A24A284)
fffff880`00c9b000 fffff880`00cf9000   CLFS     CLFS.SYS     Mon Jun 01 21:50:15 2009 (4A248557)
fffff880`00cf9000 fffff880`00db9000   CI       CI.dll       Mon Jun 01 23:54:36 2009 (4A24A27C)
fffff880`00db9000 fffff880`00dd3000   mountmgr mountmgr.sys Mon Jun 01 21:50:17 2009 (4A248559)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Mon Jun 01 21:50:45 2009 (4A248575)
fffff880`00e5f000 fffff880`00f03000   Wdf01000 Wdf01000.sys Mon Jun 01 21:53:29 2009 (4A248619)
fffff880`00f03000 fffff880`00f12000   WDFLDR   WDFLDR.SYS   Mon Jun 01 21:50:16 2009 (4A248558)
fffff880`00f12000 fffff880`00f69000   ACPI     ACPI.sys     Mon Jun 01 21:50:15 2009 (4A248557)
fffff880`00f69000 fffff880`00f72000   WMILIB   WMILIB.SYS   Mon Jun 01 21:50:14 2009 (4A248556)
fffff880`00f72000 fffff880`00f7c000   msisadrv msisadrv.sys Mon Jun 01 21:49:48 2009 (4A24853C)
fffff880`00f7c000 fffff880`00faf000   pci      pci.sys      Mon Jun 01 21:50:09 2009 (4A248551)
fffff880`00faf000 fffff880`00fbc000   vdrvroot vdrvroot.sys Mon Jun 01 22:32:17 2009 (4A248F31)
fffff880`00fbc000 fffff880`00fd1000   partmgr  partmgr.sys  Mon Jun 01 21:50:24 2009 (4A248560)
fffff880`00fd1000 fffff880`00fe6000   volmgr   volmgr.sys   Mon Jun 01 21:50:19 2009 (4A24855B)
fffff880`00fe6000 fffff880`00fed000   pciide   pciide.sys   Mon Jun 01 21:50:12 2009 (4A248554)
fffff880`00fed000 fffff880`00ffd000   PCIIDEX  PCIIDEX.SYS  Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`01000000 fffff880`01014000   fileinfo fileinfo.sys Mon Jun 01 22:05:35 2009 (4A2488EF)
fffff880`01014000 fffff880`01032000   tdx      tdx.sys      Mon Jun 01 21:51:23 2009 (4A24859B)
fffff880`01049000 fffff880`01167000   iaStorV  iaStorV.sys  Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`01167000 fffff880`01170000   atapi    atapi.sys    Mon Jun 01 21:50:10 2009 (4A248552)
fffff880`01170000 fffff880`0119a000   ataport  ataport.SYS  Mon Jun 01 21:50:14 2009 (4A248556)
fffff880`0119a000 fffff880`011a5000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`011a5000 fffff880`011f1000   fltmgr   fltmgr.sys   Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`01230000 fffff880`0123f000   VClone   VClone.sys   Fri May 22 19:08:37 2009 (4A173075)
fffff880`01244000 fffff880`013e7000   Ntfs     Ntfs.sys     Mon Jun 01 21:51:21 2009 (4A248599)
fffff880`013e7000 fffff880`013f9000   umbus    umbus.sys    Mon Jun 01 22:37:45 2009 (4A249079)
fffff880`01400000 fffff880`01416000   disk     disk.sys     Mon Jun 01 21:50:21 2009 (4A24855D)
fffff880`01424000 fffff880`01433000   discache discache.sys Mon Jun 01 22:08:24 2009 (4A248998)
fffff880`01435000 fffff880`01493000   msrpc    msrpc.sys    Mon Jun 01 21:51:39 2009 (4A2485AB)
fffff880`01493000 fffff880`014ad000   ksecdd   ksecdd.sys   Mon Jun 01 21:51:06 2009 (4A24858A)
fffff880`014ad000 fffff880`01520000   cng      cng.sys      Mon Jun 01 22:20:05 2009 (4A248C55)
fffff880`01520000 fffff880`01531000   pcw      pcw.sys      Mon Jun 01 21:49:33 2009 (4A24852D)
fffff880`01531000 fffff880`0153b000   Fs_Rec   Fs_Rec.sys   Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`0153b000 fffff880`01587000   volsnap  volsnap.sys  Mon Jun 01 21:50:29 2009 (4A248565)
fffff880`01587000 fffff880`015c1000   rdyboost rdyboost.sys Mon Jun 01 22:05:46 2009 (4A2488FA)
fffff880`015c1000 fffff880`015fb000   fvevol   fvevol.sys   Mon Jun 01 21:52:12 2009 (4A2485CC)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Mon Jun 01 22:21:02 2009 (4A248C8E)
fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Mon Jun 01 21:51:17 2009 (4A248595)
fffff880`01675000 fffff880`01685000   vmstorfl vmstorfl.sys Mon Jun 01 22:13:37 2009 (4A248AD1)
fffff880`01685000 fffff880`0168d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0168d000 fffff880`01696000   hwpolicy hwpolicy.sys Mon Jun 01 21:49:28 2009 (4A248528)
fffff880`01698000 fffff880`0178a000   ndis     ndis.sys     Mon Jun 01 21:52:00 2009 (4A2485C0)
fffff880`0178a000 fffff880`017ea000   NETIO    NETIO.SYS    Mon Jun 01 21:52:17 2009 (4A2485D1)
fffff880`017ea000 fffff880`017fc000   mup      mup.sys      Mon Jun 01 21:53:54 2009 (4A248632)
fffff880`01800000 fffff880`019fe000   tcpip    tcpip.sys    Mon Jun 01 21:55:19 2009 (4A248687)
fffff880`02c00000 fffff880`02c09000   RDPCDD   RDPCDD.sys   Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02c09000 fffff880`02c12000   rdpencdd rdpencdd.sys Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02c12000 fffff880`02c1b000   rdprefmp rdprefmp.sys Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02c1b000 fffff880`02c26000   Msfs     Msfs.SYS     Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`02c26000 fffff880`02c37000   Npfs     Npfs.SYS     Mon Jun 01 21:50:21 2009 (4A24855D)
fffff880`02c37000 fffff880`02c44000   TDI      TDI.SYS      Mon Jun 01 21:51:25 2009 (4A24859D)
fffff880`02c44000 fffff880`02d62000   dump_iaStorV dump_iaStorV.sys Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`02d7b000 fffff880`02da5000   cdrom    cdrom.sys    Mon Jun 01 21:50:16 2009 (4A248558)
fffff880`02da5000 fffff880`02dae000   Null     Null.SYS     Mon Jun 01 21:50:09 2009 (4A248551)
fffff880`02dae000 fffff880`02db5000   Beep     Beep.SYS     Mon Jun 01 22:30:54 2009 (4A248EDE)
fffff880`02db5000 fffff880`02dc3000   vga      vga.sys      Mon Jun 01 22:09:45 2009 (4A2489E9)
fffff880`02dc3000 fffff880`02de8000   VIDEOPRT VIDEOPRT.SYS Mon Jun 01 22:09:49 2009 (4A2489ED)
fffff880`02de8000 fffff880`02df8000   watchdog watchdog.sys Mon Jun 01 22:08:37 2009 (4A2489A5)
fffff880`03c00000 fffff880`03c2d000   srvnet   srvnet.sys   Mon Jun 01 21:55:00 2009 (4A248674)
fffff880`03c5f000 fffff880`03d27000   HTTP     HTTP.sys     Mon Jun 01 21:52:01 2009 (4A2485C1)
fffff880`03d27000 fffff880`03dcd000   peauth   peauth.sys   Mon Jun 01 23:32:21 2009 (4A249D45)
fffff880`03dcd000 fffff880`03dd8000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`03dd8000 fffff880`03dea000   tcpipreg tcpipreg.sys Mon Jun 01 22:40:46 2009 (4A24912E)
fffff880`04000000 fffff880`04051000   rdbss    rdbss.sys    Mon Jun 01 21:54:20 2009 (4A24864C)
fffff880`04051000 fffff880`0405d000   nsiproxy nsiproxy.sys Mon Jun 01 21:51:17 2009 (4A248595)
fffff880`0405d000 fffff880`04068000   mssmbios mssmbios.sys Mon Jun 01 22:02:07 2009 (4A24881F)
fffff880`04068000 fffff880`04072000   ElbyCDIO ElbyCDIO.sys Tue Feb 17 12:11:23 2009 (499AEFBB)
fffff880`0407b000 fffff880`04105000   afd      afd.sys      Mon Jun 01 21:51:45 2009 (4A2485B1)
fffff880`04105000 fffff880`0414a000   netbt    netbt.sys    Mon Jun 01 21:51:26 2009 (4A24859E)
fffff880`0414a000 fffff880`04153000   wfplwf   wfplwf.sys   Mon Jun 01 22:40:25 2009 (4A249119)
fffff880`04153000 fffff880`04179000   pacer    pacer.sys    Mon Jun 01 22:40:39 2009 (4A249127)
fffff880`04179000 fffff880`04188000   netbios  netbios.sys  Mon Jun 01 22:40:25 2009 (4A249119)
fffff880`04188000 fffff880`041a3000   wanarp   wanarp.sys   Mon Jun 01 22:41:24 2009 (4A249154)
fffff880`041a3000 fffff880`041e1000   truecrypt truecrypt.sys Sun May 10 14:48:02 2009 (4A072162)
fffff880`041e1000 fffff880`041f5000   termdd   termdd.sys   Mon Jun 01 22:47:14 2009 (4A2492B2)
fffff880`04200000 fffff880`0420f000   mouclass mouclass.sys Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`0421d000 fffff880`042a0000   csc      csc.sys      Mon Jun 01 21:54:46 2009 (4A248666)
fffff880`042a0000 fffff880`042be000   dfsc     dfsc.sys     Mon Jun 01 21:53:55 2009 (4A248633)
fffff880`042be000 fffff880`042cf000   blbdrive blbdrive.sys Mon Jun 01 22:07:03 2009 (4A248947)
fffff880`042cf000 fffff880`042f5000   tunnel   tunnel.sys   Mon Jun 01 22:40:35 2009 (4A249123)
fffff880`042f5000 fffff880`0430b000   intelppm intelppm.sys Mon Jun 01 21:50:10 2009 (4A248552)
fffff880`0430b000 fffff880`04361000   USBPORT  USBPORT.SYS  Mon Jun 01 22:37:25 2009 (4A249065)
fffff880`04361000 fffff880`043c4000   yk62x64  yk62x64.sys  Mon Feb 23 10:02:27 2009 (49A2BA83)
fffff880`043c4000 fffff880`043e5000   raspptp  raspptp.sys  Mon Jun 01 22:41:18 2009 (4A24914E)
fffff880`043e5000 fffff880`043f4000   kbdclass kbdclass.sys Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`0440a000 fffff880`044af700   ctaud2k  ctaud2k.sys  Thu Apr 09 05:46:11 2009 (49DDC3E3)
fffff880`044b0000 fffff880`044ed000   portcls  portcls.sys  Mon Jun 01 22:37:24 2009 (4A249064)
fffff880`044ed000 fffff880`0450f000   drmk     drmk.sys     Mon Jun 01 23:32:19 2009 (4A249D43)
fffff880`0450f000 fffff880`04552000   ks       ks.sys       Mon Jun 01 22:31:10 2009 (4A248EEE)
fffff880`04552000 fffff880`04583000   ctoss2k  ctoss2k.sys  Thu Apr 09 05:44:01 2009 (49DDC361)
fffff880`04583000 fffff880`0458b000   ctprxy2k ctprxy2k.sys Thu Apr 09 05:46:13 2009 (49DDC3E5)
fffff880`0458b000 fffff880`04590200   ksthunk  ksthunk.sys  Mon Jun 01 22:31:00 2009 (4A248EE4)
fffff880`04591000 fffff880`04599000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`04599000 fffff880`045a4000   GEARAspiWDM GEARAspiWDM.sys Thu Mar 19 11:34:13 2009 (49C265F5)
fffff880`045a4000 fffff880`045ad000   wmiacpi  wmiacpi.sys  Mon Jun 01 22:02:00 2009 (4A248818)
fffff880`045ad000 fffff880`045bd000   CompositeBus CompositeBus.sys Mon Jun 01 22:31:16 2009 (4A248EF4)
fffff880`045bd000 fffff880`045d3000   AgileVpn AgileVpn.sys Mon Jun 01 22:41:23 2009 (4A249153)
fffff880`045d3000 fffff880`045f7000   rasl2tp  rasl2tp.sys  Mon Jun 01 22:41:13 2009 (4A249149)
fffff880`045f7000 fffff880`045f8480   swenum   swenum.sys   Mon Jun 01 22:31:01 2009 (4A248EE5)
fffff880`04800000 fffff880`0482f000   ndiswan  ndiswan.sys  Mon Jun 01 22:41:13 2009 (4A249149)
fffff880`0482f000 fffff880`04849000   rassstp  rassstp.sys  Mon Jun 01 22:41:24 2009 (4A249154)
fffff880`04849000 fffff880`04e4d000   atikmdag atikmdag.sys Fri May 15 23:52:53 2009 (4A0E3895)
fffff880`04e4d000 fffff880`04f41000   dxgkrnl  dxgkrnl.sys  Mon Jun 01 22:09:50 2009 (4A2489EE)
fffff880`04f41000 fffff880`04f87000   dxgmms1  dxgmms1.sys  Mon Jun 01 22:09:33 2009 (4A2489DD)
fffff880`04f87000 fffff880`04fab000   HDAudBus HDAudBus.sys Mon Jun 01 22:37:12 2009 (4A249058)
fffff880`04fab000 fffff880`04fb8000   usbuhci  usbuhci.sys  Mon Jun 01 22:37:21 2009 (4A249061)
fffff880`04fb8000 fffff880`04fc9000   usbehci  usbehci.sys  Mon Jun 01 22:37:25 2009 (4A249065)
fffff880`04fc9000 fffff880`04fd5000   ndistapi ndistapi.sys Mon Jun 01 22:41:02 2009 (4A24913E)
fffff880`04fd5000 fffff880`04ff0000   raspppoe raspppoe.sys Mon Jun 01 22:41:19 2009 (4A24914F)
fffff880`04ff0000 fffff880`04ffb000   rdpbus   rdpbus.sys   Mon Jun 01 22:48:31 2009 (4A2492FF)
fffff880`05200000 fffff880`05269000   srv2     srv2.sys     Mon Jun 01 21:55:03 2009 (4A248677)
fffff880`05294000 fffff880`052ee000   usbhub   usbhub.sys   Mon Jun 01 22:37:51 2009 (4A24907F)
fffff880`052ee000 fffff880`05303000   NDProxy  NDProxy.SYS  Mon Jun 01 22:41:05 2009 (4A249141)
fffff880`05303000 fffff880`05323000   AtiHdmi  AtiHdmi.sys  Tue Apr 28 13:31:58 2009 (49F73D8E)
fffff880`05323000 fffff880`0535b000   ctsfm2k  ctsfm2k.sys  Thu Apr 09 05:43:48 2009 (49DDC354)
fffff880`0535b000 fffff880`05387000   mrxsmb   mrxsmb.sys   Mon Jun 01 21:54:11 2009 (4A248643)
fffff880`05387000 fffff880`053d4000   mrxsmb10 mrxsmb10.sys Mon Jun 01 21:54:18 2009 (4A24864A)
fffff880`053d4000 fffff880`053f7000   mrxsmb20 mrxsmb20.sys Mon Jun 01 21:54:11 2009 (4A248643)
fffff880`05e1a000 fffff880`05f9b000   ha20x2k  ha20x2k.sys  Thu Apr 09 05:45:37 2009 (49DDC3C1)
fffff880`05f9b000 fffff880`05fe5000   emupia2k emupia2k.sys Thu Apr 09 05:43:41 2009 (49DDC34D)
fffff880`06000000 fffff880`0601b000   avgntflt avgntflt.sys Tue Mar 24 10:00:46 2009 (49C8E78E)
fffff880`0601b000 fffff880`0603c000   WudfPf   WudfPf.sys   Mon Jun 01 22:36:40 2009 (4A249038)
fffff880`0603c000 fffff880`06051000   lltdio   lltdio.sys   Mon Jun 01 22:39:46 2009 (4A2490F2)
fffff880`06051000 fffff880`06069000   rspndr   rspndr.sys   Mon Jun 01 22:39:47 2009 (4A2490F3)
fffff880`06069000 fffff880`06087000   bowser   bowser.sys   Mon Jun 01 21:53:58 2009 (4A248636)
fffff880`06098000 fffff880`06146000   ctac32k  ctac32k.sys  Wed Jul 02 04:38:22 2008 (486B3E7E)
fffff880`06161000 fffff880`06196000   CT20XUT  CT20XUT.SYS  Thu Apr 09 05:47:24 2009 (49DDC42C)
fffff880`06196000 fffff880`061a3000   mouhid   mouhid.sys   Mon Jun 01 22:31:03 2009 (4A248EE7)
fffff880`061a3000 fffff880`061b7000   LMouFilt LMouFilt.Sys Fri Dec 19 02:38:09 2008 (494B4F61)
fffff880`061b7000 fffff880`061c5000   monitor  monitor.sys  Mon Jun 01 22:09:46 2009 (4A2489EA)
fffff880`061c5000 fffff880`061e8000   luafv    luafv.sys    Mon Jun 01 21:56:03 2009 (4A2486B3)
fffff880`061e8000 fffff880`06200000   mpsdrv   mpsdrv.sys   Mon Jun 01 22:39:19 2009 (4A2490D7)
fffff880`06600000 fffff880`0660e000   hidusb   hidusb.sys   Mon Jun 01 22:37:17 2009 (4A24905D)
fffff880`0660e000 fffff880`06627000   HIDCLASS HIDCLASS.SYS Mon Jun 01 22:37:16 2009 (4A24905C)
fffff880`06627000 fffff880`0662f080   HIDPARSE HIDPARSE.SYS Mon Jun 01 22:37:15 2009 (4A24905B)
fffff880`06630000 fffff880`06631f00   USBD     USBD.SYS     Mon Jun 01 22:37:19 2009 (4A24905F)
fffff880`06632000 fffff880`06640000   kbdhid   kbdhid.sys   Mon Jun 01 22:31:03 2009 (4A248EE7)
fffff880`06640000 fffff880`0665d000   usbccgp  usbccgp.sys  Mon Jun 01 22:37:33 2009 (4A24906D)
fffff880`0665d000 fffff880`06670000   LHidFilt LHidFilt.Sys Fri Dec 19 02:38:04 2008 (494B4F5C)
fffff880`06675000 fffff880`067d2000   CTEXFIFX CTEXFIFX.SYS Thu Apr 09 05:47:19 2009 (49DDC427)
fffff880`067d2000 fffff880`067de000   Dxapi    Dxapi.sys    Mon Jun 01 22:09:23 2009 (4A2489D3)
fffff880`067de000 fffff880`067ec000   crashdmp crashdmp.sys Mon Jun 01 22:31:55 2009 (4A248F1B)
fffff880`067ec000 fffff880`067ff000   dump_dumpfve dump_dumpfve.sys Mon Jun 01 21:52:00 2009 (4A2485C0)
fffff880`0808f000 fffff880`08127000   srv      srv.sys      Mon Jun 01 21:55:19 2009 (4A248687)
fffff880`08198000 fffff880`081a8000   usbaapl64 usbaapl64.sys Wed Apr 15 14:58:13 2009 (49E62E45)
fffff880`081a8000 fffff880`081b3000   asyncmac asyncmac.sys Mon Jun 01 22:41:12 2009 (4A249148)
fffff880`081b3000 fffff880`081c4000   WinUsb   WinUsb.sys   Mon Jun 01 22:37:22 2009 (4A249062)
fffff880`081c4000 fffff880`081f5000   WUDFRd   WUDFRd.sys   Mon Jun 01 22:37:05 2009 (4A249051)
fffff960`000a0000 fffff960`003af000   win32k   win32k.sys   Mon Jun 01 22:11:46 2009 (4A248A62)
fffff960`00590000 fffff960`0059a000   TSDDD    TSDDD.dll    Mon Jun 01 22:47:14 2009 (4A2492B2)
fffff960`006b0000 fffff960`006d7000   cdd      cdd.dll      Mon Jun 01 23:48:29 2009 (4A24A10D)

Unloaded modules:
fffff880`08051000 fffff880`0806c000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`08036000 fffff880`08051000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0801b000 fffff880`08036000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`08000000 fffff880`0801b000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`06146000 fffff880`06161000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`08127000 fffff880`08198000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01416000 fffff880`01424000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02c4a000 fffff880`02d68000   dump_iaStorV
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02d68000 fffff880`02d7b000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
start             end                 module name
fffff880`00f12000 fffff880`00f69000   ACPI     ACPI.sys     Mon Jun 01 21:50:15 2009 (4A248557)
fffff880`0407b000 fffff880`04105000   afd      afd.sys      Mon Jun 01 21:51:45 2009 (4A2485B1)
fffff880`045bd000 fffff880`045d3000   AgileVpn AgileVpn.sys Mon Jun 01 22:41:23 2009 (4A249153)
fffff880`0119a000 fffff880`011a5000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`04591000 fffff880`04599000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`081a8000 fffff880`081b3000   asyncmac asyncmac.sys Mon Jun 01 22:41:12 2009 (4A249148)
fffff880`01167000 fffff880`01170000   atapi    atapi.sys    Mon Jun 01 21:50:10 2009 (4A248552)
fffff880`01170000 fffff880`0119a000   ataport  ataport.SYS  Mon Jun 01 21:50:14 2009 (4A248556)
fffff880`05303000 fffff880`05323000   AtiHdmi  AtiHdmi.sys  Tue Apr 28 13:31:58 2009 (49F73D8E)
fffff880`04849000 fffff880`04e4d000   atikmdag atikmdag.sys Fri May 15 23:52:53 2009 (4A0E3895)
fffff880`06000000 fffff880`0601b000   avgntflt avgntflt.sys Tue Mar 24 10:00:46 2009 (49C8E78E)
fffff880`02dae000 fffff880`02db5000   Beep     Beep.SYS     Mon Jun 01 22:30:54 2009 (4A248EDE)
fffff880`042be000 fffff880`042cf000   blbdrive blbdrive.sys Mon Jun 01 22:07:03 2009 (4A248947)
fffff880`06069000 fffff880`06087000   bowser   bowser.sys   Mon Jun 01 21:53:58 2009 (4A248636)
fffff960`006b0000 fffff960`006d7000   cdd      cdd.dll      Mon Jun 01 23:48:29 2009 (4A24A10D)
fffff880`02d7b000 fffff880`02da5000   cdrom    cdrom.sys    Mon Jun 01 21:50:16 2009 (4A248558)
fffff880`00cf9000 fffff880`00db9000   CI       CI.dll       Mon Jun 01 23:54:36 2009 (4A24A27C)
fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`00c9b000 fffff880`00cf9000   CLFS     CLFS.SYS     Mon Jun 01 21:50:15 2009 (4A248557)
fffff880`014ad000 fffff880`01520000   cng      cng.sys      Mon Jun 01 22:20:05 2009 (4A248C55)
fffff880`045ad000 fffff880`045bd000   CompositeBus CompositeBus.sys Mon Jun 01 22:31:16 2009 (4A248EF4)
fffff880`067de000 fffff880`067ec000   crashdmp crashdmp.sys Mon Jun 01 22:31:55 2009 (4A248F1B)
fffff880`0421d000 fffff880`042a0000   csc      csc.sys      Mon Jun 01 21:54:46 2009 (4A248666)
fffff880`06161000 fffff880`06196000   CT20XUT  CT20XUT.SYS  Thu Apr 09 05:47:24 2009 (49DDC42C)
fffff880`06098000 fffff880`06146000   ctac32k  ctac32k.sys  Wed Jul 02 04:38:22 2008 (486B3E7E)
fffff880`0440a000 fffff880`044af700   ctaud2k  ctaud2k.sys  Thu Apr 09 05:46:11 2009 (49DDC3E3)
fffff880`06675000 fffff880`067d2000   CTEXFIFX CTEXFIFX.SYS Thu Apr 09 05:47:19 2009 (49DDC427)
fffff880`04552000 fffff880`04583000   ctoss2k  ctoss2k.sys  Thu Apr 09 05:44:01 2009 (49DDC361)
fffff880`04583000 fffff880`0458b000   ctprxy2k ctprxy2k.sys Thu Apr 09 05:46:13 2009 (49DDC3E5)
fffff880`05323000 fffff880`0535b000   ctsfm2k  ctsfm2k.sys  Thu Apr 09 05:43:48 2009 (49DDC354)
fffff880`042a0000 fffff880`042be000   dfsc     dfsc.sys     Mon Jun 01 21:53:55 2009 (4A248633)
fffff880`01424000 fffff880`01433000   discache discache.sys Mon Jun 01 22:08:24 2009 (4A248998)
fffff880`01400000 fffff880`01416000   disk     disk.sys     Mon Jun 01 21:50:21 2009 (4A24855D)
fffff880`044ed000 fffff880`0450f000   drmk     drmk.sys     Mon Jun 01 23:32:19 2009 (4A249D43)
fffff880`067ec000 fffff880`067ff000   dump_dumpfve dump_dumpfve.sys Mon Jun 01 21:52:00 2009 (4A2485C0)
fffff880`02c44000 fffff880`02d62000   dump_iaStorV dump_iaStorV.sys Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`067d2000 fffff880`067de000   Dxapi    Dxapi.sys    Mon Jun 01 22:09:23 2009 (4A2489D3)
fffff880`04e4d000 fffff880`04f41000   dxgkrnl  dxgkrnl.sys  Mon Jun 01 22:09:50 2009 (4A2489EE)
fffff880`04f41000 fffff880`04f87000   dxgmms1  dxgmms1.sys  Mon Jun 01 22:09:33 2009 (4A2489DD)
fffff880`04068000 fffff880`04072000   ElbyCDIO ElbyCDIO.sys Tue Feb 17 12:11:23 2009 (499AEFBB)
fffff880`05f9b000 fffff880`05fe5000   emupia2k emupia2k.sys Thu Apr 09 05:43:41 2009 (49DDC34D)
fffff880`01000000 fffff880`01014000   fileinfo fileinfo.sys Mon Jun 01 22:05:35 2009 (4A2488EF)
fffff880`011a5000 fffff880`011f1000   fltmgr   fltmgr.sys   Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`01531000 fffff880`0153b000   Fs_Rec   Fs_Rec.sys   Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`015c1000 fffff880`015fb000   fvevol   fvevol.sys   Mon Jun 01 21:52:12 2009 (4A2485CC)
fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Mon Jun 01 21:51:17 2009 (4A248595)
fffff880`04599000 fffff880`045a4000   GEARAspiWDM GEARAspiWDM.sys Thu Mar 19 11:34:13 2009 (49C265F5)
fffff880`05e1a000 fffff880`05f9b000   ha20x2k  ha20x2k.sys  Thu Apr 09 05:45:37 2009 (49DDC3C1)
fffff800`02a13000 fffff800`02a5c000   hal      hal.dll      Mon Jun 01 23:50:01 2009 (4A24A169)
fffff880`04f87000 fffff880`04fab000   HDAudBus HDAudBus.sys Mon Jun 01 22:37:12 2009 (4A249058)
fffff880`0660e000 fffff880`06627000   HIDCLASS HIDCLASS.SYS Mon Jun 01 22:37:16 2009 (4A24905C)
fffff880`06627000 fffff880`0662f080   HIDPARSE HIDPARSE.SYS Mon Jun 01 22:37:15 2009 (4A24905B)
fffff880`06600000 fffff880`0660e000   hidusb   hidusb.sys   Mon Jun 01 22:37:17 2009 (4A24905D)
fffff880`03c5f000 fffff880`03d27000   HTTP     HTTP.sys     Mon Jun 01 21:52:01 2009 (4A2485C1)
fffff880`0168d000 fffff880`01696000   hwpolicy hwpolicy.sys Mon Jun 01 21:49:28 2009 (4A248528)
fffff880`01049000 fffff880`01167000   iaStorV  iaStorV.sys  Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`042f5000 fffff880`0430b000   intelppm intelppm.sys Mon Jun 01 21:50:10 2009 (4A248552)
fffff880`043e5000 fffff880`043f4000   kbdclass kbdclass.sys Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`06632000 fffff880`06640000   kbdhid   kbdhid.sys   Mon Jun 01 22:31:03 2009 (4A248EE7)
fffff800`00ba1000 fffff800`00bab000   kdcom    kdcom.dll    Mon Jun 01 23:53:16 2009 (4A24A22C)
fffff880`0450f000 fffff880`04552000   ks       ks.sys       Mon Jun 01 22:31:10 2009 (4A248EEE)
fffff880`01493000 fffff880`014ad000   ksecdd   ksecdd.sys   Mon Jun 01 21:51:06 2009 (4A24858A)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Mon Jun 01 22:21:02 2009 (4A248C8E)
fffff880`0458b000 fffff880`04590200   ksthunk  ksthunk.sys  Mon Jun 01 22:31:00 2009 (4A248EE4)
fffff880`0665d000 fffff880`06670000   LHidFilt LHidFilt.Sys Fri Dec 19 02:38:04 2008 (494B4F5C)
fffff880`0603c000 fffff880`06051000   lltdio   lltdio.sys   Mon Jun 01 22:39:46 2009 (4A2490F2)
fffff880`061a3000 fffff880`061b7000   LMouFilt LMouFilt.Sys Fri Dec 19 02:38:09 2008 (494B4F61)
fffff880`061c5000 fffff880`061e8000   luafv    luafv.sys    Mon Jun 01 21:56:03 2009 (4A2486B3)
fffff880`00c43000 fffff880`00c87000   mcupdate mcupdate.dll Mon Jun 01 23:51:07 2009 (4A24A1AB)
fffff880`061b7000 fffff880`061c5000   monitor  monitor.sys  Mon Jun 01 22:09:46 2009 (4A2489EA)
fffff880`04200000 fffff880`0420f000   mouclass mouclass.sys Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`06196000 fffff880`061a3000   mouhid   mouhid.sys   Mon Jun 01 22:31:03 2009 (4A248EE7)
fffff880`00db9000 fffff880`00dd3000   mountmgr mountmgr.sys Mon Jun 01 21:50:17 2009 (4A248559)
fffff880`061e8000 fffff880`06200000   mpsdrv   mpsdrv.sys   Mon Jun 01 22:39:19 2009 (4A2490D7)
fffff880`0535b000 fffff880`05387000   mrxsmb   mrxsmb.sys   Mon Jun 01 21:54:11 2009 (4A248643)
fffff880`05387000 fffff880`053d4000   mrxsmb10 mrxsmb10.sys Mon Jun 01 21:54:18 2009 (4A24864A)
fffff880`053d4000 fffff880`053f7000   mrxsmb20 mrxsmb20.sys Mon Jun 01 21:54:11 2009 (4A248643)
fffff880`02c1b000 fffff880`02c26000   Msfs     Msfs.SYS     Mon Jun 01 21:50:20 2009 (4A24855C)
fffff880`00f72000 fffff880`00f7c000   msisadrv msisadrv.sys Mon Jun 01 21:49:48 2009 (4A24853C)
fffff880`01435000 fffff880`01493000   msrpc    msrpc.sys    Mon Jun 01 21:51:39 2009 (4A2485AB)
fffff880`0405d000 fffff880`04068000   mssmbios mssmbios.sys Mon Jun 01 22:02:07 2009 (4A24881F)
fffff880`017ea000 fffff880`017fc000   mup      mup.sys      Mon Jun 01 21:53:54 2009 (4A248632)
fffff880`01698000 fffff880`0178a000   ndis     ndis.sys     Mon Jun 01 21:52:00 2009 (4A2485C0)
fffff880`04fc9000 fffff880`04fd5000   ndistapi ndistapi.sys Mon Jun 01 22:41:02 2009 (4A24913E)
fffff880`04800000 fffff880`0482f000   ndiswan  ndiswan.sys  Mon Jun 01 22:41:13 2009 (4A249149)
fffff880`052ee000 fffff880`05303000   NDProxy  NDProxy.SYS  Mon Jun 01 22:41:05 2009 (4A249141)
fffff880`04179000 fffff880`04188000   netbios  netbios.sys  Mon Jun 01 22:40:25 2009 (4A249119)
fffff880`04105000 fffff880`0414a000   netbt    netbt.sys    Mon Jun 01 21:51:26 2009 (4A24859E)
fffff880`0178a000 fffff880`017ea000   NETIO    NETIO.SYS    Mon Jun 01 21:52:17 2009 (4A2485D1)
fffff880`02c26000 fffff880`02c37000   Npfs     Npfs.SYS     Mon Jun 01 21:50:21 2009 (4A24855D)
fffff880`04051000 fffff880`0405d000   nsiproxy nsiproxy.sys Mon Jun 01 21:51:17 2009 (4A248595)
fffff800`02a5c000 fffff800`0303a000   nt       ntoskrnl.exe Mon Jun 01 22:01:18 2009 (4A2487EE)
fffff880`01244000 fffff880`013e7000   Ntfs     Ntfs.sys     Mon Jun 01 21:51:21 2009 (4A248599)
fffff880`02da5000 fffff880`02dae000   Null     Null.SYS     Mon Jun 01 21:50:09 2009 (4A248551)
fffff880`04153000 fffff880`04179000   pacer    pacer.sys    Mon Jun 01 22:40:39 2009 (4A249127)
fffff880`00fbc000 fffff880`00fd1000   partmgr  partmgr.sys  Mon Jun 01 21:50:24 2009 (4A248560)
fffff880`00f7c000 fffff880`00faf000   pci      pci.sys      Mon Jun 01 21:50:09 2009 (4A248551)
fffff880`00fe6000 fffff880`00fed000   pciide   pciide.sys   Mon Jun 01 21:50:12 2009 (4A248554)
fffff880`00fed000 fffff880`00ffd000   PCIIDEX  PCIIDEX.SYS  Mon Jun 01 21:50:11 2009 (4A248553)
fffff880`01520000 fffff880`01531000   pcw      pcw.sys      Mon Jun 01 21:49:33 2009 (4A24852D)
fffff880`03d27000 fffff880`03dcd000   peauth   peauth.sys   Mon Jun 01 23:32:21 2009 (4A249D45)
fffff880`044b0000 fffff880`044ed000   portcls  portcls.sys  Mon Jun 01 22:37:24 2009 (4A249064)
fffff880`00c87000 fffff880`00c9b000   PSHED    PSHED.dll    Mon Jun 01 23:54:44 2009 (4A24A284)
fffff880`045d3000 fffff880`045f7000   rasl2tp  rasl2tp.sys  Mon Jun 01 22:41:13 2009 (4A249149)
fffff880`04fd5000 fffff880`04ff0000   raspppoe raspppoe.sys Mon Jun 01 22:41:19 2009 (4A24914F)
fffff880`043c4000 fffff880`043e5000   raspptp  raspptp.sys  Mon Jun 01 22:41:18 2009 (4A24914E)
fffff880`0482f000 fffff880`04849000   rassstp  rassstp.sys  Mon Jun 01 22:41:24 2009 (4A249154)
fffff880`04000000 fffff880`04051000   rdbss    rdbss.sys    Mon Jun 01 21:54:20 2009 (4A24864C)
fffff880`04ff0000 fffff880`04ffb000   rdpbus   rdpbus.sys   Mon Jun 01 22:48:31 2009 (4A2492FF)
fffff880`02c00000 fffff880`02c09000   RDPCDD   RDPCDD.sys   Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02c09000 fffff880`02c12000   rdpencdd rdpencdd.sys Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`02c12000 fffff880`02c1b000   rdprefmp rdprefmp.sys Mon Jun 01 22:47:16 2009 (4A2492B4)
fffff880`01587000 fffff880`015c1000   rdyboost rdyboost.sys Mon Jun 01 22:05:46 2009 (4A2488FA)
fffff880`06051000 fffff880`06069000   rspndr   rspndr.sys   Mon Jun 01 22:39:47 2009 (4A2490F3)
fffff880`00c00000 fffff880`00c2f000   SCSIPORT SCSIPORT.SYS Mon Jun 01 22:32:00 2009 (4A248F20)
fffff880`03dcd000 fffff880`03dd8000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`01685000 fffff880`0168d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0808f000 fffff880`08127000   srv      srv.sys      Mon Jun 01 21:55:19 2009 (4A248687)
fffff880`05200000 fffff880`05269000   srv2     srv2.sys     Mon Jun 01 21:55:03 2009 (4A248677)
fffff880`03c00000 fffff880`03c2d000   srvnet   srvnet.sys   Mon Jun 01 21:55:00 2009 (4A248674)
fffff880`045f7000 fffff880`045f8480   swenum   swenum.sys   Mon Jun 01 22:31:01 2009 (4A248EE5)
fffff880`01800000 fffff880`019fe000   tcpip    tcpip.sys    Mon Jun 01 21:55:19 2009 (4A248687)
fffff880`03dd8000 fffff880`03dea000   tcpipreg tcpipreg.sys Mon Jun 01 22:40:46 2009 (4A24912E)
fffff880`02c37000 fffff880`02c44000   TDI      TDI.SYS      Mon Jun 01 21:51:25 2009 (4A24859D)
fffff880`01014000 fffff880`01032000   tdx      tdx.sys      Mon Jun 01 21:51:23 2009 (4A24859B)
fffff880`041e1000 fffff880`041f5000   termdd   termdd.sys   Mon Jun 01 22:47:14 2009 (4A2492B2)
fffff880`041a3000 fffff880`041e1000   truecrypt truecrypt.sys Sun May 10 14:48:02 2009 (4A072162)
fffff960`00590000 fffff960`0059a000   TSDDD    TSDDD.dll    Mon Jun 01 22:47:14 2009 (4A2492B2)
fffff880`042cf000 fffff880`042f5000   tunnel   tunnel.sys   Mon Jun 01 22:40:35 2009 (4A249123)
fffff880`013e7000 fffff880`013f9000   umbus    umbus.sys    Mon Jun 01 22:37:45 2009 (4A249079)
fffff880`08198000 fffff880`081a8000   usbaapl64 usbaapl64.sys Wed Apr 15 14:58:13 2009 (49E62E45)
fffff880`06640000 fffff880`0665d000   usbccgp  usbccgp.sys  Mon Jun 01 22:37:33 2009 (4A24906D)
fffff880`06630000 fffff880`06631f00   USBD     USBD.SYS     Mon Jun 01 22:37:19 2009 (4A24905F)
fffff880`04fb8000 fffff880`04fc9000   usbehci  usbehci.sys  Mon Jun 01 22:37:25 2009 (4A249065)
fffff880`05294000 fffff880`052ee000   usbhub   usbhub.sys   Mon Jun 01 22:37:51 2009 (4A24907F)
fffff880`0430b000 fffff880`04361000   USBPORT  USBPORT.SYS  Mon Jun 01 22:37:25 2009 (4A249065)
fffff880`04fab000 fffff880`04fb8000   usbuhci  usbuhci.sys  Mon Jun 01 22:37:21 2009 (4A249061)
fffff880`01230000 fffff880`0123f000   VClone   VClone.sys   Fri May 22 19:08:37 2009 (4A173075)
fffff880`00faf000 fffff880`00fbc000   vdrvroot vdrvroot.sys Mon Jun 01 22:32:17 2009 (4A248F31)
fffff880`02db5000 fffff880`02dc3000   vga      vga.sys      Mon Jun 01 22:09:45 2009 (4A2489E9)
fffff880`02dc3000 fffff880`02de8000   VIDEOPRT VIDEOPRT.SYS Mon Jun 01 22:09:49 2009 (4A2489ED)
fffff880`01675000 fffff880`01685000   vmstorfl vmstorfl.sys Mon Jun 01 22:13:37 2009 (4A248AD1)
fffff880`00fd1000 fffff880`00fe6000   volmgr   volmgr.sys   Mon Jun 01 21:50:19 2009 (4A24855B)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Mon Jun 01 21:50:45 2009 (4A248575)
fffff880`0153b000 fffff880`01587000   volsnap  volsnap.sys  Mon Jun 01 21:50:29 2009 (4A248565)
fffff880`04188000 fffff880`041a3000   wanarp   wanarp.sys   Mon Jun 01 22:41:24 2009 (4A249154)
fffff880`02de8000 fffff880`02df8000   watchdog watchdog.sys Mon Jun 01 22:08:37 2009 (4A2489A5)
fffff880`00e5f000 fffff880`00f03000   Wdf01000 Wdf01000.sys Mon Jun 01 21:53:29 2009 (4A248619)
fffff880`00f03000 fffff880`00f12000   WDFLDR   WDFLDR.SYS   Mon Jun 01 21:50:16 2009 (4A248558)
fffff880`0414a000 fffff880`04153000   wfplwf   wfplwf.sys   Mon Jun 01 22:40:25 2009 (4A249119)
fffff960`000a0000 fffff960`003af000   win32k   win32k.sys   Mon Jun 01 22:11:46 2009 (4A248A62)
fffff880`081b3000 fffff880`081c4000   WinUsb   WinUsb.sys   Mon Jun 01 22:37:22 2009 (4A249062)
fffff880`045a4000 fffff880`045ad000   wmiacpi  wmiacpi.sys  Mon Jun 01 22:02:00 2009 (4A248818)
fffff880`00f69000 fffff880`00f72000   WMILIB   WMILIB.SYS   Mon Jun 01 21:50:14 2009 (4A248556)
fffff880`0601b000 fffff880`0603c000   WudfPf   WudfPf.sys   Mon Jun 01 22:36:40 2009 (4A249038)
fffff880`081c4000 fffff880`081f5000   WUDFRd   WUDFRd.sys   Mon Jun 01 22:37:05 2009 (4A249051)
fffff880`04361000 fffff880`043c4000   yk62x64  yk62x64.sys  Mon Feb 23 10:02:27 2009 (49A2BA83)

Unloaded modules:
fffff880`08051000 fffff880`0806c000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`08036000 fffff880`08051000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0801b000 fffff880`08036000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`08000000 fffff880`0801b000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`06146000 fffff880`06161000   CTHWIUT.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`08127000 fffff880`08198000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01416000 fffff880`01424000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02c4a000 fffff880`02d68000   dump_iaStorV
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02d68000 fffff880`02d7b000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`072ec028 00000000`fe000000 00000000`0040014a
Closing open log file C:\Users\FUBAR-RC1-Desktop\TempDUMP\DATA\$99-dbug.txt

.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
.

usasma · Jun 20, 2009

Righto thx, il try the volts and such first... btw i take it the sys file is a driver? If so can i update it through device manager? or can i google the sys file and replace my old one... windows update is useless anyway. I'm posting up photos of most of my bios settings aswell for clarity. later

Yes, the .sys file is a driver. I don't recommend using Windows Update to update drivers - as they're just the drivers that were supplied to them from different manufacturers. But the drivers must be "certified" by Microsoft before posting - so it may be a while until they're listed - if at all.

Most likely the ASACPI.SYS file is a part of the drivers for your motherboard (most likely an Asus motherboard). If it's a part of installed Asus utilities, uninstall the Asus utilities in Windows 7 (they don't work well there).

ACPI functions are lower level functions (they work lower in the OS than most other stuff). As such, they have a higher likelyhood of being incompatible with Win7. I recall one other post where I dealt with this same file in Win7 - but don't recall if it was ever resolved. I had issues with Asus utilities in the beta of Win7 - so I didn't install them in the RC and haven't had any problems since.

But, having had a brainstorm just now (and I lost what I was typing) - I searched my system (I have a P6T mobo) and found the same driver dated 3/29/05 on my Win7 RC!!!

That's only 2 days after yours - so I wonder if this even has any bearing on your issues?

coldshiver · Jun 20, 2009

Lol so uhh you gonna update it? If thats possible and how ? Seems i never installed asus utility either haha, driver must come with win7 RC?

usasma · Jun 20, 2009

Update it? Why? I'm not having any issues with my system (so, why should you?).
Seriously, I haven't installed anything from Asus - any drivers that I did install came from the hardware manufacturer's website and not from Asus (thanks to my difficulties with it in the beta).

So, this either came off of the Win7 DVD, or it was a Windows Update...
Having just had another brainstorm (this is beginning to hurt!

), I checked my Windows Updates... On 02 May 2009 I got the driver in an update. Unfortunately, the Drive ID link won't work in Firefox, and in IE8 it gives a "sorry, but we're not ready to list drivers ID's yet" message.

AAARRRRGGGGHHHHH!!!!!!

coldshiver · Jun 20, 2009

haha well good point, i'l leave it be then... now for the voltages, could someone help me set those and what values/how to find out?, and/or any pointers to get ATT working? (i'm trying now to set the Traytools.ini (or somethings like that) to ignore Overdrive and use alternate driver level clocking) rebooting...

Snufffed · Jun 20, 2009

After consolting with several MS MVP on Win7 BSOD 0x124 errors. they all concluded.

Most STOP 0x124 errors are hardware related. They are errors that are reported to Windows by the processor (in most cases) and use the Windows Hardware Error Architecture (WHEA) reporting format. As such, the information is a bit limited.

In this case the first parameter of the error message is a 4 - and this means "An uncorrectable PCI Express error occurred." (from the Windows Debugging Tools Help files).

I would suspect that either the motherboard is bad, or that Windows hasn't picked the proper drivers for the motherboard and it's confusing the processor (where the error message is generated). It can also be other drivers causing this - but since it's a processor error, the likelyhood is less IMO

coldshiver · Jun 20, 2009

PCI Express error, coudn't that mean my ATI card is broke then?, i'm gonna try and get the latest drivers for my Mobo anyway, and i'l still try and stop ati from switching clock speeds on-the fly, if i can get rivaturner to work or ATT. You recommend flashing my mobo bios? or ATI then? or not yet?

Edit: Crap it seems they only have Win7 driver for P6T Deluxe v2 not the v1 ive got (only difference between them was it having less sata but more SAS connection ports or something, something minor as i recall it anyway) i wonder if i can still install the v2 ones.. don't think thats wise though

usasma · Jun 20, 2009

A PCI Express error is when the STOP 0x124 error has it's first parameter as a 4.
Here's the code from the BSOD:

BugCheck 124, {0, fffffa80072fe028, fe200040, 60114a}

There is considerable disagreement in these sort of communities over the exact interpretation of these errors. Some will insist that they are hardware and nothing but hardware. Others will allow that they can also be caused by compatibility issues and/or firmware issues, while still others will say that they can be caused by drivers also (I'm of this belief).

Regardless of the cause, these are errors that cause a crash in the processor (CPU) rather than in Windows. There's lot's of documentation available describing them, but the details are very technical. I've had a shot at trying to interpret them and have gotten nowhere.

Here's a listing of the first parameters and their cause:

Code:

0x0 - A machine check exception occurred.
0x1 - A corrected machine check exception occurred.
0x2 - A corrected platform error occurred.
0x3 - A nonmaskable Interrupt (NMI) error occurred.
0x4 - An uncorrectable PCI Express error occurred.
0x5 - A generic hardware error occurred.
0x6 - An IA64 INIT error occurred.
0x7 - A BOOT error occurred.
0x8 - A Scalable Coherent Interface (SCI) generic error occurred.
0x9 - An uncorrectable IA-64 machine check abort error occurred.
0xA - A corrected IA-64 machine check error occurred.
0xB - A corrected IA-64 platform error occurred.

Of these I've only encountered the 0x0 and the 0x4. There hasn't been much resolution for them - but having seen the number of "wipe and reinstalls" that are done for them (and not hearing anything back) I have to presume that it's something like a driver doing it (because the other problems aren't fixed by a "wipe and reinstall".

But, with the number of other BSOD's that are generated by Windows, I'd have to suspect something extremely "whacky" is happening in order to crash the processor and not Windows.

There have been attempts at BIOS updates, and firmware updates that may have met with success. But once again there's no firm evidence that they have fixed the issues.

In short, there's no "magic bullet" for these errors. IMO the best thing to do is to fix everything that may be involved with the sub-systems that are affected by the error. That includes BIOS updates, firmware updates, driver updates, and compatibility checks with the Windows HAL database, and even hardware replacements.

coldshiver · Jun 20, 2009

Ok next step is flashing my mobo & graphics card then. After i get these voltages set manually right? Could you tell me what to set?

CPU-z gives this info.

And could you also take a quick look through my bios settings if its ok?, because i have no idea what half of the features mean. It also shows the volt settings.
BiosSettings1
BiosSettings2
BiosSettings3
BiosSettings4

PS: Ive downloaded a rom file from asus its a vista 64 bios update for my mobo, since thers no win7 anyway its the latest thats not in beta, do i go in the bios and start that ez flash ? and then choose NTFS as source and find the rom file?

smarteyeball · Jun 20, 2009

From the CPU-Z shots, it looks as if there are enough volts already. 1.264V would equate to around 1.2700 in the BIOS.

However, for elimination purposes, you could safely set that to between 1.28 - 1.30V. (key in numerically and then use the +/- keys to go up or down)

This will be more than sufficient to run at stock speeds. If the 0x124 still occurs, then you will have ruled out one potential cause. (You can lower the voltages afterwards back to the 1.26-1.27 range)

As usasma has pointed out, 0x124 errors are an absolute PITA to troubleshoot.

There is a Win 7 x64 BIOS version available. I didn't see anything about beta versions. Chances are it's just the Vista one anyway.

P6T Deluxe V2 0504 BIOS
ASUSTeK Computer Inc.-Support-

When I update my BIOS I actually use FAT32 on my flash drive instead of NTFS, although it appears EZ-Flash supports it. EZ-Flash is quite easy to use. Just run it, find the .rom and off you go.

At this stage, the only BIOS setting you should need to touch would be the CPU Voltage and possibly the QPI/DRAM core voltage (to manually set your ram's voltage)

BSOD 0x00000124 Need Assistance

ColdShiver

My Computer

Account closed by request

My Computer

Dark Lord of the Sith

My Computer

New member

My Computer

New member

My Computer

ColdShiver

My Computer

knows his stuff

My Computer

ColdShiver

My Computer

New member

My Computer

knows his stuff

My Computer

Mr. Cranky Pants

My Computer

Mr. Cranky Pants

My Computer

ColdShiver

My Computer

Mr. Cranky Pants

My Computer

ColdShiver

My Computer

Expelled

ColdShiver

My Computer

Mr. Cranky Pants

My Computer

ColdShiver

My Computer

knows his stuff

My Computer