dwsolo
Newbie

Posts: 31
|
 |
« on: June 18, 2010, 10:04:50 PM » |
|
Hi Mr Ticker :-) My Win 7 64-bit home premium computer with 2 internal disks (250 MB system disk C: and 2 TB storage disk D: now half full ) and one (2 TB) expansion disk (P: now three quarters full) seems to behave OK most of the time, but it has a couple of peculiarities which I cannot get to the bottom of - and they may be related. The first peculiarity is occasional BSODs. I always run checkdisk after these and often no problems are found - the usual problems, when they do get detected, relate to free spaces allocated as if they had files in them. I have run various solutions including "reimage" but the basic BSOD problems tend to return after a while, usually once or twice a month. The second peculiarity is that although Windows sees the D and P drives as NTFS and I have no problem copying deleting defragging etc, when I run Easeus Todo to back up the iamge of the system disk, Easeus reports D and P as unformatted. Again, the Easeus file is created on the D or P drive with no difficulty but the fact that Easeus thinks they are unformatted worries me somewhat. (BTW I have run the "reimage" programme several times, with varying and temporary success, but that relates only to the system drive and doesn't pick up on potential failures in the D and P drives). (BTW I also use the search programme "everything.exe" (a very handy file finder), and this programme occasionally reports problems with the D and P drives, even though Windows seems quite happy, so I run checkdisk each time that happens too.) Any ideas? Do I need to reformat my D and P drives? Kind regards David
|
|
|
|
|
Logged
|
|
|
|
|
|
|
MrTicker
|
 |
« Reply #1 on: June 19, 2010, 12:36:44 AM » |
|
Hi David,
In order for us to help you further it would be helpful if you could let us know more precisely what the occasional BSOD Error is that you are getting, plus other relevant information regarding your system.
Are the BSOD's the same each time or different?
When did this problem begin? Before or after you added/changed the drives?
Have you tried running the system without either of these TB drives? If so do you get the same result or not?
Are all your drivers up to date?
Get back to us with this info and we can help you further.
Cheers,HTH,
ticker
|
|
|
|
|
Logged
|
|
|
|
dwsolo
Newbie

Posts: 31
|
 |
« Reply #2 on: June 19, 2010, 02:37:09 AM » |
|
Hi, thanks. Well it's not possible for me to say whether the BSODs are the same or not, because I never have time to note down what it says. Are the reports stored somewhere? If so I might be able to post copies here. The first BSOD I got was within the first week of buying the computer and a complete reinstall of Windows 7 seemed to sort it out for a couple of months. The TB drives have always been connected. I'm not sure how I would disconnect the D drive, which is internal, since I am afraid that by going inside the computer I might disconnect the wrong drive and even if I disconnect the correct one, I'm not sure whether that would prevent bootup, since the system is presumably expecting two internal drives? Would that cause a disaster? Perhaps you can advise on this point? (I can of course take the P drive offline if necessary since it's USB, and then simply reconnect for image backups)
I think my drivers are up to date, but it's not clear: - "Driver agent" reports that new drivers are available for many devices but when I download the drivers from their site and unbundle them, the devices area of my computer reports (when I click update driver and direct them to the newly unbundled drivers that I donwloaded) that there is no need to update the driver. This happens every single time and for every single device which "driver agent" complains about, so I don't understand this and I've asked them to clarify (no reply as yet).
That's all the info I have at the moment (unless you have further questions to narrow the problem down). Perhaps I'll try running on the C drive alone for a while and report back after a month or so, but, before I do that I need to be sure that I don't make a mess of things by going into the computer and physically disconnecting the D drive, so please advise on that. Thanks.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
MrTicker
|
 |
« Reply #3 on: June 20, 2010, 01:59:17 PM » |
|
Hi There The main problem that you have got at the moment is the BSOD that you keep getting, so we need to address that one first. When Windows crashes, mini dump files containing all the information relating to the crash are created and stored on your system. However, they will not be created if the system is not set up to do so and neither will you see the BSOD on your screen in the event of a crash. To correct this, go to this Forum link: http://www.briteccomputers.co.uk/forum/tutorials-and-how-to/more-help-with-bsod/ , follow the steps in blue type that starts with "Start>Right click...." etc. Further down the same page, in the paragraph just above the fourth screenshot, you will find a link for the BlueScreenView application, which is a very useful app for viewing the mini dump files. Download it; it needs no installation as it runs directly from the .EXE. Do both of these and let us know the results of the BSOD when it happens again, i.e. the full BSOD error message that you can view with BlueScreenView app, or a screenshot of it if you can. Cheers,HTH, ticker P.S. I am curious to know why a reinstall of Win 7 was needed in the first week and also what Make, Model of PC do you have?
|
|
|
|
|
Logged
|
|
|
|
dwsolo
Newbie

Posts: 31
|
 |
« Reply #4 on: June 21, 2010, 02:22:16 AM » |
|
Hi Mr Ticker It seems that the system is already configured to retain dmp files. The BSOD viewer has picked up all the dmp files since February, with interesting results. They mostly relate to "memory management" but not every time. Should I email you the html exports from these or should I (somehow?) post relevant info into this thread? I can also send you the setup info (specifications) of the computer as ordered from PCSpecialist.com if you think it will help.
PS these are the address in stack data for the last three events ntoskrnl.exe+e3ede nvlddmkm.sys+20b8cb
ntfs.sys+96ac ntoskrnl.exe+36b5a4
fltmgr.sys+2160 ntfs.sys+1e95 Kind regards David
|
|
|
|
« Last Edit: June 21, 2010, 02:43:26 AM by dwsolo »
|
Logged
|
|
|
|
|
Britec
|
 |
« Reply #5 on: June 21, 2010, 02:51:18 AM » |
|
Hi Run some tests on your memory with this free software just burn the ISO to cd Memtest86+http://www.memtest.org/
|
|
|
|
|
Logged
|
|
|
|
dwsolo
Newbie

Posts: 31
|
 |
« Reply #6 on: June 21, 2010, 06:24:44 AM » |
|
memtest revealed no errors (I can send you a photo of the final screen if required)
|
|
|
|
|
Logged
|
|
|
|
|
MrTicker
|
 |
« Reply #7 on: June 21, 2010, 07:12:01 AM » |
|
Hi there,
Yes, that would be helpful, thanks.
Cheers,
ticker
|
|
|
|
|
Logged
|
|
|
|
|
Britec
|
 |
« Reply #8 on: June 21, 2010, 08:31:37 AM » |
|
if possible can you zip up your bsod dump files so we can take a look and the errors?
|
|
|
|
|
Logged
|
|
|
|
dwsolo
Newbie

Posts: 31
|
 |
« Reply #9 on: June 21, 2010, 12:53:08 PM » |
|
How do I get the zip files to you? Should I send to an email address? Perhaps you could email me at dwsolo@gmail.com(that is an email I use for public consumption in order to prevent spambots from harvesting my main address)
|
|
|
|
|
Logged
|
|
|
|
|
Britec
|
 |
« Reply #10 on: June 21, 2010, 01:48:16 PM » |
|
|
|
|
|
|
Logged
|
|
|
|
|
|
|
Britec
|
 |
« Reply #12 on: June 22, 2010, 07:05:15 AM » |
|
21/06/2010 nvlddmkm.sys is to do with Nvidia maybe you go issues with your graphics drivers 19/06/2010 NTFS_FILE_SYSTEM First try this: 1. Open Explorer or My Computer (Press Windows+E). 2. In the right pane, right-click on the drive you want to validate and select Properties. 3. Select the Tools tab. 4. Under Error-checking, click on " Check Now". 5. In the next dialog, make sure the option " Automatically fix file system errors" is checked. If you want a more complete validation and repair check the option " Scan for and attempt recovery of bad sectors" (although this takes considerably longer to complete). If that dont work try this: 1. cd \windows\system32\drivers ren ntfs.sys ntfs.oldThis basically renames the current ntfs.sys file to something else so that we can replace it with a new one that hopefully is not corrupted. Now type in the following command: 2. copy cd:\i386\ntfs.sys drive:\windows\system32\drivers
|
|
|
|
« Last Edit: June 22, 2010, 07:15:08 AM by Britec »
|
Logged
|
|
|
|
dwsolo
Newbie

Posts: 31
|
 |
« Reply #13 on: June 22, 2010, 09:09:42 AM » |
|
I'm afraid I don't understand the instructions after "if that dont work" Am I supposed to put a CD in the CD drive? If so which CD? or does the "cd" mean "change directory" - if so, where do I type such instructions? I tried copying it in the "search programs and files" box, but nothing came up
|
|
|
|
|
Logged
|
|
|
|
|
Britec
|
 |
« Reply #14 on: June 22, 2010, 03:18:21 PM » |
|
Sorry i always think people know already... so yeah your need a windows cd then go to command prompt and then follow commands
|
|
|
|
|
Logged
|
|
|
|
|