Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Chronic BSOD

  • Please log in to reply
2 replies to this topic

#1 lynned


  • Members
  • 1 posts
  • Local time:05:08 PM

Posted 15 February 2009 - 05:34 PM

Hi. I'm trying to figure out a BSOD on my wife's pc. Always get a crash during virus scan regardless of which scanner I use. Also often crashes with cd/dvd burning programs or just random crashes because it feels like it. The hardware is my old stuff and worked fine in my old case with my hd's. Oddly, My wife's PC had this same problem before I swapped the hardware. It used to be a P4. Could one of her HDs be the culprit? Also, after swapping the hardware I did a clean install of XP pro, SP3 and installed all the latest drivers.
MSI K8N Neo4 Platinum
AMD 64 x2 4200+ CPU
2-6600gt XFX video cards (SLI)
2 gb OCZ dual channel ram
one 160 gb sata hd
one 160 gb ide hd

I followed the instructions from here: http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

My WinDbg report:

Microsoft Windows Debugger Version 6.11.0001.402 X86
Copyright Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini021509-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Feb 15 15:52:23.734 2009 (GMT-6)
System Uptime: 0 days 0:24:18.456
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
Unable to load image nvata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvata.sys
*** ERROR: Module load completed but symbols could not be loaded for nvata.sys
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {60, 2, 0, b9ef178c}

Probably caused by : nvata.sys ( nvata+1378c )

Followup: MachineOwner

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

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.
Arg1: 00000060, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b9ef178c, address which referenced memory

Debugging Details:

READ_ADDRESS: 00000060


b9ef178c 8b4660 mov eax,dword ptr [esi+60h]





LAST_CONTROL_TRANSFER: from b9ee7c7d to b9ef178c

WARNING: Stack unwind information not available. Following frames may be wrong.
805513d8 b9ee7c7d 8a56d0e8 00000000 8a56d0e8 nvata+0x1378c
805513f8 b9ee069e 8a56d0e8 8a56d864 00000000 nvata+0x9c7d
80551418 b9ee0e60 8a56d0e8 8a56d864 ffdff9c0 nvata+0x269e
80551428 80545e7f 8a56d1d0 8a56d0e8 00000000 nvata+0x2e60
80551450 80545d64 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


b9ef178c 8b4660 mov eax,dword ptr [esi+60h]


SYMBOL_NAME: nvata+1378c



IMAGE_NAME: nvata.sys


FAILURE_BUCKET_ID: 0xD1_nvata+1378c

BUCKET_ID: 0xD1_nvata+1378c

Followup: MachineOwner

Thanks for any help. Looks like driver error, but, not sure for what.

Edited by lynned, 15 February 2009 - 05:56 PM.

BC AdBot (Login to Remove)


#2 Budapest


    Bleepin' Cynic

  • Moderator
  • 23,579 posts
  • Gender:Male
  • Local time:09:08 AM

Posted 15 February 2009 - 10:34 PM

I believe that nvata.sys is the Nvidia sata/raid driver. You could try reinstalling it and/or the motherboard drivers.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#3 dpunisher


  • BC Advisor
  • 2,234 posts
  • Gender:Male
  • Location:South TX
  • Local time:06:08 PM

Posted 15 February 2009 - 11:03 PM

Beat me to it. Reinstall the motherboard chipset drivers. Get them straight from NVidia, not the driver CD that came with the board. (lynned, I know you said you installed the latest drivers, just covering the bases.)

I am a retired Ford tech. Next to Fords, any computer is a piece of cake. (The cake, its not a lie)

3770K @4.5, Corsair H100, GTX780, 16gig Samsung, Obsidian 700 (yes there is a 700)

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users