windows 7 keeps crashing

[damonjames]

Hi,

A newbie here. My tech knowledge is limited.

I have done a clean install of a win7 (purchased new) and it has been running now for about 2 weeks, but keeps crashing (blue screen).

Dunno what it is, but OMG i'm going NUTS trying to get it running stable. It has crashed during document writing, picture viewing, zip file creation... there seems no common thread.

I have searched and searched, but don't really know what to try. Will post any other information that may help.

I really want to nail this, WITHOUT having to buy a new computer if I can help it.

Any assistance will me much appreciated.

Regards, Damon.

 

[Wishmaster]

the problems just started recently, or always had the issue?
have you updated all your drivers to Win7 compatable?
What type/speed RAM are you running?

 

[richc46]

Here Follow the instructions given and you will be enjoying your new OS, soon.

How to Fix Internet Explorer Crashes | Technize.com

 

[damonjames]

Wishmaster,

1. Problems seem to have occurred ever since install. I installed the OS and then iolo antivirus, office and a few other apps. The system has been unstable since this time.

2. All drivers are updated using windows update (including optional updates).

3. Ram is 4.0 GB but I don't know how to find out what type.

Damon.

 

[GrandPaFred]

Wishmaster,

1. Problems seem to have occurred ever since install. I installed the OS and then iolo antivirus, office and a few other apps. The system has been unstable since this time.

2. All drivers are updated using windows update (including optional updates).

3. Ram is 4.0 GB but I don't know how to find out what type.

Damon.

According to Iolo's website that Antivirus program not for Windows 7
see info @

http://www.iolo.com/customercare/kbarticle.aspx?id=KBA-02130

 

[damonjames]

Sorry I should have been more explicit. I am running iolo system mechanic 9.5.3 which has iolo system shield (antivirus) attached to it. According to my own research and the table you found it's supported by win7.

Another thing I have found though...

win7 generated an error report: "blue screen error caused by a device or driver". However when I go to update drivers on windows update it says no important updates are available, and I have installed all optional updates as well.

There are 5 problems (ie blue screen shut downs) the error message applies to. Here is the info win7 has provided for 2 of them:

EVENT 1
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 3081
Extra information about the problem
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF8800396FBE8
BCP3: FFFFF8800396F440
BCP4: FFFFF880012CE88D
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Bucket ID: X64_0x24_Ntfs!NtfsCommonQueryInformation+9d
Server information: 969b8959-12c9-4032-86a2-6dfe3f49d3fb

EVENT 2

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 3081
Extra information about the problem
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF880081A7BE8
BCP3: FFFFF880081A7440
BCP4: FFFFF880012A988D
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Bucket ID: X64_0x24_Ntfs!NtfsCommonQueryInformation+9d
Server information: 9c9de211-2483-4dda-90c7-4bcf37acf346

 

[amirage]

Hi there...

Don't worry..we are in the same boat. My windows too crashes; it's been doing this 1 week after installation. All drivers are the latest and also so is Windows completely updated. I'm moved from ubuntu to Windows but now I think I made a grave mistake...Well back to Linux.

 

[usasma]

Driver's are necessarily fully updated when you visit:
- Windows Update
- Update drivers tool in Device Manager
- The manufacturer of the PC's website

The reason for this is that the drivers are written by the company who makes the device - not by the PC manufacturer or by Microsoft (which is where Windows Update checks).
So the challenge is to find out who makes the device (whether it's a driver from a device or a driver from a program). Then visit their website for the most updated version.

In this case you have a BCCode: 24 error. More information on that here: BSOD Index
What all that stuff says is that there's a problem with the file system on your hard drive. To attempt to fix it, try this:

CHKDSK /R:
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7; winlogon for XP).
Copy/paste the results into your next post.

Then, while waiting for the next BSOD, try this:

H/W Diagnostics:
Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Also, please provide us with the dump files so that we can perform a more thorough analysis:

Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
{Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

 

[damonjames]

Hi,

I did the chkdsk /r from an elevated command prompt but did not get a resulting log file entry under the source column in event viewer. I saw chkdsk running but here's the chkdsk table results - there is nothing for todays chkdsk operation

Information 24/12/09 7:52:55 Chkdsk 26213 None
Information 24/12/09 7:28:40 Chkdsk 26213 None
Information 31/12/09 10:39:36 Chkdsk 26214 None
Information 24/12/09 7:52:51 Chkdsk 26213 None
Information 24/12/09 7:28:24 Chkdsk 26213 None
Information 24/12/09 7:28:37 Chkdsk 26213 None
Information 24/12/09 7:52:39 Chkdsk 26213 None

Here is the results of one of the above:

C:\
CHKDSK is verifying files (stage 1 of 3)...
76800 file records processed. File verification completed.
49 large file records processed. 0 bad file records processed. 2 EA records processed. 41 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
106568 index entries processed. Index verification completed.
　
CHKDSK is verifying security descriptors (stage 3 of 3)...
76800 file SDs/SIDs processed. Cleaning up 218 unused index entries from index $SII of file 0x9.
Cleaning up 218 unused index entries from index $SDH of file 0x9.
Cleaning up 218 unused security descriptors.
Security descriptor verification completed.
14885 data files processed. CHKDSK is verifying Usn Journal...
33804376 USN bytes processed. Usn Journal verification completed.
The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
244187999 KB total disk space.
22871936 KB in 59116 files.
44200 KB in 14886 indexes.
183423 KB in use by the system.
65536 KB occupied by the log file.
221088440 KB available on disk.
4096 bytes in each allocation unit.
61046999 total allocation units on disk.
55272110 allocation units available on disk.

Also I am noticing the BSOD happens quite frequently when I move or resize (compress) zip files or pictures.

minidump folder attached.

 

[usasma]

The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
Windows found problems with the file system.

Please run CHKDSK /R /F as described above.
The log file is most likely located in the source column heading of Wininit (for Win7)(added to above post).

And, do the H/W Diagnostics listed above also. I suspect issues with the Hard Drive, so run that test first.

 

[damonjames]

chkdsk log

OK you were right I found it under wininit:

I will now run the diagnostic tools.

-System
-Provider[ Name] Microsoft-Windows-Wininit[ Guid] {206f6dea-d3c5-4d10-bc72-989f03c8b84b}[ EventSourceName] Wininit
-EventID1001[ Qualifiers] 16384
Version0Level4Task0Opcode0Keywords0x80000000000000-TimeCreated[ SystemTime] 2010-01-10T01:19:44.000000000Z
EventRecordID3000Correlation-Execution[ ProcessID] 0[ ThreadID] 0
ChannelApplicationComputerPCSecurity
-EventData
Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 79616 file records processed. File verification completed. 47 large file records processed. 0 bad file records processed. 2 EA records processed. 41 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 110214 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 79616 file SDs/SIDs processed. Cleaning up 20 unused index entries from index $SII of file 0x9. Cleaning up 20 unused index entries from index $SDH of file 0x9. Cleaning up 20 unused security descriptors. Security descriptor verification completed. 15300 data files processed. CHKDSK is verifying Usn Journal... 33744800 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 79600 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 53578837 free clusters processed. Free space verification is complete. Windows has checked the file system and found no problems. 244187999 KB total disk space. 29642436 KB in 63767 files. 43928 KB in 15301 indexes. 0 KB in bad sectors. 186287 KB in use by the system. 65536 KB occupied by the log file. 214315348 KB available on disk. 4096 bytes in each allocation unit. 61046999 total allocation units on disk. 53578837 allocation units available on disk. Internal Info: 00 37 01 00 e7 34 01 00 7c 5b 02 00 00 00 00 00 .7...4..|[...... fa 00 00 00 29 00 00 00 00 00 00 00 00 00 00 00 ....)........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.

 

[usasma]

Windows has checked the file system and found no problems.

So far, so good!

 

[damonjames]

Problem Fixed!!!!

Hi,

I bought a new computer.

Many thanks to usasma and others for contributing to this thread.

I just wasn't getting time enough to run the required diagnostics, nor would it have neccessarily made me confident enough in the OS to trust it to run my working life, without worying about what will happen next.

So still plagued by BSOD's and underconfident in the whole computer I copped out and threw the lot in the bin and bought a new one, which is now working fine with win64.

Once again, many thanks for your time and help in attempting to nail the problems with my old one, but I didn't feeel like wasting any more of mine and everybody else's time persisting with it.

Regards,

Damon James.

 

[usasma]

Thanks for letting us know!
It's your system and it's gotta do what you want it to do - so there's no problem with swapping it for a new one.
And that appears to have solved your problems also!
Good luck and thanks for the kind words!