Random BSOD Windows 7

Hi. On behalf of my colleagues and myself, thanks!

If overclocking anything in any way, set back to default factory values.

Which motherboard do you have? I can tell you where to get latest drivers related to it.

These are the older ones and need to be updated:

Code:

nvm62x32 nvm62x32.sys Fri Oct 17 17:00:39 2008
CLBStor  CLBStor.SYS  Thu Oct 25 22:38:49 2007
RTKVAC   RTKVAC.SYS   Thu Jun 18 15:36:37 2009

Wow... how quick was that! Thanks.

No overclocking being done.

Abit AN8 Ultra (nforce 4).

Many Thanks Again,
soup

That nForce4 is rough since NVIDIA does not support it any longer.

I'd update to the latest bios from here:

Universal abit > Motherboard, Digital Speakers, iDome, AirPace, Multimedia

And install the audio driver for Windows 7 from here:

Realtek

Finally, uninstall Cyberlink Storage Helper to get CLBStor.sys off the system.

Many thanks again for your help Torrentg. I'll do that and get back to you.

Thanks,
soup

Best of luck to ya!

Keep us updated how things seem to be going either way.

In the future, you can install from the device manager like this:

Right click on the device you're updating - Update driver software. Browse my computer. Let me pick. Have disk. Browse. Double click the .inf from the new driver folder. Hit ok. Hit next.

Hi again torrentg,
You said keep us updated.
Old drivers replaced last Monday morning, all was good for 4 days, I used the pc lots, I thought it was sorted then on Thursday evening it crashed again. However, this time I understood the message as the BSOD named nvm62x32.sys as the culprit, a driver you'd flagged as a problem yourself. Also, as you pointed out, my nforce4 board is no longer supported.
I downloaded some nforce7 drivers (I think they were) and installed the Ethernet driver, Windows said it didn't think the drivers would run my hardware but I installed anyway.
No BSOD since then and I've worked the pc and network card hard, so looking good.
A million thanks for your advice yet again.
soup

Hi,
Thanks for previous help but bad news, I've just had another crash, the pc was sitting idle, just a couple of web pages open. I've attached my minidump. Can someone please advise?
Many Thanks In Advance Again,
soup

soup said:

Hi,
Thanks for previous help but bad news, I've just had another crash, the pc was sitting idle, just a couple of web pages open. I've attached my minidump. Can someone please advise?
Many Thanks In Advance Again,
soup

Hi and welcome
This crash was probably caused by ataport.sys I suspect anther issue is but having only 1 DMP I cannot be sure. THe issue I susppect is either heat or ram.

I would
download memtestx86 andrun it for several hours at least (overnight preferred)
update the driver involved
run a system file check to verifu (and fix) your system files
type cmd in search>right click and run as admin>sfc /scannow

Good luck

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\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
---------