1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

chkdsk /f gives BSOD

Discussion in 'Windows XP' started by PeteC, 2003/07/16.

Thread Status:
Not open for further replies.
Page 2 of 2
  1. 2003/07/18
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Newt,

    Don't think it is a problem re voltage - few folks this side of the water have aircon - the weather rarely justifies it!

    The bsods appeared on chkdsk on both my desktop and the laptop (running on batteries, but charging) - and not on my standby m/c - all at the same time of day.

    As I posted earlier I think it is software related - both the laptop and the desktop (both XP SP1 + all updates) have some common progs loaded, the standby is basically bare XP SP1 and does not bsod on chkdsk.

    The camera question may or may not be a red herring, but it's a fact that the camera has never been connected to the standby m/c.

    Seem to have eliminated the updates as the root cause. Intend to run chkdsk ever so often as I load this m/c back up.
     
    PeteC,
    #21
  2. 2003/07/19
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Problem solved - and the culprit is .....

    InCD on NTFS

    Installed XP, SP1 and all critical updates - ran chkdsk - no bsod

    Ran chkdsk after installing InCd 4.0.1.7 and got the bsod posted above.

    Uninstalled InCd and ran chkdsk - no bsod

    Uninstalled InCd from laptop (NTFS) and ran chkdsk - no bsod

    Loaded InCd 4.0.1.7 to standby m/c - FAT32 - no bsod

    It would appear that InCd causes this problem on NTFS volumes only - I shall be emailling Ahead tech when this m/c is back up to speed - still a lot of software/tweaks to go. With hindsight InCd was always a prime candidate with UDF, etc.

    Whether or not other versions of InCd cause the same problem I don't know - and don't intend to find out - life is too short. Fact is I've not run chkdsk on any XP m/c before - never had the need, so the problem could well have been there all the time and might explain other occasional bsods - time will tell.

    Basic question that remains - is this a problem or merely an inconvenience - and what else might InCd be doing to my system??

    I would like to have the facility to use CD-RW's, but not at the expense of m/c problems.

    Mike, Newt - Thanks for your help and advice - one happy camper here :D
     
    PeteC,
    #22


  3. to hide this advert.

  4. 2003/07/19
    mflynn

    mflynn Inactive

    Joined:
    2002/08/14
    Messages:
    4,141
    Likes Received:
    9
    10-4 Pete

    Yes that does sound right to me. It goes along with the error for Fs_REC.SYS which was why I kept asking if you had some unusual file system like a card reader etc. that it was trying to recognize.

    So it was trying to recognize the CD file system.

    Yes most likely it was there all a long. Yes also to it probably causing some intermittent problems.

    The fix for this might be the Adaptec ASPI drivers needed by all CDR drives. Try installing them. Won't hurt. There are many issues related to CDR on XP because of old Aspi drivers. Actually this applies to DVD also. It is also an issue in making Ghost work to a CDR even if everything else seems ok.

    The latest ASPI drivers usually cure most Roxio, Nero and other CDR problems. Lots of times Roxio and Nero are blamed when it is the ASPI layer that is either corrupted or out of date. So if corrupted then latest drivers fix that.

    Get latest ASPI for XP here:
    http://www.adaptec.com/worldwide/co...dgjldffo.0&language=English+US&docType=DRIVER

    Get number 3 on the list aspi 471a2.exe

    Put this in a folder of its own and execute, it will extract.

    After you D/L the above run the aspichk.exe first, it will tell you about your current ASPI version. Run it again after install and compare. I have found that even if aspichk reports no problem but reports a bad date like the year 1600 then something is wrong and the update will fix it.

    Additional info on ASPI. It is usually referred to in SCSI items but is used by CDR. The above link is all you need to update these are only for additional insight.

    http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2002071613342625

    http://www.ncf.carleton.ca/~aa571/aspi.htm


    So INCD should not be install when you update ASPI but then after updating ASPI and rebooting (even if it don’t ask you to) then try installing INCD again and see if chkdsk problem is fixed.

    Mike
     
    Last edited: 2003/07/19
    mflynn,
    #23
  5. 2003/07/19
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Mike,

    Thanks for the suggestion - No go!

    Interestingly aspichk showed no ASPI layer installed (??)

    Looks like InCd is binned, but I shall contact Ahead anyway.
     
    PeteC,
    #24
  6. 2003/07/19
    mflynn

    mflynn Inactive

    Joined:
    2002/08/14
    Messages:
    4,141
    Likes Received:
    9
    10-4

    Was worth a try. When and if they do get back to you that will be one of the first things they will ask about.

    BTW do you have the very latest INCD update?

    But you did leave the ASPI installed, yes?

    Mike
     
    mflynn,
    #25
  7. 2003/07/19
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Yes and Yes
     
    PeteC,
    #26
  8. 2003/07/19
    mflynn

    mflynn Inactive

    Joined:
    2002/08/14
    Messages:
    4,141
    Likes Received:
    9
    10-4 good

    Mike
     
    mflynn,
    #27
  9. 2003/07/25
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Well - the first response from Ahead was ...... mindboggling :D
    Either this is a brush off or they misread my query - needless to say I have set them straight on this.
     
    Last edited: 2003/07/25
    PeteC,
    #28
  10. 2003/07/25
    mflynn

    mflynn Inactive

    Joined:
    2002/08/14
    Messages:
    4,141
    Likes Received:
    9
    Hee hee!

    Mike
     
    mflynn,
    #29
  11. 2003/07/29
    PeteC

    PeteC SuperGeek Staff Thread Starter

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    It does't get any better !

    My response to Ahead :
    From Ahead:
    Clearly they do not understand the question. No chance of getting anywhere with this guy.
     
    PeteC,
    #30
  12. 2003/08/12
    Christer

    Christer Geek Member Staff

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Hi Pete!

    A bit late but anyway, a while back when I tried to install Norton Internet Security it failed. After some work I isolated InCD v.4010 as the cause. With an earlier version of InCD (v.35240) NIS installed just fine.

    It seems like a restore point or a new Ghost Image before the installation of anything Nero, well, anything at all, is adviseable.

    Regards,
    Christer
     
    Christer,
    #31
Page 2 of 2
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...