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

Can't use right click format


  • Please log in to reply
10 replies to this topic

#1 Balta

Balta

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:05:29 PM

Posted 14 February 2009 - 11:04 AM

Hi, everything became because in my windows couldn't not use format after right click on any drive, window doesn't popup or give any ind of error.

I thought was some kind of malware and open this topic here:
http://www.bleepingcomputer.com/forums/topic199621-30.html


Now like asked by The Panda I'm opening this one as since trying to fix my windows doesn't boot normal at all, please read that topic and see if anyone can help me restoring everything like was supose to be normal.

Thanks.

BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:29 PM

Posted 14 February 2009 - 03:49 PM

Let's start out by checking out the memory dump files from the Blue Screen events (using the link below for instructions.
In particular we're interested in the ones that occurred while you were using the Driver Verifier.

There's no need to use Driver Verifier at this point. Verifying all drivers will (as you experienced) slow your system down dramatically. Also, when Driver Verifier finds a malfunctioning driver it will generate a Blue Screen crash. It's the memory dump files from that that can be used to track down the offending driver.

Just copy/paste the results of each analysis here and we'll work our way through them.

http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 DaChew

DaChew

    Visiting Alien


  • Members
  • 10,317 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:millenium falcon and rockytop
  • Local time:12:29 PM

Posted 14 February 2009 - 03:53 PM

http://www.michaelstevenstech.com/XPrepairinstall.htm

You might follow these directions exactly and see what effect running windows as a repair disk has

It's been my experience that on a single boot OS having it on D is not a good idea and somehow the initial install was faulty

A clean install on a newly partitioned and formatted hard drive with only that hard drive in the computer would be the best option
Chewy

No. Try not. Do... or do not. There is no try.

#4 Balta

Balta
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:05:29 PM

Posted 15 February 2009 - 11:15 AM

Let's start out by checking out the memory dump files from the Blue Screen events (using the link below for instructions.
In particular we're interested in the ones that occurred while you were using the Driver Verifier.

There's no need to use Driver Verifier at this point. Verifying all drivers will (as you experienced) slow your system down dramatically. Also, when Driver Verifier finds a malfunctioning driver it will generate a Blue Screen crash. It's the memory dump files from that that can be used to track down the offending driver.

Just copy/paste the results of each analysis here and we'll work our way through them.

http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/



Not allways have blue screens, the start is a bit erratic, some times after 4 or more auto reboots he starts normaly.

I have the auto reboot option disabled. I found out that I had a lot of registry keys with nulls that I managed to fix and delete, anyway I can't find anywhere information about how to recreat all the missing keys. So I tryed to do again a repair install witch is not booting again and keeps rebooting on the startup logo.

Going to boot in recovery console and restore the last registry backup before the recovery install.
After going to try to folow all that iinformation on the page you provide and post here what ou need.

Thanks.

UPDATE: Since I can only boot in safe mode the folowing is upening right now.

I can't install the debuging tools it says that "the system administrator is set policies that prevents this instalation"
Also another strange thing the minidump file is not recent and I have only this one "Mini020809-01.dmp" strange that even having 2 or 3 blue screens the minidump stays exactly the same one.

The memory.dmp file has almost 2Gb uauuuuuuu, is it normal?

So I don't know what to do from now on?

Edited by Balta, 15 February 2009 - 01:11 PM.


#5 Balta

Balta
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:05:29 PM

Posted 15 February 2009 - 02:42 PM

Ok here is the the log you asked for:


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


Loading Dump File [D:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

************************************************************
WARNING: Dump file has been truncated. Data may be missing.
************************************************************
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Windows XP Kernel Version 2600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x00000000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Feb 15 17:21:06.656 2009 (GMT+0)
System Uptime: 0 days 0:09:40.347
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
CS descriptor lookup failed
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get program counter
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {3c, 80001324, 8b2975b0, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 1
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
?: kd> !analyze -v
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get program counter
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000003c, ObReferenceObjectByHandle is being called with a bad handle.
Arg2: 80001324, bad handle passed in,
Arg3: 8b2975b0, object type,
Arg4: 00000000, 0.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 1
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0

BUGCHECK_STR: 0xc4_3c

DEFAULT_BUCKET_ID: DRIVER_FAULT

STACK_TEXT:
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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

GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002

#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:29 PM

Posted 15 February 2009 - 04:29 PM

That's a regular memory dump, let's enable the small memory dump and see what you get.
Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Under Write Debugging Information, select Small Memory Dump (64 kB)
Then click OK to exit the dialog and save the changes.

Reboot into normal mode to see if you can get a small memory dump (BSOD).
If not, and if you're feeling courageous, re-run Driver Verifier, reboot and see what happens.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 Balta

Balta
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:05:29 PM

Posted 15 February 2009 - 06:21 PM

Strange now I can't get blue screens even with verifier on. Anyway the boot sometimes still autoreboots a couple of times, but if I choose at boot menu debug mode, allways works, apart that windows looks like runnnig smooth just two problems, one the initial one that I can use right click format anywhere and a new one that is the Security Center al ways reports that I dont have any antivirus installed, and I have Kaspersky runnig ok with lasted updates.

Update:

Just found more problems, the WMI is not working. I tryed everything to repair/rebuild but nothing works. Because of that firewall is not working also on the network properties the firewall TAB is desapeared or not normal as should be.

I think the security center is no working because of the WMI problem.

What can I do now?

Edited by Balta, 16 February 2009 - 06:02 AM.


#8 Balta

Balta
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:05:29 PM

Posted 16 February 2009 - 04:12 PM

Ok fixed the WMI problems and windows looks and running smooth now.

So back to the initial problems:

- In my computer right click in any drive and select fromat doesn't open any windows nor gives any error/messages.

- Every start the security center reports that I don't have any anti-virus even Kaspersky is installed and updated 100%, strange is if I restart the Security Center service this desapears and only shows again on next boot.

#9 Balta

Balta
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:05:29 PM

Posted 20 February 2009 - 12:28 PM

UPDATE:

After a few days I solved the Security Center problem now is OK.

So remaining problem and the initial one is, I can't use format anyware, right-click or trought computer managment.

In computer managment I get a error after trying to format any drive, USB pen, etc. like this:

"The operation did not complete. Check the System Event Log for more information on the error."


Event Viewer shows this error on System: Event ID:2 Source: LDM Unspecified error (80004005).


Also like I said before roght click on any drive letter and format, doesn't open any windows or gives any error/message.

Edited by Balta, 20 February 2009 - 01:40 PM.


#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:29 PM

Posted 24 February 2009 - 07:39 AM

Most references to the LDM error refer to a problem with RAID. Do you have RAID installed? If so, have you tried updating the RAID drivers in XP?
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#11 Balta

Balta
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:05:29 PM

Posted 24 February 2009 - 09:04 AM

No I don't have RAID installed, not even is ON in the mother board bios.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users