Bsod

Hey had a little look around and wasnt sure if there was somewhere specific to post errors couldnt find one and saw other BSOD errors in here. Sorry if Ive missed something!

Any help would be wonderful. The debug textfile is attached, thanks in advance!

 

Hi Coyle, could you upload a zipped copy of C:\Windows\Minidump\032611-42650-01.dmp please? It'll make it easier for me to checkout driver dates and maybe do more debugging on it.

 

Hey Satrow, I wasnt expecting such a fast reply hence my late reply. Ill attack the archive onto this post, thanks for wanting to have a look. Really appreciate it!


Hmm, using WinRAR it is claiming that the file is invalid. Ill upload elsewhere and link it.


http://www.megaupload.com/?d=9PS7GDT7

Thats it there, thanks again.

 

.zip and .rar are coming up as invalid and I presume my other post was deleted by a moderator for having an outside line in it.

 

Your missing post may be held in moderation for some reason, maybe it'll appear once it's checked and fixed

A zip file should be ok to post here, a single minidump will be way less than 1 Mb. Copy the dumpfile to your Desktop before zipping it or you may get an error from Windows.

How to attach items to your Post.

 

There we go, must have been in moderation for the old link I guess. Makes sense checking Im not linking who knows what.

In saying that .zip files are still showing up as "Invalid". Im just using winzip is there an issue with that or...

Thanks for the replies!

 

Back to plan B, I'm afraid; none of my 4 browsers can see the download link at Megaupload. So, zip and attach it here, please?

 

I think I'll need to check my hosts file and rem out all references to megaupload next time I need to get something from there Thanks for watching over us, plodr

Code:

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 8c78da00, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 83201fb6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82ba0718
Unable to read MiSystemVaType memory at 82b80160
 8c78da00 

CURRENT_IRQL:  2

FAULTING_IP: 
ataport!IdeLogCrbActive+94
83201fb6 a5              movs    dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  8078ad08 -- (.trap 0xffffffff8078ad08)
ErrCode = 00000000
eax=84dd3928 ebx=84c8e5c0 ecx=8c78d9d0 edx=00000001 esi=8c78da00 edi=84c8e5c0
eip=83201fb6 esp=8078ad7c ebp=8078ad88 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
ataport!IdeLogCrbActive+0x94:
83201fb6 a5              movs    dword ptr es:[edi],dword ptr [esi] es:0023:84c8e5c0=???????? ds:0023:8c78da00=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 83201fb6 to 82a7e81b

STACK_TEXT:  
8078ad08 83201fb6 badb0d00 00000001 00000002 nt!KiTrap0E+0x2cf
8078ad88 8320a0e8 84dd3928 84e354a0 00000000 ataport!IdeLogCrbActive+0x94
8078adac 833b7074 84dd3928 8078ade4 82a05a2e ataport!IdeStartIoCallBack+0x5c
8078adb8 82a05a2e 855a0030 00000000 84dd3984 PCIIDEX!BmReceiveScatterGatherList+0x1e
8078ade4 833b7199 84dd3984 855a0030 84e35480 hal!HalBuildScatterGatherList+0x1ba
8078ae20 83209b46 855a00e8 84dd3928 84dd3900 PCIIDEX!BmSetup+0x3d
8078ae3c 8320a041 84cc60e0 84dd3900 84dd3928 ataport!IdePortSetupScatterGatherList+0x2a
8078ae54 83208a12 84cc60e0 84dd3928 84ecbb8a ataport!IdeDispatchChannelRequest+0x59
8078ae6c 83208c6a 84cc60e0 84dd3928 84ecb900 ataport!IdeStartChannelRequest+0x42
8078ae80 8320a2a0 855a30e8 84ecb900 84cc60e0 ataport!IdeStartNextDeviceRequest+0x22
8078aef4 8320a66b 84cc60e0 84ecb900 84cc609c ataport!IdeProcessCompletedRequests+0xd8
8078af48 82aa04f5 84cc609c 84cc6028 00000000 ataport!IdePortCompletionDpc+0xab
8078afa4 82aa0358 82b61d20 a4604d48 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 82a9fb1c 8c781c70 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 8c781c70 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82a9fb1c 00000000 0000001a 00d6850f bb830000 0x8c781c70


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdeLogCrbActive+94
83201fb6 a5              movs    dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ataport!IdeLogCrbActive+94

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf16

FAILURE_BUCKET_ID:  0xD1_ataport!IdeLogCrbActive+94

BUCKET_ID:  0xD1_ataport!IdeLogCrbActive+94

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

0: kd> .trap 0xffffffff8078ad08
ErrCode = 00000000
eax=84dd3928 ebx=84c8e5c0 ecx=8c78d9d0 edx=00000001 esi=8c78da00 edi=84c8e5c0
eip=83201fb6 esp=8078ad7c ebp=8078ad88 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
ataport!IdeLogCrbActive+0x94:
83201fb6 a5              movs    dword ptr es:[edi],dword ptr [esi] es:0023:84c8e5c0=???????? ds:0023:8c78da00=????????
0: kd> lmvm ataport
start    end        module name
83200000 83223000   ataport    (pdb symbols)          c:\symbols\ataport.pdb\7AC193B7BDE242239273B5CD16763D751\ataport.pdb
    Loaded symbol image file: ataport.SYS
    Mapped memory image file: c:\symbols\ataport.SYS\4A5BBF1623000\ataport.SYS
    Image path: \SystemRoot\system32\DRIVERS\ataport.SYS
    Image name: ataport.SYS
    Timestamp:        Tue Jul 14 00:11:18 2009 (4A5BBF16)
    CheckSum:         0002F425
    ImageSize:        00023000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ataport.sys
    OriginalFilename: ataport.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  ATAPI Driver Extension
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

The debugger references the standard Windows 7 ATAPI driver which controls the drives connected. This is unlikely to be the cause - if the driver is the real thing. Can you check the System and Application logs for other clues around the time of the error?

After scanning through the list of drivers loaded on your system at the time of the crash, I don't see any that I recognise as being outdated. I think a trip to the Malware section might be in order next, just to ensure the PC is clean.

If you get the all clear from the Malware folks, remove AVG completely and install Avast!, Avira or MSE instead.

Any more BSOD's, attach them here.