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.

Photo

nv4_mini.sys Intermittent BSOD. Help needed narrowing down the cause.


  • Please log in to reply
4 replies to this topic

#1 GuitarGeek

GuitarGeek

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:22 AM

Posted 28 May 2009 - 08:29 PM

Hey all,
I have been getting a random BSOD on Windows XP with SP3. The BSOD is intermittent, but I just built this system and feel like I shouldn't be having this issue.
I will be copying my Windbg report here for you to look over.

System Specs:
ECS BLACK SERIES GF8200A (V1.0) AM2+/AM3 NVIDIA GeForce 8200 HDMI ATX AMD Motherboard
HITACHI 0A38016 1TB 7200 RPM SATA 3.0Gb/s 3.5" Internal Hard Drive
OCZ SLI-Ready Edition 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
AMD Athlon 64 X2 6000+ Windsor 3.0GHz Socket AM2 125W Dual-Core Processor Model ADX6000IAA6CZ
Truepower 2.0 550W Power Supply
SAMSUNG 22X DVD Burner Black SATA Model SH-S223F
Lite-On 22X DVD Burner IDE

I have ran Speedfan diagnostics and all temps appear to be in normal range, with only the GPU being at 40C or above.

I ran Memtest86 for 3 hours and returned no errors, but I intend to run it overnight tonight.
Here is the Windows Debug report:

BugCheck 9C, {0, b833c050, b20b4000, 175}

*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
Probably caused by : nv4_mini.sys ( nv4_mini+1e0b33 )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: b833c050
Arg3: b20b4000
Arg4: 00000175

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

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- Bios and Kernel Developers Guid for AMD Athlon® 64 and AMD Opteron® Processors
Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000001011010000000000000000000000000000000000000101110101


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

MEMHIRERR - Memory Hierarchy Error {TT}CACHE{LL}_{RRRR}_ERR
These errors match the format 0000 0001 RRRR TTLL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_PCC_MEMHIRERR_75

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x9C_AuthenticAMD

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: firefox.exe

LAST_CONTROL_TRANSFER: from 806e9bfb to 804f9f43

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb833c0c0

STACK_COMMAND: dds B833C0C0-0x20 ; kb

STACK_TEXT:
b833c0a0 00122092
b833c0a4 10521311
b833c0a8 640201b1
b833c0ac 13470023
b833c0b0 36b57d2a
b833c0b4 bff333f6
b833c0b8 0ae2b10f
b833c0bc b771bb33 nv4_mini+0x1e0b33
b833c0c0 5404ec0e
b833c0c4 99fa6eca
b833c0c8 444dc42a
b833c0cc 088bc5ea
b833c0d0 fbbfffe7
b833c0d4 df2f4bfc
b833c0d8 acfcedcc
b833c0dc 7ecc476e
b833c0e0 000484c4
b833c0e4 004c8800
b833c0e8 080c40e0
b833c0ec 8c8c0887
b833c0f0 acf2cf6d
b833c0f4 ccacc8ec
b833c0f8 0abcb84c
b833c0fc ac96dd48
b833c100 005a3121
b833c104 6b599025
b833c108 3a222133
b833c10c 8335b651
b833c110 7bbdfffb
b833c114 273f9aff
b833c118 7b761397
b833c11c fe377f6b


FOLLOWUP_IP:
nv4_mini+1e0b33
b771bb33 56 push esi

SYMBOL_NAME: nv4_mini+1e0b33

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49fa9709

FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_nv4_mini+1e0b33

BUCKET_ID: 0x9C_AuthenticAMD_nv4_mini+1e0b33

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


Anyone have any idea what could be causing this? I know the code it is throwing is hardware failure, but the problem appears to be caused by a driver. I already updated all nVIDIA drivers to the most current release and updated my chipset drivers. All of these parts are brand new, I just got the comp up and running on Wednesday.

Thanks in advance one and all.

BC AdBot (Login to Remove)

 


#2 TallyHo

TallyHo

  • Members
  • 43 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:OZTRALIA
  • Local time:10:22 PM

Posted 28 May 2009 - 09:04 PM

hi.

long thread, but worth the time!

hope it helps solve your problem..worked for a mate of mine..

:thumbsup: :flowers:

#3 GuitarGeek

GuitarGeek
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:22 AM

Posted 29 May 2009 - 09:27 AM

Hmmm, is my post too long or is my problem just not interesting?

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,246 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:07:22 AM

Posted 29 May 2009 - 11:36 AM

http://www.file.net/process/nv4_mini.sys.html

http://forums.techguy.org/all-other-softwa...video-card.html

I would follow the suggestions in the second link...uninstall the video drivers, reboot and then reinstall the video drivers.

<<PROCESS_NAME: firefox.exe>>

But...I see Firefox also mentioned on your bug report...it also has drivers and could be the culprit. It won't hurt to uninstall/reinstall it.

<<BugCheck 9C>>

Worth reading, http://support.microsoft.com/kb/329284

FWIW: Memtest86 is unreliable, you should run Memtest86+, available at Memtest86+ - Advanced Memory Diagnostic Tool - http://www.memtest.org/#downiso

FWIW: http://en.wikipedia.org/wiki/Memtest86, read the lines under Known Problems.

Louis

#5 GuitarGeek

GuitarGeek
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:22 AM

Posted 30 May 2009 - 04:08 PM

Didn't work. I am going to run a registry cleaner. Any more ideas? This has me at my wits end.

I am going to reinstall windows and see what happens.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users