Frequent BSOD

[rubbishbin]

Been having quite a few BSODs recently. Happens when i'm using my laptop halfway through or just booting up.

Need help in identifying the cause(s)!

Basic system info as follows:
Win 7 Pro x64
Original OS installed: Vista home premium
MSDN version
Laptop reaching 1 year old soon
Just reformatted at about 1 month ago

Attached is zip file as instructed.
Thanks in advanced!

 

[rubbishbin]

Hi guys, it just happened SEVERAL more time a while ago...can anybody help?

 

[CarlTR6]

I will take a look for you. Since you are having this problem during the booting process, I suspect you have a hardware problem.

You uploaded two dumps in your last upload; both are error code F4

Error code F4, CRITICAL_OBJECT_TERMINATION - BSOD Index

You most recent dump blames a hard drive. The other dumps points to memory corruption.

Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Sun Sep  5 03:20:26.047 2010 (GMT-4)
System Uptime: 0 days 1:13:25.014
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005ac1b30, fffffa8005ac1e10, fffff80002fd85d0}

Probably caused by : csrss.exe

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8005ac1b30, Terminating object
Arg3: fffffa8005ac1e10, Process image file name
Arg4: fffff80002fd85d0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8005ac1b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  fffff8800679fb38 -- (.exr 0xfffff8800679fb38)
ExceptionAddress: 0000000076cd592d
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000a20c88
Attempt to write to address 0000000000a20c88

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000a20c88

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f050e0
 0000000000a20c88 

FOLLOWUP_IP: 
+54fe952f01fede08
00000000`76cd592d ??              ???

FAULTING_IP: 
+54fe952f01fede08
00000000`76cd592d ??              ???

FAILED_INSTRUCTION_ADDRESS: 
+54fe952f01fede08
00000000`76cd592d ??              ???

BUGCHECK_STR:  0xF4_C0000005

STACK_TEXT:  
fffff880`0679f0b8 fffff800`03059652 : 00000000`000000f4 00000000`00000003 fffffa80`05ac1b30 fffffa80`05ac1e10 : nt!KeBugCheckEx
fffff880`0679f0c0 fffff800`030023e3 : ffffffff`ffffffff fffffa80`05e1a060 fffffa80`05ac1b30 fffffa80`05ac1b30 : nt!PspCatchCriticalBreak+0x92
fffff880`0679f100 fffff800`02f8a80c : ffffffff`ffffffff 00000000`00000001 fffffa80`05ac1b30 fffff6fb`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17946
fffff880`0679f150 fffff800`02ccc993 : fffffa80`05ac1b30 fffff800`c0000005 ffffef5f`c5c0291c fffffa80`05e1a060 : nt!NtTerminateProcess+0x20c
fffff880`0679f1d0 fffff800`02cc8f30 : fffff800`02d07dbc fffff880`0679fb38 fffff880`0679f8a0 fffff880`0679fbe0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0679f368 fffff800`02d07dbc : fffff880`0679fb38 fffff880`0679f8a0 fffff880`0679fbe0 00000000`00a21f10 : nt!KiServiceLinkage
fffff880`0679f370 fffff800`02cccd82 : fffff880`0679fb38 00000000`000116e4 fffff880`0679fbe0 00000000`00a219e8 : nt!KiDispatchException+0x53b
fffff880`0679fa00 fffff800`02ccb8fa : 00000000`00000001 00000000`000116e4 00000000`76de9001 00000000`76d0fcb8 : nt!KiExceptionDispatch+0xc2
fffff880`0679fbe0 00000000`76cd592d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00a20c90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76cd592d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

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

Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Tue Aug 31 06:31:15.066 2010 (GMT-4)
System Uptime: 0 days 2:05:28.033
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005ae94c0, fffffa8005ae97a0, fffff80002f905d0}

Probably caused by : hardware_disk

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8005ae94c0, Terminating object
Arg3: fffffa8005ae97a0, Process image file name
Arg4: fffff80002f905d0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8005ae94c0

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  fffff88006bc0b38 -- (.exr 0xfffff88006bc0b38)
ExceptionAddress: 00000000771651df
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 000007fefd0cd8a8
   Parameter[2]: 00000000c000000e
Inpage operation failed at 000007fefd0cd8a8, due to I/O error 00000000c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000007fefd0cd8a8

EXCEPTION_PARAMETER3:  00000000c000000e

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR:  0xc0000006_c000000e

FAULTING_IP: 
+23a
00000000`771651df ??              ???

BUGCHECK_STR:  0xF4_IOERR_C000000E

FOLLOWUP_IP: 
+54fe952f01a8df10
000007fe`fd0cd8a8 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

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

I suggest you begin by uninstalling Kaspersky using this uninstall tool: Info > Tool. Download and install Microsoft Security Essentials in ts place and make sure Windows Firewall is turned on. Kaspersky is known to cause BSODs on some Win 7 systems. Reboot and run your system. After you get your system stable, you can try Kaspersky again; but I do not recommend doing so.

I find two older drivers on your system.

bcmwl664.sys Tue Jul 07 20:45:04 2009 - This is a Broadcom wireless driver. Read this thread: Broadcom Wireless Win64bit BSOD bcmwl664.sys Fix - RRTech...The SOURCE for Extreme Liquid Cooling It will give you a link to a driver update.

SCDEmu.SYS Sun Mar 15 06:30:00 2009 - Update this driver to one dated July13, 2009 or later. If there is not an updated driver available, uninstall the software.

After you uninstall Kapsersky and update the above drivers, reeboot and run your system. Let's see if you are still getting BSOD's. If you get one, upload it to us and we will take next steps. Either way, let us know how your system is doing.

Our next steps will be to test your RAM and your hard drive.

 

[rubbishbin]

thanks for the suggestions... I'll do them once i reach home later.

My laptop warranty is ending soon hopefully a hardware problem can be spotted b4 it ends

 

[rubbishbin]

Have done all of the above.

Removed KIS and replaced it with MSE.
Updated the Broadcom driver and removed the program associated with SCDEmu.sys

The thing strange about my system is that sometimes it can run an mmorpg for hours, only to crash several times while doing close to nothing or just booting up.

Will keep watch on my system and hope any crashes come sooner rather than later.

 

[rubbishbin]

This is bad. It just crashed moments ago, what do I do next?

 

[CarlTR6]

If your laptop is under warranty, I would let the shop techs take a look at it. This appears to be a hardware issue. Both dumps are showing error code F4, CRITICAL_OBJECT_TERMINATION. The most recent dump blames the hard drive and points to an I/O error. The next latest dump shows c0000005, memory corruption.

You can test your hard drive using one of the programs shown in this link. Read the information thoroughly. HD Diagnostic. You can also run chkdsk.

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
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 Windows 7) (winlogon for XP).

Copy/paste your results into your next post.

You can test your RAM following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Let us know the results of Memtest.

I still recommend that while you are under warranty, you have your machine checked by a tech. You can give him/her the information from the these tests and tell them what you have done so far.

 

[rubbishbin]

Did a CHKDSK, have not done the Memtest yet, the results are as follow. Gonna send my laptop to the service centre on thursday.

Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows 7.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  103936 file records processed.                                          File verification completed.
  512 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  143240 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  103936 file SDs/SIDs processed.                                         Cleaning up 16 unused index entries from index $SII of file 0x9.
Cleaning up 16 unused index entries from index $SDH of file 0x9.
Cleaning up 16 unused security descriptors.
Security descriptor verification completed.
  19653 data files processed.                                            CHKDSK is verifying Usn Journal...
  36950928 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  103920 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  4046665 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

  41946111 KB total disk space.
  25565384 KB in 76077 files.
     49172 KB in 19654 indexes.
         0 KB in bad sectors.
    144895 KB in use by the system.
      2048 KB occupied by the log file.
  16186660 KB available on disk.

      4096 bytes in each allocation unit.
  10486527 total allocation units on disk.
   4046665 allocation units available on disk.

Internal Info:
00 96 01 00 fe 75 01 00 67 c6 02 00 00 00 00 00  .....u..g.......
5a 03 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  Z...,...........
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.


Chkdsk was executed in read/write mode.  

Checking file system on X:
The type of the file system is NTFS.
Volume label is Windows XP.

CHKDSK is verifying files (stage 1 of 5)...
  15520 file records processed.                                          File verification completed.
  14 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              2 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  18334 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  15520 file SDs/SIDs processed.                                         Cleaning up 46 unused index entries from index $SII of file 0x9.
Cleaning up 46 unused index entries from index $SDH of file 0x9.
Cleaning up 46 unused security descriptors.
Security descriptor verification completed.
  1408 data files processed.                                            CHKDSK is verifying Usn Journal...
  682792 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  15504 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  191700 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

   3145727 KB total disk space.
   2340504 KB in 14071 files.
      3788 KB in 1409 indexes.
         0 KB in bad sectors.
     34635 KB in use by the system.
     17792 KB occupied by the log file.
    766800 KB available on disk.

      4096 bytes in each allocation unit.
    786431 total allocation units on disk.
    191700 allocation units available on disk.



Checking file system on D:
The type of the file system is NTFS.
Volume label is Program Files and Data.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  80128 file records processed.                                          File verification completed.
  21 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              0 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  90226 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  80128 file SDs/SIDs processed.                                         Cleaning up 27 unused index entries from index $SII of file 0x9.
Cleaning up 27 unused index entries from index $SDH of file 0x9.
Cleaning up 27 unused security descriptors.
Security descriptor verification completed.
  5050 data files processed.                                            CHKDSK is verifying Usn Journal...
  1169224 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x131484b000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x131485b000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x1314865000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x1314866000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x1314866000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x1314867000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x1314869000 for 0x1000 bytes.
Windows replaced bad clusters in file 70987
of name \DOWNLO~1\Comic ZO\COMICZ~1.17\COA8B3~1.JPG.
  80112 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  48110930 free clusters processed.                                         Free space verification is complete.
Adding 3 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 267474943 KB total disk space.
  74844832 KB in 73927 files.
     30968 KB in 5051 indexes.
        12 KB in bad sectors.
    155407 KB in use by the system.
     65536 KB occupied by the log file.
 192443724 KB available on disk.

      4096 bytes in each allocation unit.
  66868735 total allocation units on disk.
  48110931 allocation units available on disk.

Internal Info:
00 39 01 00 8e 34 01 00 c9 2d 02 00 00 00 00 00  .9...4...-......
6b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  k...............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Looks like there's some problem in my D drive.

 

[CarlTR6]

Obviously D: had some problems. If this a new computer, that should not be the case. A few bad clusters is not unusual; but that can be an indication that the drive is beginning to fail. I agree with sending it to the service center while it is still under warranty. If it were not under warranty, I would suggest that you use the hard drive manufacturer's diagnostic tool for a further check.

Thanks for posting your test results and for telling us what you are going to do. If you decide to run Memtest, please tell us those results. Any errors will show on your screen in red. Let us know what the service center finds and does. Good luck!

 

[rubbishbin]

Hi!

Just did a memtest for 7 passes...took 8 hrs

All passed without any errors. Is is safe to assume that there is no problem with my RAM?

 

[CarlTR6]

That is a pretty good indication your RAM is fine. It is not always conclusive; but it is safe to say that the RAM is OK. Any more BSOD's?

 

[rubbishbin]

No more BSOD's until since I last ran chkdsk, but can't really say much because I haven't been using the system a lot since then.

Bringing it down to service center tomorrow, should I insist on a replacement drive?

 

[rubbishbin]

Hi, an update.

HP have replaced my old fujitsu hard disk to a WDC (is it western digital) and I have restored all my files using Macrium Reflect.

Did a chkdsk and got the same result as my old hard disk

anything wrong there?

Checking file system on D:
The type of the file system is NTFS.
Volume label is Program Files and Data.


A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 3)...
  80128 file records processed.                                          File verification completed.
  21 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              0 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
  90240 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 3)...
  80128 file SDs/SIDs processed.                                         Security descriptor verification completed.
  5057 data files processed.                                            CHKDSK is verifying Usn Journal...
  1261360 USN bytes processed.                                             Usn Journal verification completed.
Windows has checked the file system and found no problems.

 267473919 KB total disk space.
  74906692 KB in 73957 files.
     30988 KB in 5058 indexes.
        12 KB in bad sectors.
    155663 KB in use by the system.
     65536 KB occupied by the log file.
 192380564 KB available on disk.

      4096 bytes in each allocation unit.
  66868479 total allocation units on disk.
  48095141 allocation units available on disk.

Internal Info:
00 39 01 00 b3 34 01 00 fc 2d 02 00 00 00 00 00  .9...4...-......
6b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  k...............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

 

[CarlTR6]

A few bad sectors on a new drive is not unheard of. I don't see any errors in the report. Is it possible because you restored an image that the bad sectors were in that image? I don't know the answer to that; I am not an expert in this area by any stretch of the imagination. I am just thinking "out loud". Anyway, congratulations on the new hard drive. If your old was failing, you have solved that problem and that is good.

Have you had any further BSOD's?

 

[rubbishbin]

Been running for more than 6 hours without further BSOD.

+1 rep for u

 

[CarlTR6]

Thank you for the rep. That was very thoughtful of you. If you get another BSOD, please upload it. If you don't, post back in a couple of days and let us know. We can then ask the moderators to mark this thread as solved. Fingers crossed!

 

[rubbishbin]

An update: Its been almost a week since I got my laptop bag.

I have not encountered anymore BSODs

This thread can be closed already, thanks a lot CarlTR6

 

[CarlTR6]

Thank you for the great update and for reporting back! And you are very welcome; I am glad we could help. Happy computing!