Black screen, log tells me: 0x100000d1 + minidump

[Anlavabeed]

Hello,

Today all of a sudden my screen turned black and my monitor went on standby after a startup. I just had put in an USBstick and I opened Firefox when this happened. I manually rebooted the system. A minidump was saved.

In the logfiles I found this error:
0x100000d1 (0xf7e4d000 0x00000005 0x00000000 0xf7787cb1) On http://aumha.org/a/stop.htm this error is not mentioned.

My machine:
Windows XP Home SP3 (recently installed)
Abit IP-95
Pentium 4 3,4Ghz
1 GB Ram DDR
SATA HD Seagate Barracuda 80GB (a week ago checked with checkdisk: no problems found)
ATI Radeon X1800XL

Not a clue what this might be. Can somebody help? it is much appreciated. Thanks.

 

[raybay]

Likely the USB drive has damaged software on it... or is itself damaged.

 

[Anlavabeed]

Likely the USB drive has damaged software on it... or is itself damaged.

Thanks. What did you find exactly in the minidump? The USB stick is brandnew.

==============================================================

Edit:

Hmmm, today the monitor went black again after a startup, and the USB stick wasn't attached to the computer so it had nothing to do with that.

The Event log gave me this error:
0x100000d1 (0xf7f14000 0x00000005 0x00000000 0xf7787cb1)

I have attached the new minidump. Hopefully this problem can be found.

==============================================================

Edit:

I was able to debug both the minidump files, and they are both pointing at the Viamraid.sys driver:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini011409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Jan 14 11:27:45.687 2009 (GMT+1)
System Uptime: 0 days 0:00:57.265
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................

Loading User Symbols
Loading unloaded module list
...
Unable to load image viamraid.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for viamraid.sys
*** ERROR: Module load completed but symbols could not be loaded for viamraid.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {f7f14000, 5, 0, f7787cb1}

*** WARNING: Unable to verify timestamp for SCSIPORT.SYS
*** WARNING: Unable to verify timestamp for hal.dll
Probably caused by : viamraid.sys ( viamraid+dcb1 )

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: f7f14000, memory referenced
Arg2: 00000005, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f7787cb1, address which referenced memory

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


READ_ADDRESS: f7f14000

CURRENT_IRQL: 5

FAULTING_IP:
viamraid+dcb1
f7787cb1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from f778db96 to f7787cb1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805571f8 f778db96 86555004 86598d5c 86598d5c viamraid+0xdcb1
80557220 f777df36 86555004 00598d5c 86555004 viamraid+0x13b96
8055724c f777e288 01555004 866edae8 a4fff94c viamraid+0x3f36
80557264 f77638eb 86555004 a4fff94c a4fff94c viamraid+0x4288
80557288 804db6ab 866eda30 00000002 866edae8 SCSIPORT!SpStartIoSynchronized+0x14f
805572c8 807056e8 866eda30 85cf7e70 00000000 nt!KiReadyThread+0x5f
805572f4 80518bf8 867e2d80 866eda64 00000001 hal!HalpBiosDisplayReset+0x322
8055730c f776564d 867e2d80 866eda30 00000001 nt!CcSetDirtyPinnedData+0x26
80557344 804e60d9 866eda30 85cf7e70 866edae8 SCSIPORT!ScsiPortStartIo+0x23f
80557364 f7763d5e 866eda30 85cf7e70 00000000 nt!KiDeliverApc+0x197
8055738c f7766195 00000000 00000000 866edae8 SCSIPORT!GetNextLuRequest+0x92
805573b8 f77666f7 866edae8 8633a480 80557427 SCSIPORT!SpProcessCompletedRequest+0x391
80557428 804dcd21 866edaa4 866eda30 00000000 SCSIPORT!ScsiPortCompletionDpc+0x2b5
8055743c 80561f20 80561cc0 ffdffc50 00000000 nt!ZwFlushWriteBuffer+0x11
80557440 80561cc0 ffdffc50 00000000 80561cc0 nt!WmipLoggerContext+0xa0
80561f20 00000000 80561f28 80561f28 80561f30 nt!WmipAnyoneAccessSecurityDescriptor


STACK_COMMAND: kb

FOLLOWUP_IP:
viamraid+dcb1
f7787cb1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: viamraid+dcb1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: viamraid

IMAGE_NAME: viamraid.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48757fa5

FAILURE_BUCKET_ID: 0xD1_viamraid+dcb1

BUCKET_ID: 0xD1_viamraid+dcb1

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

Any ideas what I could do?

 

[Route44]

Your minidump error is a 0xD1 and these are caused by faulty drivers or buggy software. The driver cited is viamraid.sys which is a VIA Raid Driver for Windows XP or VIA AHCI Raid Driver for WIN 2000/XP belonging to the software VIA RAID driver or viamraid by VIA.

Either uninstall and re-install the drivers or update to the latest drivers.

*** Let us know if this either fixed or did not fix your issues.

 

[Anlavabeed]

Deleted double

 

[Anlavabeed]

I need a bit of advice before I do that if you don't mind.

I recently installed the above mentioned SATA harddisk into my computer and after that Windows XP SP3. Within the Bios in the Advanced features there is the option 'SATA-IDE'. I can disable it, set it to IDE or RAID.

After I started installing XP setup asked for a 3rd party Raid driver so I used the lastest version at that time (two weeks ago this was the VIA V-RAID Driver v5.80c) and created a floppy. However, after a while during installation I received an error that the VIA RAID Controller 3149 didn't comply to the Windows Logo test which checks the compatibility with Windows XP (or something similar, I translated it from dutch). It gave me the same error when I used the floppy made from the 5.21A Hyperion driver.

So I used the Raid driver from the Abit website instead of the new one.
Everything went fine. Later I installed the chipset drivers (Hyperion v521A) and other drivers in Windows without any problems.

A week later I was adviced to change the setting of the controller to IDE instead of RAID within the Bios because I only have one harddisk.

I searched for all the Viamraid.sys files on my harddisk and I found these:

-version 5.1.2600.530 (from the Abit floppy) at
C:\Windows\System32\ReinstallBackups\0011\DriverFiles
C:\Windows\OemDir

-version 5.1.6000.581 (Hyperion 521A) at
C:Windows\System32\drivers

Can there be some kind of conflict because I used two different versions? Can I safely install a new driver?

 

[Route44]

I know nothing about RAID set-ups so I don't want to venture any guesses as to how to help you. I will say that a SATA harddrive is not an IDE harddrive. IDE is being phased out,

The SATA harddrive should have been set to Master (or at least neutral) and set to SATA in the BIOS.

And since your system wasn't configured to RAID there is little wonder to why that VIA Driver floppy didn't work.

Perhaps raybay will respond later and give more knowlegeable experience. He knows tons more than I do.

Have you tried setting your HD to SATA in the BIOS?

 

[Anlavabeed]

There is no option for SATA, it is either IDE, RAID or Disbabled. When I set the controller to IDE the harddisk shows up in the Bios as a SATA drive, when I set it to RAID I can't find it in the Bios. The harddisk works fine though in both options.

Unfortunately there is nothing to find in the manual about Bios settings.

And since your system wasn't configured to RAID there is little wonder to why that VIA Driver floppy didn't work.

The Abit Raid floppy driver worked fine though.

BTW There is no option to set the SATA drive to Master or Slave (which is normal).

 

[Route44]

That is true about SATA, my bad. It gets tricky sometimes when you set SATA as the C Drive and slave an IDE. But I am aware you didn't do this. Have you tried the Abit forums (if they are still active)?

 

[Anlavabeed]

I haven't tried the Abit forum yet, thanks for letting me know, good idea. But Abit is no longer selling motherboards anymore, so I'm not sure if they support it either. I will have a look later.

But I personally doubt it is a Bios problem and/or RAID setting problem. I worked perfect for a few weeks without any crashes.

 

[Route44]

Well since you aren't running in RAID try uninstalling the VIA Raid drivers for Windows. Per minidumps it says this is the cause.

 

[Anlavabeed]

I will do what you suggested. However it did not crash today as it did last two days. So maybe I will never know if it helped or not. I'll keep you guys updated.

==========================================================
Edit:
After I removed the VIA Raid driver my computer didn't boot anymore! I got the BSOD!
STOP: 0x0000007B (0xF7C46524, 0xc0000034, 0x00000000, 0x00000000)

I received the exact same error twice (also when I did try to boot in safe mode). i had to install an image I made two weeks ago but unfortunately I lost all my emails, favorites, etc. Grrrrrr. :-(

 

[Route44]

Crap! Man I'm really sorry. I feel terrible suggesting you might want to uninstall the VIA Raid driver. Here is your error

0x0000007B: INACCESSIBLE_BOOT_DEVICE

Windows lost access to the system partition or boot volume during the startup process. Typical causes: Installing incorrect device drivers when installing or upgrading storage adapter hardware, or a virus.

 

[Anlavabeed]

It is no big problem. I was able to find back most of my emails on my old harddisk. Pffew!

Anyway, I removed the driver/hardware in the Device Manager. Was that the correct way to do it? Is it normal that Windows lost access to the system partion because I deleted the VIA RAID controller?

Hopefully Raybay can tell us more if he reads this. This problem is getting on my nervs. ;-)

 

[Route44]

Take my next piece of advice for what it is. But perhaps you could post your issue in the Network & Storage forums because of the nature of your problem.

Just a thought.

 

[Anlavabeed]

I have done what you said. In the other thread someone gave me a tip to post the porblem on the VIA Arena forum.

It turns out that newer versions than the VIA Hyperion v5.18A drivers are causing this problem! So hopefully problem is fixed!

Thanks for your help so far.

 

[Route44]

Thanks for the reply! I'm feeling better. The minidumps did point to these drivers, but I really thought I messed you up. How did you resolve this? Roll back the driver?

 

[Anlavabeed]

Well, rolling back the driver won't work, it is the only which is on the machine. I need to uninstall the current Hyperion dirvers, and then install an older version. I haven't tried it yet though, so I'm not 100% sure it is the solution. If it didn't help, I will let you know.