Sign in with
Sign up | Sign in

Nvstor64 Event ID:9

Last response: in Storage
Share

Greetings!
I have a known issue with nvstor64, but I`d rather ask again to make sure just how to respond to the issue.
Here's my log:


Log Name: System
Source: nvstor64
Date: 12/1/2012 11:46:24 AM
Event ID: 9
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Ciel-PC
Description:
An unknown error has occured on this device.

Device: \Device\RaidPort1
Model: WDC WD5000AADS-00S9B0
Firmware Version: 01.0
Serial Number: WD-WCAV95339484
Port: 1

- System

- Provider

[ Name] nvstor64

- EventID 9

[ Qualifiers] 49374

Level 2

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2012-12-01T09:46:24.568359300Z

EventRecordID 13799

Channel System

Computer Ciel-PC

Security


- EventData

\Device\RaidPort1
WDC WD5000AADS-00S9B0
01.0
WD-WCAV95339484
1
0000000005002800000000000900DEC0000000000000000000000000000000000000000000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00000000 00280005 00000000 C0DE0009
0008: 00000000 00000000 00000000 00000000
0010: 00000000 00000000


In Bytes

0000: 00 00 00 00 05 00 28 00 ......(.
0008: 00 00 00 00 09 00 DE C0 ......?A
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

PLEASE HELP!

More about : nvstor64 event

Related ressources

System Information (local)
--------------------------------------------------------------------------------

computer name: CIEL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X2 245 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4294238208 total
VM: 2147352576, free: 1960726528




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 11/28/2012 12:37:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112812-21296-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF8800149DEA4)
Bugcheck code: 0xD1 (0x1, 0x2, 0x0, 0xFFFFF8800149DEA4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 11/15/2012 3:44:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111512-21718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A1FCC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004488038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
!