Random BSOD Windows 7

Many thanks Zigzag,
I'm having trouble finding an update for the ataport.sys driver, I can't find a download for it, any advice?
I've also attached my last 3 minidumps which includes the one you've offerd advice about already.
Many Thanks,
soup

soup said:

Many thanks Zigzag,
I'm having trouble finding an update for the ataport.sys driver, I can't find a download for it, any advice?
I've also attached my last 3 minidumps which includes the one you've offerd advice about already.
Many Thanks,
soup

Hi soup

Ataport.sys is part of an IDE HD driver. It might be part of a BIOS upgrade, or should be availible from the mobo manufacturer.

Dont know if you are 32bit or 64

Let me know if you need help with it

I will take a peek at the latest DMPS just in case

Ken J+

soup said:

Many thanks Zigzag,
I'm having trouble finding an update for the ataport.sys driver, I can't find a download for it, any advice?
I've also attached my last 3 minidumps which includes the one you've offerd advice about already.
Many Thanks,
soup

Hey soup
One dmp is corrupt. One says ataport and one says : nvm62x32.sys which is part of your nvidea lan driver

Upgrade both just in case

Ken J+

Code:

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


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

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82810000 PsLoadedModuleList = 0x82958810
Debug session time: Fri Dec 11 03:33:36.930 2009 (GMT-5)
System Uptime: 0 days 23:24:27.180
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {80000008, 4, 0, 9128389a}

Unable to load image \SystemRoot\system32\DRIVERS\nvm62x32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvm62x32.sys
*** ERROR: Module load completed but symbols could not be loaded for nvm62x32.sys
Probably caused by : nvm62x32.sys ( nvm62x32+2089a )

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

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: 80000008, memory referenced
Arg2: 00000004, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 9128389a, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82978718
Unable to read MiSystemVaType memory at 82958160
 80000008 

CURRENT_IRQL:  4

FAULTING_IP: 
nvm62x32+2089a
9128389a f6400808        test    byte ptr [eax+8],8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  82936b34 -- (.trap 0xffffffff82936b34)
ErrCode = 00000000
eax=80000000 ebx=00000000 ecx=9129d4c0 edx=00000053 esi=8645d000 edi=86866ed0
eip=9128389a esp=82936ba8 ebp=82936ba8 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nvm62x32+0x2089a:
9128389a f6400808        test    byte ptr [eax+8],8         ds:0023:80000008=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 9128389a to 828567eb

STACK_TEXT:  
82936b34 9128389a badb0d00 00000053 aa589e15 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
82936ba8 9127831d 80000000 82936bc8 91268a8f nvm62x32+0x2089a
82936bb4 91268a8f 9129d4c0 80000000 858c10e0 nvm62x32+0x1531d
82936bc8 8aee0317 8645d000 82936bfb 82936bf0 nvm62x32+0x5a8f
82936bfc 8284f7ad 863e1780 86866ed0 82936c28 ndis!ndisMiniportIsr+0x67
82936bfc 90320bb6 863e1780 86866ed0 82936c28 nt!KiInterruptDispatch+0x6d
82936c98 82895695 84fe5d48 82943280 82939c00 amdk8!C1Halt+0x4
82936d20 8287800d 00000000 0000000e 00000000 nt!PoIdle+0x538
82936d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvm62x32+2089a
9128389a f6400808        test    byte ptr [eax+8],8

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nvm62x32+2089a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvm62x32

IMAGE_NAME:  nvm62x32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48f8fcf7

FAILURE_BUCKET_ID:  0xD1_nvm62x32+2089a

BUCKET_ID:  0xD1_nvm62x32+2089a

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

Code:

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


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

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82846000 PsLoadedModuleList = 0x8298e810
Debug session time: Wed Dec 16 07:07:14.505 2009 (GMT-5)
System Uptime: 0 days 1:51:51.724
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {296cb44, 1f, 0, 828e210e}

Probably caused by : ataport.SYS ( ataport!IdePortCompletionDpc+b7 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0296cb44, memory referenced
Arg2: 0000001f, IRQL
Arg3: 00000000, 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: 828e210e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 829ae718
Unable to read MiSystemVaType memory at 8298e160
 0296cb44 

CURRENT_IRQL:  1f

FAULTING_IP: 
nt!EtwpReserveTraceBuffer+72
828e210e 8b0e            mov     ecx,dword ptr [esi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  8296cabc -- (.trap 0xffffffff8296cabc)
ErrCode = 00000000
eax=85001408 ebx=85a2c880 ecx=00000000 edx=0000001c esi=85001408 edi=0000000c
eip=828e210e esp=8296cb30 ebp=8296cb5c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!EtwpReserveTraceBuffer+0x72:
828e210e 8b0e            mov     ecx,dword ptr [esi]  ds:0023:85001408=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828e210e to 8288c7eb

STACK_TEXT:  
8296cabc 828e210e badb0d00 0000001c 8296cb1c nt!KiTrap0E+0x2cf
8296cb5c 828fdad5 8296cb90 8296cb98 00609a02 nt!EtwpReserveTraceBuffer+0x72
8296cba0 828fecdc 8296cbf0 00000000 00000000 nt!EtwpLogKernelEvent+0x1dd
8296cbcc 82956f6a 8296cbf0 00000001 20000002 nt!EtwpTraceKernelEvent+0x47
8296cc0c 828b65f3 8282a082 8296cc28 00000000 nt!PerfProfileInterrupt+0xa0
8296cc34 8ab6b677 00000000 84fdc23c 8281a58d nt!KeProfileInterruptWithSource+0x23
8296cd20 828ae00d 00000000 0000000e 00000000 ataport!IdePortCompletionDpc+0xb7
8296cd34 00000000 00000000 00000000 00000000 nt!KiIdleLoop+0xd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdePortCompletionDpc+b7
8ab6b677 c9              leave

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ataport!IdePortCompletionDpc+b7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf16

FAILURE_BUCKET_ID:  0xA_ataport!IdePortCompletionDpc+b7

BUCKET_ID:  0xA_ataport!IdePortCompletionDpc+b7

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

Hi Again Zigzag,
It's an Abit nforce4 mobo, ataport.sys is not part of the driver package as far as I'm aware. It's also no longer supported. Bios is up to date, flashed last week.
I downloaded the drivers for the Nvidia nforce7 board to update the nvm62x32.sys driver which went ok.
Windows 7 32 bit.
Thanks Again,
soup

Hi Again,
1.Ran memtest86 for just under 11 hours, 8 passes, no errors.
2.Verified system files, no problems.
Still can’t find a download to update ataport.sys, can anybody advise where I might find it or what package it might come in please?
Thanks,
Soup
32 bit
Abit Nforce4 mobo

Hi

I have a same problem with Asus A8N-E on nforce4 (with dual opteron 185, 4gb memory). Also worked pefect under Windows Vista x64 and also has random BSODs in Windows 7 x64. I did almost everything - removed all third-party software (at least the one with drivers), installed the latest nvidia built-in network controller driver, installed SATA drivers from Vista x64, changed audio and video cards, moved the system from PATA IDE onto SATA (it means, I have no any pata devices in my system) - thought may be ATA driver is responsible for the problems (NVIDIA doen't update it for years and you have to use the built-in one), run memtest86 for more than 12 hours (of course, there was no any problems), watched for the temperature.

Nothing helps. A system just crashes after 12-24 hours of an uptime. BSOD is ALWAYS different (the last one - Pool_corruption). On two other computers (notebooks, based on intel chipsets) Win7 runs perfectly, without any single glitch.

It looks like, that Win7 x64 is simply incapable to run on NFORCE4 motherboards. Or, at least on some of them. Now I have to decide, should I go back on Windows Vista, install Linux (not really the option for a home pc) or get a new motherboard (this involves getting of new cpu, memory, psu and cooler).