Tech Support Guy banner
Status
Not open for further replies.

BSOD problem

Solved 
5K views 79 replies 2 participants last post by  Macboatmaster 
#1 ·
Reinstalled windows 7 a few weeks ago after computer was giving trouble. I've been encountering bsods for the last two weeks. I attached minidumps
 

Attachments

#2 ·
If it is the same computer as here
https://forums.techguy.org/threads/bsod-unexpected-shutdown-error.1141619/

and the ram was not replaced, then therein lies the problem
Did you get someone to deal with the ram issue
Ok. I might need to get some help checking the ram sticks from someone. (Don't even know where they are lol) But I should be ok. I'll report back once that's all done. Thanks again!
You ran memtest and it reported errors
If ram has not been replaced or checks made to establish if it is the stick or the slot - that is what you need to do
 
#4 ·
send me please a copy and paste of this
http://static.techguy.org/download/SysInfo.exe

clean boot it and see if you still get BSOD`s
Windows 7 and Windows Vista
  1. Log on to the computer by using an account that has administrator rights.
  2. Click Start, type msconfig.exe in the Start Search box, and then press Enter to start the System Configuration utility.
    Note If you are prompted for an administrator password or for confirmation, you should type the password or provide confirmation.
  3. On the General tab, click the Selective startup option, and then click to clear the Load startup items check box. (The Use Original Boot.ini check box is unavailable.)
  4. On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all.

    Note This step lets Microsoft services continue to run. These services include Networking, Plug and Play, Event Logging, Error Reporting, and other services. If you disable these services, you may permanently delete all restore points. Do not do this if you want to use the System Restore utility together with existing restore points.
  5. Click OK, and then click Restart.
In the meantime I will analyse the dump
 
#5 ·
I have had a look at the dumps when you reply with the spec and the results of the clean boot I will advise further
 
#6 ·
Tech Support Guy System Info Utility version 1.0.0.2
OS Version: Microsoft Windows 7 Home Premium, Service Pack 1, 32 bit
Processor: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz, x64 Family 6 Model 37 Stepping 2
Processor Count: 4
RAM: 1948 Mb
Graphics Card: Intel(R) HD Graphics, 750 Mb
Hard Drives: C: Total - 953867 MB, Free - 873327 MB;
Motherboard: ASUSTeK Computer INC., P7H55-M
Antivirus: Microsoft Security Essentials, Updated and Enabled

Thank you. I'm currently running a hard drive scan which will take all night. The 5 bsods in the minidumps have happened over a period of about 2 weeks. Should I just let the computer run in clean boot all day?
 
#7 ·
do you mean a chkdsk /r
having seen the above info and the dumps
there is another possible cause, when you have completed the chkdsk /r and got the results from event viewer to establish that the cause is not bad sectors, as one of the dumps suggests that it maybe, then we will proceed

If it is a disc problem I may have expected you to have received messages that one of the discs needed to be checked and having set the dirty bit I would have expected windows to run autochk which is chkdsk on boot - have you received such messages

If you wish to continue with my help please do not run any other analysis or suggested solutions until I so advise or agree them

My troubleshooting of BSOD methods require a step by step approach

post the results of the chkdsk please
 
#8 ·
I was/am running HD tune error scan. It's picked up some damaged sections. I ran check disk without error correction or recovery of sectors and it said everything was fine. I'm going to run it again with correction and recovery later and see if it fixes anything. Not sure where the checkdisk dump file is though...
 
#9 ·
Go windows button
type
cmd
when it appears above
right click and click run as admin

at the prompt
type
chkdsk /r

press enter
agree message to run on restart by typing
Y
and do so

If first message is dismount must be etc do you wish to force
type
N
then next message will be on restart

when completed and computer has rebooted
control panel
admin tools
event viewer
windows logs left pane
application log
when it loads
find right pane
type
wininit
click find next
check that what it finds is the chkdsk log

open it
click copy button bottom left corner - as text to clipboard
and paste to reply

PLEASE confirm as asked if you have had autochk messages
If it is a disc problem I may have expected you to have received messages that one of the discs needed to be checked and having set the dirty bit I would have expected windows to run autochk which is chkdsk on boot - have you received such messages
 
#10 ·
The danger of the processes you have followed with the original chkdsk which was no use as without error checking the results are unreliable and now the HDTune is that you risk pushing that disk over the edge - if it does have bad sectors - and if a bad sector develops in the MFT or the BCD there is a chance windows will not load

Just the ONE chkdsk /r would have been a better approach.
However no point in worrying now
 
#13 ·
L22
I am signing off in about 30 mins or so
I will tell you before I do sdo

Please tell me when you leave it for the night

The dump that suggests it MAYBE a drive problem is
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.19045.x86fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0x82c12000 PsLoadedModuleList = 0x82d5de30
Debug session time: Tue Nov 24 15:26:34.439 2015 (UTC - 5:00)
System Uptime: 0 days 0:25:37.501

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.

If the error status is 0xC000009A, then it means the request failed because
a file system failed to make forward progress.
Arguments:
Arg1: c04902f8, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000009c, error status (normally i/o status code)
Arg3: 3e53f820, current process (virtual address for lock type 3, or PTE)
Arg4: 9205f056, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000009c

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 0

TRAP_FRAME: 94cbb8f4 -- (.trap 0xffffffff94cbb8f4)
ErrCode = 00000000
eax=9205f054 ebx=94cbb9b8 ecx=82e5ff93 edx=8de4e9c8 esi=8de4e9c8 edi=9205efdc
eip=82e9b187 esp=94cbb968 ebp=94cbb970 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!CmpDoCompareKeyName+0x17:
82e9b187 f6400220 test byte ptr [eax+2],20h ds:0023:9205f056=20
Resetting default scope

LAST_CONTROL_TRANSFER: from 82cb6068 to 82cf1b84

STACK_TEXT:
94cbb75c 82cb6068 0000007a c04902f8 c000009c nt!KeBugCheckEx+0x1e
94cbb7cc 82cb994a 94cbb820 82d7f280 94cbb840 nt!MiWaitForInPageComplete+0x302
94cbb85c 82ca2cc8 82d7f280 9205f056 87b11c18 nt!MiIssueHardFault+0x3b3
94cbb8dc 82c52be8 00000000 9205f056 00000000 nt!MmAccessFault+0x29fc
94cbb8dc 82e9b187 00000000 9205f056 00000000 nt!KiTrap0E+0xdc
94cbb970 82e9b342 94cbb9f0 0053a050 8de4e9c8 nt!CmpDoCompareKeyName+0x17
94cbb98c 82e9b286 8de4e9c8 94cbb9f0 00000000 nt!CmpFindSubKeyByHashWithStatus+0x40
94cbb9c0 82e440d1 94cbb9f0 94cbba64 94cbbc18 nt!CmpFindSubKeyByNameWithStatus+0x9e
94cbbb48 82e3b3d2 cb34f030 84c18550 87d08008 nt!CmpParseKey+0x938
94cbbbc4 82e4b90d 00000160 94cbbc18 00000040 nt!ObpLookupObjectName+0x510
94cbbc20 82e49852 0061e7ac 84c18550 b17a3701 nt!ObOpenObjectByName+0x165
94cbbd00 82e2631c 0061e8b4 00020019 0061e7ac nt!CmOpenKey+0x1f4
94cbbd1c 82c4fa06 0061e8b4 00020019 0061e7ac nt!NtOpenKeyEx+0x18
94cbbd1c 77ce71b4 0061e8b4 00020019 0061e7ac nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0061e7ec 00000000 00000000 00000000 00000000 0x77ce71b4

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiWaitForInPageComplete+302
82cb6068 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiWaitForInPageComplete+302

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 56257f54

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x7a_c000009c_nt!MiWaitForInPageComplete+302

BUCKET_ID: 0x7a_c000009c_nt!MiWaitForInPageComplete+302

Therefore as explained here
Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.

If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /r on the system partition. You must restart the computer before the disk scan begins.

Which is why I asked if you have the autochk error messages stating one of your discs needs to be checked

HOWEVER it is important not to jump to conclusions as I see other possible causes on the dumps
 
#14 ·
I will wait for the chkdsk /r report
If I go before completion post it and I will check before I leave home tomorrow about 1000
Normally I am online from about 1800

as I said please do not run other possible checks and solutions
IF that chkdsk reveals bad sectors
BACK UP all you need and then I will advise when I return
 
#16 ·
You are welcome pleased to help
 
#17 ·
I have gone
Goodnight
Post chkdsk results
and I will read tomorrow am
and post
then see you about 1800 UK if convenient to you
 
#20 ·
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 2015/11/26 06:54:31 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: L22-PC
Description:

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)...
351744 file records processed.

File verification completed.
889 large file records processed.

0 bad file records processed.

0 EA records processed.

94 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
430936 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
351744 file SDs/SIDs processed.

Cleaning up 2062 unused index entries from index $SII of file 0x9.
Cleaning up 2062 unused index entries from index $SDH of file 0x9.
Cleaning up 2062 unused security descriptors.
Security descriptor verification completed.
39597 data files processed.

CHKDSK is verifying Usn Journal...
36125008 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x78d1fa8000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x78d1fb5000 for 0x1000 bytes.
Windows replaced bad clusters in file 168848
of name \Windows\System32\config\software.
351728 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
223579285 free clusters processed.

Free space verification is complete.
Adding 268 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

976760000 KB total disk space.
81785452 KB in 237839 files.
170928 KB in 39598 indexes.
1072 KB in bad sectors.
486472 KB in use by the system.
65536 KB occupied by the log file.
894316076 KB available on disk.

4096 bytes in each allocation unit.
244190000 total allocation units on disk.
223579019 allocation units available on disk.

Internal Info:
00 5e 05 00 c9 3b 04 00 26 39 08 00 00 00 00 00 .^...;..&9......
64 07 00 00 5e 00 00 00 00 00 00 00 00 00 00 00 d...^...........
48 5c 23 00 50 01 21 00 00 1a 21 00 00 00 21 00 H\#.P.!...!...!.

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-11-26T04:54:31.000000000Z" />
<EventRecordID>3805</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>L22-PC</Computer>
<Security />
</System>
<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)...
351744 file records processed.

File verification completed.
889 large file records processed.

0 bad file records processed.

0 EA records processed.

94 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
430936 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
351744 file SDs/SIDs processed.

Cleaning up 2062 unused index entries from index $SII of file 0x9.
Cleaning up 2062 unused index entries from index $SDH of file 0x9.
Cleaning up 2062 unused security descriptors.
Security descriptor verification completed.
39597 data files processed.

CHKDSK is verifying Usn Journal...
36125008 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x78d1fa8000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x78d1fb5000 for 0x1000 bytes.
Windows replaced bad clusters in file 168848
of name \Windows\System32\config\software.
351728 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
223579285 free clusters processed.

Free space verification is complete.
Adding 268 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

976760000 KB total disk space.
81785452 KB in 237839 files.
170928 KB in 39598 indexes.
1072 KB in bad sectors.
486472 KB in use by the system.
65536 KB occupied by the log file.
894316076 KB available on disk.

4096 bytes in each allocation unit.
244190000 total allocation units on disk.
223579019 allocation units available on disk.

Internal Info:
00 5e 05 00 c9 3b 04 00 26 39 08 00 00 00 00 00 .^...;..&9......
64 07 00 00 5e 00 00 00 00 00 00 00 00 00 00 00 d...^...........
48 5c 23 00 50 01 21 00 00 1a 21 00 00 00 21 00 H\#.P.!...!...!.

Windows has finished checking your disk.
Please wait while your computer restarts.

</EventData>
</Event>
 
#21 ·
Well as I suspected and I am sure you did as well, the drive is failing
You can see the read errors
Read failure with status 0xc000009c at offset 0x78d1fa8000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x78d1fb5000 for 0x1000 bytes.
Windows replaced bad clusters in file 168848
of name \Windows\System32\config\software.
and then the added bad clusters
Adding 268 bad clusters to the Bad Clusters File.
with now
1072 KB in bad sectors
so you have approx. ONE MB of bad clusters 1000KB = 1MB

The reason for the problems is of course the read failures as when the system was accessing that Windows\System32\config\software, it could not determine the data and as you know a vital part of the OS file structure

YOUR urgent job is to back up everything of importance to an external source, preferably an external hard drive or if you do not have such a flash pen and then copy to another computer.

Then you NEED a new hard drive to replace this one and then we will attempt a clone to the new drive so that you are back as you are now.

As I said online about 18 to 1900hrs

Please do NOT think this chkdsk has fixed it - all it as done is to copy data from the bad sectors and rewrite it to good sectors, marking the original sectors as bad to stop data being written to them. it has NOT mended anything and the disc will continue to fail. When it fails completely is an unknown quantity.
 
#22 ·
Further to the above, there are three main reasons why that hard disk has bad sectors
1. It has simply developed the fault just like any other component may fail
2. It has had a knock or jolt whilst the drive is running - more likely of course on laptops rather than desktops
3. Overheat - caused by either overclocking or a poor air flow caused by the computer being run in an enclosed space - dust filled case dirty fan blades

The reason I mention this is because of the apparent failed ram on the topic earlier this year
When taking the two together you have either simply drawn the short straw or you have a problem somewhere with temps
Excess heat can damage ram
OC by the very nature of it can also damage ram
Excess heat MAY be the cause of the hard drive problem
 
#24 ·
Sorry do not know what you mean by
I will have to problem solve this issue
if you want my help as I outlined in post 21
YOUR urgent job is to back up everything of importance to an external source, preferably an external hard drive or if you do not have such a flash pen and then copy to another computer.

Then you NEED a new hard drive to replace this one and then we will attempt a clone to the new drive so that you are back as you are now.
I will be ready to advise
 
#25 ·
- I meant figure out why the drive and ram stopped working. Like whether it's overheating, etc.

- The computer was blue screening,etc before so I burned what i wanted onto cds. Then I reinstalled windows but it was doing it again. Hence I came to you.
 
#26 ·
Good luck with it
replace that drive ASAP
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top