frequent random BSODs

[thargas]

Hi folks.

I've got a 6-month old OEM, original install of Win7 X64. Until a couple of weeks ago it was stable: no BSODs. Then there was one. Now I'm lucky if I can get through a session without one. They seem to be of random types, according to windbg, though there have been a number of ones pointing at amdppm.sys. They seem to be more frequent if the machine is busier.

I don't recall installing anything in particular around the time that it started.

I've tried uninstalling a bunch of unused programs, and my old scanner. I've uninstalled the anti-virus program I was using (avast free) and installing Microsoft Security Essentials instead. I've tried runing Malwarebytes Anti-Malware, with a clean report (when I don't get a random BSOD).

I'm getting to the point of considering re-installing Win7, but ideally I'd like to figure out what causes this so I can avoid it in future.

 

[usasma]

No memory dumps in this upload, please do the following:

Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service . I recommend Windows Live SkyDrive - http://skydrive.live.com or another free, file-hosting service. Then post the link to it in your topic so that we can download it.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

The BSOD's noted in the MSINFO32 file aren't very helpful. I'd suggest trying Driver Verifier according to these instructions:

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

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

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[thargas]

minidumps

here are the minidumps.

 

[zigzag3143]

here are the minidumps.

The majority of these were caused by amdpp.sys, and the attempt to write to read only memory.

You also have some drivers that are old and need to be updated.

I would
1- update amdppm.sys which is a processor driver. It may be integral to BIOS, I am no sure.

2-update the old drivers

3- run a system file check. Type cmd in search>right click and run as admin>
sfc /scannow

Ken




Old drivers needing updating

SSPORT.sys        fffff880`06170000    fffff880`06178000    0x00008000    0x42fbda34    8/11/2005 19:07:32                        
secdrv.SYS        fffff880`06138000    fffff880`06143000    0x0000b000    0x4508052e    9/13/2006 09:18:38                        
AsIO.sys        fffff880`02bc4000    fffff880`02bcb000    0x00007000    0x47663d55    12/17/2007 05:11:49                        
DgiVecp.sys        fffff880`05223000    fffff880`05233000    0x00010000    0x490a7db5    10/30/2008 23:38:29                        
NuidFltr.sys        fffff880`03e83000    fffff880`03e8c000    0x00009000    0x4a03f30b    5/8/2009 04:53:31                        
spldr.sys        fffff880`014e5000    fffff880`014ed000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
amdxata.sys        fffff880`00d91000    fffff880`00d9c000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59

Analysis

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


Loading Dump File [C:\Users\K\Desktop\072310-19250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca1e50
Debug session time: Fri Jul 23 17:25:32.275 2010 (GMT-4)
System Uptime: 0 days 1:49:05.836
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff880016fa354, 3ce1121, fffff88002d1b8b0, a}

Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff880016fa354, Virtual address for the attempted write.
Arg2: 0000000003ce1121, PTE contents.
Arg3: fffff88002d1b8b0, (reserved)
Arg4: 000000000000000a, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xBE

PROCESS_NAME:  System

CURRENT_IRQL:  d

TRAP_FRAME:  fffff88002d1b8b0 -- (.trap 0xfffff88002d1b8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000001f287 rbx=0000000000000000 rcx=000000000001f287
rdx=000000000002633a rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002adb258 rsp=fffff88002d1ba40 rbp=0000000000000001
 r8=000000000000761a  r9=0000000000000000 r10=0000000000005892
r11=fffff88007b0bc70 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeAccumulateTicks+0xf8:
fffff800`02adb258 898bd4210000    mov     dword ptr [rbx+21D4h],ecx ds:00000000`000021d4=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b53388 to fffff80002ad4600

STACK_TEXT:  
fffff880`02d1b748 fffff800`02b53388 : 00000000`000000be fffff880`016fa354 00000000`03ce1121 fffff880`02d1b8b0 : nt!KeBugCheckEx
fffff880`02d1b750 fffff800`02ad26ee : fffff880`02d1b938 fffff880`009e8180 00000000`00000010 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x409f4
fffff880`02d1b8b0 fffff800`02adb258 : fffff8a0`09629000 fffff8a0`07fc8000 fffff8a0`002cd000 fffff8a0`0f3c0000 : nt!KiPageFault+0x16e
fffff880`02d1ba40 fffff800`02ae1518 : fffff8a0`001df000 fffff880`04705cf0 00000000`00026160 fffffa80`05593d00 : nt!KeAccumulateTicks+0xf8
fffff880`02d1bad0 fffff800`02ae12a1 : 00000000`00000000 fffff880`02d1bb80 fffff880`009e8180 00000000`00000001 : nt!KeUpdateRunTime+0xb8
fffff880`02d1bb00 fffff880`02a037f2 : fffff800`02ae213a 00000000`0026da19 fffffa80`05593dd8 fffff880`009f2fc0 : nt!KiSecondaryClockInterrupt+0x131
fffff880`02d1bc98 fffff800`02ae213a : 00000000`0026da19 fffffa80`05593dd8 fffff880`009f2fc0 00000000`00000001 : amdppm!C1Halt+0x2
fffff880`02d1bca0 fffff800`02adcdcc : fffff880`009e8180 fffff880`00000000 00000000`00000000 fffff800`02bf4ce0 : nt!PoIdle+0x53a
fffff880`02d1bd80 00000000`00000000 : fffff880`02d1c000 fffff880`02d16000 fffff880`02d1bd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
amdppm!C1Halt+2
fffff880`02a037f2 c3              ret

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  amdppm!C1Halt+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: amdppm

IMAGE_NAME:  amdppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0xBE_VRF_amdppm!C1Halt+2

BUCKET_ID:  X64_0xBE_VRF_amdppm!C1Halt+2

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

 

[thargas]

better but not fixed

I've been able to work for an hour or two before getting a BSOD.

I've updated the asus chipset sw. Unfortunately, this seems not to have any effect on amdppm.sys.

I'm working my way through the old drivers you mentioned:
- replaced the samsung printer driver (ssport.sys) and now I have a non-functional printer
- disabled (renamed) secdrv.sys as it doesn't sound like anything I want/need
- found references connecting asio.sys with pc probe, which didn't sound interesting so I uninstalled it.

I've run "sfc /scannow" and it says the system is clean.

 

[usasma]

Posted before I read your post:
Update the chipset drivers for your motherboard from the Asus support website.
Uninstall the Asus PCProbe software from your system (the AsIO.sys driver).
Uninstall Microsoft Intellitype/IntelliPoint software (the NuidFltr.sys driver)
Uninstall Samsung Drivers (SSPORT.sys and DgiVecp.sys)

Posted after I read your post:
Did the Samsung driver update also update the DgiVecp.sys file?
Do not rename the secdrv.sys - it is a Windows file and doesn't need updating

 

[thargas]

DgiVecp.sys

yes, DgiVecp.sys was updated to 2009-03-02

 

[thargas]

windows DVD creator

One thing I've noticed is that I can "reliably" get a BSOD by attempting to create a DVD, and it will always happen before it starts to write to the DVD.

Thanks for all the detailed instructions. They really do help when one isn't a win7 guru.

 

[usasma]

Generate a BSOD by trying to create a DVD and then upload the memory dump file - we'll have a shot at figuring it out.

 

[thargas]

I've got a dump...

but it's 66MB, so it won't fit in skydrive.

Here's the output of windbg:


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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\Websymbols*Symbol information
Executable search path is: SRV*C:\Websymbols*Symbol information
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c4be50
Debug session time: Sat Jul 24 19:04:35.269 2010 (UTC - 3:00)
System Uptime: 0 days 0:03:29.220
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {3, 2, 1, fffff80002a8a0e2}

Probably caused by : ntkrnlmp.exe ( nt!KiReadyThread+2 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a8a0e2, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'hidusb' and 'crashdmp.sys' overlap

WRITE_ADDRESS: 0000000000000003

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiReadyThread+2
fffff800`02a8a0e2 4883ec20 sub rsp,20h

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff88002ffd440 -- (.trap 0xfffff88002ffd440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa80066ca060
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a8a0e2 rsp=fffff88002ffd5d0 rbp=fffffa80066ca168
r8=fffff88002fd7301 r9=0000000000000002 r10=0000000000000063
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiReadyThread+0x2:
fffff800`02a8a0e2 4883ec20 sub rsp,20h
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a7db69 to fffff80002a7e600

STACK_TEXT:
fffff880`02ffd2f8 fffff800`02a7db69 : 00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02ffd300 fffff800`02a7c7e0 : fffffa80`05c37418 fffffa80`066ca168 fffff980`01366ce0 fffff980`0e266c10 : nt!KiBugCheckDispatch+0x69
fffff880`02ffd440 fffff800`02a8a0e2 : fffffa80`066ca168 fffff800`02a89ab7 fffffa80`066ca120 fffffa80`066ee230 : nt!KiPageFault+0x260
fffff880`02ffd5d0 fffff800`02a89ab7 : fffffa80`066ca120 fffffa80`066ee230 fffffa80`066ee230 00000000`00000102 : nt!KiReadyThread+0x2
fffff880`02ffd5e0 fffff800`02a8a57e : 00000000`7cb479e8 fffff880`02ffdc58 00000000`00003463 fffff880`02fd81e8 : nt!KiProcessExpiredTimerList+0x157
fffff880`02ffdc30 fffff800`02a89d97 : 00000000`1fcfb1c1 00000000`00003463 00000000`1fcfb133 00000000`00000063 : nt!KiTimerExpiration+0x1be
fffff880`02ffdcd0 fffff800`02a86dfa : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`04e5f588 : nt!KiRetireDpcList+0x277
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiReadyThread+2
fffff800`02a8a0e2 4883ec20 sub rsp,20h

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiReadyThread+2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0xA_VRF_nt!KiReadyThread+2

BUCKET_ID: X64_0xA_VRF_nt!KiReadyThread+2

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

 

[usasma]

Please post the output of this command in the debugger:

lmtsmn

Zip up the dump file (to less than 50 mb) and load it to SkyDrive
Zip up the dump file and upload it to another, free online file hosting site
Use the .dump /m command to generate a minidump and upload that
Set the system to create minidumps ( Set MiniDump ) and then make another crash by using the DVD creator - then upload that minidump

Once you've got it making minidumps, then please run Driver Verifier according to these directions:

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

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

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[thargas]

here's the dump

MEMORY.zip

 

[Jonathan_King]

I notice your serial port drivers are out of date. Please install the latest version from the computer manufacturer's site.

The other thing I notice is your outdated AsIO.sys file. Please install the latest PC Probe utility from here: ASUSTeK Computer Inc.-Support-

Enable driver verifier when you're done: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

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


Loading Dump File [C:\Users\Jonathan\_jcgriff2_\dbug\__Kernel__\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c4be50
Debug session time: Sat Jul 24 18:04:35.269 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:29.220
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {3, 2, 1, fffff80002a8a0e2}

Probably caused by : ntkrnlmp.exe ( nt!KiReadyThread+2 )

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

3: kd> !analyze -v;lmtsmn;.bugcheck;.logclose;q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a8a0e2, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'hidusb' and 'crashdmp.sys' overlap

WRITE_ADDRESS:  0000000000000003 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiReadyThread+2
fffff800`02a8a0e2 4883ec20        sub     rsp,20h

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffd440 -- (.trap 0xfffff88002ffd440)
.trap 0xfffff88002ffd440
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa80066ca060
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a8a0e2 rsp=fffff88002ffd5d0 rbp=fffffa80066ca168
 r8=fffff88002fd7301  r9=0000000000000002 r10=0000000000000063
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiReadyThread+0x2:
fffff800`02a8a0e2 4883ec20        sub     rsp,20h
.trap
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7db69 to fffff80002a7e600

STACK_TEXT:  
fffff880`02ffd2f8 fffff800`02a7db69 : 00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02ffd300 fffff800`02a7c7e0 : fffffa80`05c37418 fffffa80`066ca168 fffff980`01366ce0 fffff980`0e266c10 : nt!KiBugCheckDispatch+0x69
fffff880`02ffd440 fffff800`02a8a0e2 : fffffa80`066ca168 fffff800`02a89ab7 fffffa80`066ca120 fffffa80`066ee230 : nt!KiPageFault+0x260
fffff880`02ffd5d0 fffff800`02a89ab7 : fffffa80`066ca120 fffffa80`066ee230 fffffa80`066ee230 00000000`00000102 : nt!KiReadyThread+0x2
fffff880`02ffd5e0 fffff800`02a8a57e : 00000000`7cb479e8 fffff880`02ffdc58 00000000`00003463 fffff880`02fd81e8 : nt!KiProcessExpiredTimerList+0x157
fffff880`02ffdc30 fffff800`02a89d97 : 00000000`1fcfb1c1 00000000`00003463 00000000`1fcfb133 00000000`00000063 : nt!KiTimerExpiration+0x1be
fffff880`02ffdcd0 fffff800`02a86dfa : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`04e5f588 : nt!KiRetireDpcList+0x277
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiReadyThread+2
fffff800`02a8a0e2 4883ec20        sub     rsp,20h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiReadyThread+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiReadyThread+2

BUCKET_ID:  X64_0xA_VRF_nt!KiReadyThread+2

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

start             end                 module name
fffff880`00e13000 fffff880`00e6a000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c50000 fffff880`02cda000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03fb9000 fffff880`03fcf000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`03fa4000 fffff880`03fb9000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00fa7000 fffff880`00fb2000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`04fed000 fffff880`04ff5000   ASACPI   ASACPI.sys   Wed Jul 15 23:31:29 2009 (4A5E9F11)
fffff880`03f77000 fffff880`03f7e000   AsIO     AsIO.sys     Mon Dec 17 04:11:49 2007 (47663D55)
fffff880`05e71000 fffff880`05e7c000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00f74000 fffff880`00f7d000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f7d000 fffff880`00fa7000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`04195000 fffff880`041b6000   AtiHdmi  AtiHdmi.sys  Fri Jul 24 02:33:11 2009 (4A6955A7)
fffff880`0483f000 fffff880`04e56000   atikmdag atikmdag.sys Mon Aug 17 23:05:47 2009 (4A8A1A8B)
fffff880`01861000 fffff880`01869000   AtiPcie  AtiPcie.sys  Tue May 05 11:00:22 2009 (4A005486)
fffff880`018ff000 fffff880`01906000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03f66000 fffff880`03f77000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`0392f000 fffff880`0394d000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00660000 fffff960`00687000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A)
fffff880`04090000 fffff880`040ad000   cdfs     cdfs.sys     Mon Jul 13 19:19:46 2009 (4A5BC112)
fffff880`0189f000 fffff880`018c9000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01831000 fffff880`01861000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00ce8000 fffff880`00d46000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0115e000 fffff880`011d1000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`03ea7000 fffff880`03eb7000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`040ad000 fffff880`040bb000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03ec5000 fffff880`03f48000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`041f3000 fffff880`041ff000   dc3d     dc3d.sys     Tue Nov 03 21:55:41 2009 (4AF0ED2D)
fffff880`03f48000 fffff880`03f66000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03823000 fffff880`03833000   DgiVecp  DgiVecp.sys  Thu Oct 30 23:38:29 2008 (490A7DB5)
fffff880`02c17000 fffff880`02c26000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01200000 fffff880`01216000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04000000 fffff880`04022000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`040c7000 fffff880`040d0000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`040bb000 fffff880`040c7000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0181a000 fffff880`0182d000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`04084000 fffff880`04090000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04e56000 fffff880`04f4a000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04f4a000 fffff880`04f90000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`010ec000 fffff880`01100000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00fb2000 fffff880`00ffe000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013e9000 fffff880`013f3000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01086000 fffff880`010c0000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0148b000 fffff880`014d5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02fea000 fffff800`03033000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04f90000 fffff880`04fb4000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`04028000 fffff880`04084000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`01880000 fffff880`01899000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`01869000 fffff880`01871080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`01872000 fffff880`01880000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`03867000 fffff880`0392f000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`015f7000 fffff880`01600000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`04800000 fffff880`0481e000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0481e000 fffff880`0482d000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bb5000 fffff800`00bbf000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`040d1000 fffff880`04114000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`013be000 fffff880`013d8000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`04022000 fffff880`04027200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`02521000 fffff880`02536000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`024dd000 fffff880`02500000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00cc7000 fffff880`00cd4000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`024b4000 fffff880`024c2000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`02c41000 fffff880`02c50000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`010dd000 fffff880`010ea000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00f5a000 fffff880`00f74000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`018c9000 fffff880`018f6000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`0394d000 fffff880`03965000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`03965000 fffff880`03992000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`03992000 fffff880`039e0000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`03800000 fffff880`03823000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`01964000 fffff880`0196f000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e73000 fffff880`00e7d000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01100000 fffff880`0115e000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02c0c000 fffff880`02c17000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015e5000 fffff880`015f7000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`014eb000 fffff880`015dd000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03ff3000 fffff880`03fff000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`019ab000 fffff880`019da000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04180000 fffff880`04195000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02d4e000 fffff880`02d5d000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02cda000 fffff880`02d1f000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`0196f000 fffff880`01980000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02c00000 fffff880`02c0c000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a0e000 fffff800`02fea000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`0121b000 fffff880`013be000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`013f3000 fffff880`013fc000   NuidFltr NuidFltr.sys Fri May 08 04:53:31 2009 (4A03F30B)
fffff880`018f6000 fffff880`018ff000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`011d1000 fffff880`011de000   nx6000   nx6000.sys   Wed Jan 27 18:36:09 2010 (4B60CDE9)
fffff880`02d28000 fffff880`02d4e000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`04fd0000 fffff880`04fed000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`00ebd000 fffff880`00ed2000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e7d000 fffff880`00eb0000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00f43000 fffff880`00f4a000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00f4a000 fffff880`00f5a000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013d8000 fffff880`013e9000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`0254e000 fffff880`025f4000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`041b6000 fffff880`041f3000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00cd4000 fffff880`00ce8000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`03fcf000 fffff880`03ff3000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`02c26000 fffff880`02c41000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`019da000 fffff880`019fb000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`01800000 fffff880`0181a000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02da9000 fffff880`02dfa000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`03eb7000 fffff880`03ec2000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`01949000 fffff880`01952000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01952000 fffff880`0195b000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0195b000 fffff880`01964000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0104c000 fffff880`01086000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`02536000 fffff880`0254e000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`03e00000 fffff880`03e51000   Rt64win7 Rt64win7.sys Tue Jan 12 01:37:27 2010 (4B4C18A7)
fffff880`0482d000 fffff880`04839000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02d5d000 fffff880`02d7a000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`015dd000 fffff880`015e5000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`05e00000 fffff880`05e71000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`05ed7000 fffff880`05f6f000   srv      srv.sys      Tue Dec 08 03:32:55 2009 (4B1E0F37)
fffff880`02400000 fffff880`02469000   srv2     srv2.sys     Mon Jul 13 19:25:02 2009 (4A5BC24E)
fffff880`03833000 fffff880`03860000   srvnet   srvnet.sys   Tue Dec 08 03:32:26 2009 (4B1E0F1A)
fffff880`039e0000 fffff880`039e8000   SSPORT   SSPORT.sys   Thu Aug 11 19:07:32 2005 (42FBDA34)
fffff880`04ffe000 fffff880`04fff480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`039e8000 fffff880`039fa000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`0199e000 fffff880`019ab000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`01980000 fffff880`0199e000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02d95000 fffff880`02da9000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`005c0000 fffff960`005ca000   TSDDD    TSDDD.dll    Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`03f7e000 fffff880`03fa4000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04114000 fffff880`04126000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`02499000 fffff880`024b3c00   usbaudio usbaudio.sys Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`010c0000 fffff880`010dd000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`04839000 fffff880`0483af00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04fbf000 fffff880`04fd0000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04126000 fffff880`04180000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04fb4000 fffff880`04fbf000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`03e51000 fffff880`03ea7000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`024c2000 fffff880`024dd000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`0246b000 fffff880`02498100   usbvideo usbvideo.sys Mon Jul 13 20:07:00 2009 (4A5BCC24)
fffff880`00eb0000 fffff880`00ebd000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01906000 fffff880`01914000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01914000 fffff880`01939000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`014d5000 fffff880`014e5000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00ed2000 fffff880`00ee7000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00ee7000 fffff880`00f43000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01000000 fffff880`0104c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02d7a000 fffff880`02d95000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`01939000 fffff880`01949000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00d46000 fffff880`00dea000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00dea000 fffff880`00df9000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02d1f000 fffff880`02d28000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000d0000 fffff960`003df000   win32k   win32k.sys   Sat May 01 11:06:30 2010 (4BDC4376)
fffff880`04ff5000 fffff880`04ffe000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00e6a000 fffff880`00e73000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`02500000 fffff880`02521000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`05f6f000 fffff880`05fa0000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`01869000 fffff880`01877000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`01877000 fffff880`01883000   dump_ataport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`01883000 fffff880`0188c000   dump_atapi.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`0188c000 fffff880`0189f000   dump_dumpfve.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000

 

[thargas]

minidujps from verifier

here they are

 

[thargas]

serial port driver

I tried to update the serial port driver in device-manager, but it says I have the best driver already.

I walked through all the devices shown in device-manager and told each of them to update their driver, but they all claim to be the best driver.

 

[thargas]

autoruns

I ran autoruns without much luck. I removed about 10 google updater entries, but the rest looked reasonable. I've attacked a save from it.

 

[thargas]

fanspeed

I've installed fanspeed. It says temps are fine: 40, 43 and core 31, C of course

I've left it running with logging.

 

[zigzag3143]

I tried to update the serial port driver in device-manager, but it says I have the best driver already.

I walked through all the devices shown in device-manager and told each of them to update their driver, but they all claim to be the best driver.

You cant use driver manager because it is using win 7 database which is nowhere near current. go to the mfr website and get it there

KEN

 

[Jonathan_King]

Are you doing any overclocking?

[font=lucida console]
BugCheck D1, {fffff8000238d28f, d, 8, fffff8000238d28f}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {fffff8804ef685f0, d, 1, fffff80002acd1c0}
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 124, {0, fffffa8005d978f8, 0, 0}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {955e81b9, d, 0, fffff80002acf254}
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[thargas]

no overclocking

not unless someone sneaked it in when I wasn't looking. Given that no-one else in the house is at all into computers, that would mean that the vendor would have had to do that.

Is it possible to tell without taking the box apart?