Crucial 128gb M4 Bluescreen of death

(update) Dump file at post #10

I have just fresh installed win764bit on my new SSD Crucial M4 128gb (newest firmware 309)

I've had 4 Bsod in the last 7 hours since i've been installing software drivers.., the last bsod was when cystalDM3 was finishing off the read n writes for a benchmark test...
.the others were random.
I've just ran the test again after reboot and it worked..the last bsod was pretty random too i guess.

I transferred 30gb of files from my second 7200rpm HDD (in ultra bay of T500) to my SSD. The transfer speed was 60mb/s it took 12mins...is that ok?

Anyway what can be wrong with it? It's brand new SSD...

Here's the results. i also have the dump files...if anyone knows how to view em





Thanks

 

A better bench tool for diagnostic would be AS SSD.

Post 1 AS SSD and 1 crystal disk info would be ideal

 

Did you so happen to write down the BSOD codes? It would help in diagnosing them. You can also download BSOD reader and see what BSOD codes you were getting.

 

I tried AS SSD, first time it gave me a bsod towards the end of the process (acc.time), just like before!!
Anyway i tried it again and it worked flawless.. and got the results.

 

I wish I had any general idea about how to read the BSOD info, but did you try the LPM fix?

 

your not the only one on this forum that doesn't know..awfully quiet it seems....??

Whats the LPM?

 

Only Microsoft has the source code to know which line the ntkernel module crashed

 

LPM = Link Power Management
Solution: C300 Disk Freeze-ups in Windows 7 solved... - Crucial Community

Under certain conditions the default settings in W7 *may* cause BSODs with certain drives (SSDs, HDDs, or Optical Drives). Saw this happen with my hard drive RAID1 array before I applied to registry fix.

 

Zip and upload your dump files from C:\Windows\Minidump and I'll analyze them for you.

 

thanks for the info i'll read up on c300,
actually it hasn't crashed since 7th april... but i haven't ran the benchmark test to see if it triggers the bsod again...out of fear.

very appreciated that you take the time to read these dumps.

minidumps.rar - 4shared.com - online file sharing and storage - download

Thanks alot!

 

I just downloaded the files but I'm at work right now so I'll post back after I've had a chance to go over them at home.

 

oops happened again today.. i was loading samples into a software called kontakt via ram and got a freeze and bluescreen see below

new dump 041412-15054-01.dmp - 4shared.com - online file sharing and storage - download

 

All of your BSOD's were caused either by wininit.exe or csrss.exe, both of which are system files necessary for Windows to run.

Spoiler

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008b68b30, fffffa8008b68e10, fffff80002dd18b0}

Probably caused by : wininit.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: fffffa8008b68b30, Terminating object
Arg3: fffffa8008b68e10, Process image file name
Arg4: fffff80002dd18b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8008b68b30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME:  wininit.exe

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

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT: 
fffff880`077d00a8 fffff800`02e585e2 : 00000000`000000f4 00000000`00000003 fffffa80`08b68b30 fffffa80`08b68e10 : nt!KeBugCheckEx
fffff880`077d00b0 fffff800`02e0599b : ffffffff`ffffffff fffffa80`091148d0 fffffa80`08b68b30 fffffa80`08b68b30 : nt!PspCatchCriticalBreak+0x92
fffff880`077d00f0 fffff800`02d85448 : ffffffff`ffffffff 00000000`00000001 fffffa80`08b68b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`077d0140 fffff800`02acced3 : fffffa80`08b68b30 fffff800`c0000005 fffffa80`091148d0 00000000`02670730 : nt!NtTerminateProcess+0xf4
fffff880`077d01c0 fffff800`02ac9470 : fffff800`02b1967f fffff880`077d0b38 fffff880`077d0890 fffff880`077d0be0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`077d0358 fffff800`02b1967f : fffff880`077d0b38 fffff880`077d0890 fffff880`077d0be0 00000000`ff8bb4d8 : nt!KiServiceLinkage
fffff880`077d0360 fffff800`02acd2c2 : fffff880`077d0b38 00000000`026f0000 fffff880`077d0be0 00000000`ff8bfb88 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`077d0a00 fffff800`02acbe3a : 00000000`00000001 00000000`02670ce8 00000000`02673301 00000000`026f0000 : nt!KiExceptionDispatch+0xc2
fffff880`077d0be0 00000000`776f8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02670cf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776f8e3d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe

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

Spoiler

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008983830, fffffa8008983b10, fffff80002b948b0}

Probably caused by : csrss.exe

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: fffffa8008983830, Terminating object
Arg3: fffffa8008983b10, Process image file name
Arg4: fffff80002b948b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8008983830

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME:  csrss.exe

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.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT: 
fffff880`06b130a8 fffff800`02c1b5e2 : 00000000`000000f4 00000000`00000003 fffffa80`08983830 fffffa80`08983b10 : nt!KeBugCheckEx
fffff880`06b130b0 fffff800`02bc899b : ffffffff`ffffffff fffffa80`08e91ac0 fffffa80`08983830 fffffa80`08983830 : nt!PspCatchCriticalBreak+0x92
fffff880`06b130f0 fffff800`02b48448 : ffffffff`ffffffff 00000000`00000001 fffffa80`08983830 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`06b13140 fffff800`0288fed3 : fffffa80`08983830 fffff800`c0000006 fffffa80`08e91ac0 00000000`00560e00 : nt!NtTerminateProcess+0xf4
fffff880`06b131c0 fffff800`0288c470 : fffff800`028dc67f fffff880`06b13b38 fffff880`06b13890 fffff880`06b13be0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06b13358 fffff800`028dc67f : fffff880`06b13b38 fffff880`06b13890 fffff880`06b13be0 00000000`005619a0 : nt!KiServiceLinkage
fffff880`06b13360 fffff800`028902c2 : fffff880`06b13b38 00000000`00013510 fffff880`06b13be0 00000000`00561478 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`06b13a00 fffff800`0288ee3a : 00000000`00000000 000007fe`fd3ed8b4 00000000`0056d401 00000000`00013510 : nt!KiExceptionDispatch+0xc2
fffff880`06b13be0 00000000`76f79c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`005613c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f79c12


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

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

As such, I would try running a system file scan first to check for file corruption and fix it. Follow the instructions here: SFC /SCANNOW Command - System File Checker

There was also a 0x7A KERNEL_DATA_INPAGE_ERROR. The dump file for this BSOD was incomplete for some reason so the faulting driver/module was not recorded. 7A's are sometimes caused by data corruption in the page file.

Spoiler

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc50000000, ffffffffc00000c0, 35003880, fffff8a000000118}

Probably caused by : Unknown_Module_fffff800`02802000 ( nt+7cc40 )

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

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

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 filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc50000000, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc00000c0, error status (normally i/o status code)
Arg3: 0000000035003880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a000000118, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

ADDITIONAL_DEBUG_TEXT: 
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002802000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.

BUGCHECK_STR:  0x7a_c00000c0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800028efb52 to fffff8000287ec40

STACK_TEXT: 
fffff880`071797e8 fffff800`028efb52 : 00000000`0000007a fffff6fc`50000000 ffffffff`c00000c0 00000000`35003880 : nt+0x7cc40
fffff880`071797f0 00000000`0000007a : fffff6fc`50000000 ffffffff`c00000c0 00000000`35003880 fffff8a0`00000118 : nt+0xedb52
fffff880`071797f8 fffff6fc`50000000 : ffffffff`c00000c0 00000000`35003880 fffff8a0`00000118 ffffffff`ffffffff : 0x7a
fffff880`07179800 ffffffff`c00000c0 : 00000000`35003880 fffff8a0`00000118 ffffffff`ffffffff 00000000`c00000c0 : 0xfffff6fc`50000000
fffff880`07179808 00000000`35003880 : fffff8a0`00000118 ffffffff`ffffffff 00000000`c00000c0 fffffa80`00000000 : 0xffffffff`c00000c0
fffff880`07179810 fffff8a0`00000118 : ffffffff`ffffffff 00000000`c00000c0 fffffa80`00000000 fffff8a0`00000118 : 0x35003880
fffff880`07179818 ffffffff`ffffffff : 00000000`c00000c0 fffffa80`00000000 fffff8a0`00000118 fffff800`028a6bc5 : 0xfffff8a0`00000118
fffff880`07179820 00000000`c00000c0 : fffffa80`00000000 fffff8a0`00000118 fffff800`028a6bc5 fffffa80`070324a0 : 0xffffffff`ffffffff
fffff880`07179828 fffffa80`00000000 : fffff8a0`00000118 fffff800`028a6bc5 fffffa80`070324a0 fffffa80`070324a0 : 0xc00000c0
fffff880`07179830 fffff8a0`00000118 : fffff800`028a6bc5 fffffa80`070324a0 fffffa80`070324a0 fffffa80`093846b0 : 0xfffffa80`00000000
fffff880`07179838 fffff800`028a6bc5 : fffffa80`070324a0 fffffa80`070324a0 fffffa80`093846b0 fffffa80`009f0090 : 0xfffff8a0`00000118
fffff880`07179840 fffffa80`070324a0 : fffffa80`070324a0 fffffa80`093846b0 fffffa80`009f0090 00000000`00002000 : nt+0xa4bc5
fffff880`07179848 fffffa80`070324a0 : fffffa80`093846b0 fffffa80`009f0090 00000000`00002000 fffff6fc`50000000 : 0xfffffa80`070324a0
fffff880`07179850 fffffa80`093846b0 : fffffa80`009f0090 00000000`00002000 fffff6fc`50000000 ffffffff`ffffffff : 0xfffffa80`070324a0
fffff880`07179858 fffffa80`009f0090 : 00000000`00002000 fffff6fc`50000000 ffffffff`ffffffff 00000000`00000000 : 0xfffffa80`093846b0
fffff880`07179860 00000000`00002000 : fffff6fc`50000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : 0xfffffa80`009f0090
fffff880`07179868 fffff6fc`50000000 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 fffffa80`08886ca0 : 0x2000
fffff880`07179870 ffffffff`ffffffff : 00000000`00000000 00000000`00000000 fffffa80`08886ca0 fffff800`02ab45c0 : 0xfffff6fc`50000000
fffff880`07179878 00000000`00000000 : 00000000`00000000 fffffa80`08886ca0 fffff800`02ab45c0 fffffa80`009f0090 : 0xffffffff`ffffffff


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt+7cc40
fffff800`0287ec40 48894c2408      mov     qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt+7cc40

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  Unknown_Module_fffff800`02802000

BUCKET_ID:  WRONG_SYMBOLS

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

So the second thing I would try if the system scan doesn't find anything and/or doesn't fix the issue would be to disable page files. If you would rather have page filing enabled, this is just a temporary measure to see if this is the cause. To so this follow these instructions:

If you still get BSOD's after attempting the above solutions, I would suggest enabling Driver Verifier. Follow the instructions here under Option one: Driver Verifier - Enable and Disable

On a side note, some programs don't play nice with Windows 7 and have been known to casue BSOD's. If you're using any of the following programs and the above solutions don't resolve your issues uninstall them (one at a time if you have more than one) and see if that helps.

Antivirus/Anti-malware
- Avast
- Kaspersky
- McAfee
- Comodo Firewall
Uninstall and replace with Microsoft Security Essentials and use Windows firewall

Virtual drive/ROM Burning programs
- Alcohol 120%
- Daemon Tools
Uninstall.

Also make sure all your divers are up to date. Make sure that your Windows update is up to date as well (SP1 in particular).

edit: Make sure your M4 SSD's firmware is up to date as well. To do this use either the Firmware Update utility for the M4:

Spoiler

Guide: Guide to updating firmware on M4 with Utility
Utility download: M4 SSD Firmware Update Utility 000F

Or the manual boot file:

Spoiler

Guide: Guide to updating firmware with manual boot file
Manual Boot File Download: M4 000F Firmware (Manual Boot File)

 

Thank you very much!

So far

1 i've update firmware for SSD...done
2. Window updates.... done
3. SFC no problems ...done

Ran AS SSD test to see if it crashes...but it didn't. But score improves by a lot. See below


old




So i'll wait to see if i have anymore crashes before i attempt the other stuff, whats your views?

Thanks!!

 

Very nice
There isn't much else to do really. Just keep using your computer normally and see if any other BSOD's happen. If none pop up then all's good
If you get any more just upload the dump file and I'll analyze them.

 

Cool, i wll let you know! Thanks again for your help and time!

 

Np. Glad to help
I'm willing to bet that the firmware upgrade was what solved it but do keep my updated. If any new BSOD's happen upload the dumps.

 

spoke too soon! : )

Ok i booted up and went to make a cup of tea...and came back only to see a another bluescreen!! Damn it. Maybe we can isolate it this time.

Here it is
041712-9516-01.dmp - 4shared.com - online file sharing and storage - download

 

another one 3hrs later.....

Link below

Bad pool caller???? Minidump


This is worrying as this SSD is new...a complete pain in rear. Crucial M4 128gb..my HD had no problems..perhaps it is the operating system files like you said..

 

Was too good to be true I guess. This BSOD was another 0x0F4 caused by csrss.exe.

Spoiler

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008bc7b30, fffffa8008bc7e10, fffff80002d96660}

Probably caused by : csrss.exe

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: fffffa8008bc7b30, Terminating object
Arg3: fffffa8008bc7e10, Process image file name
Arg4: fffff80002d96660, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8008bc7b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME:  csrss.exe

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

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT: 
fffff880`036b10a8 fffff800`02e1d772 : 00000000`000000f4 00000000`00000003 fffffa80`08bc7b30 fffffa80`08bc7e10 : nt!KeBugCheckEx
fffff880`036b10b0 fffff800`02dcaf7b : ffffffff`ffffffff fffffa80`08c51b60 fffffa80`08bc7b30 fffffa80`08bc7b30 : nt!PspCatchCriticalBreak+0x92
fffff880`036b10f0 fffff800`02d4a0f4 : ffffffff`ffffffff 00000000`00000001 fffffa80`08bc7b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`036b1140 fffff800`02a92f13 : fffffa80`08bc7b30 fffff800`c0000005 fffffa80`08c51b60 00000000`00a10a00 : nt!NtTerminateProcess+0xf4
fffff880`036b11c0 fffff800`02a8f4d0 : fffff800`02ade9df fffff880`036b1b38 fffff880`036b1890 fffff880`036b1be0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`036b1358 fffff800`02ade9df : fffff880`036b1b38 fffff880`036b1890 fffff880`036b1be0 000007fe`fd69a358 : nt!KiServiceLinkage
fffff880`036b1360 fffff800`02a93302 : fffff880`036b1b38 00000000`00a50000 fffff880`036b1be0 000007fe`fd69f03c : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`036b1a00 fffff800`02a91e7a : 00000000`00000001 00000000`00a10fb8 00000000`00000001 00000000`00a50000 : nt!KiExceptionDispatch+0xc2
fffff880`036b1be0 00000000`77218e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00a10fc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77218e3d


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
---------

Again, csrss.exe is a system file but if the SFC Scan didn't pick it up there may not be anything wrong with it. You can try a repair install (instructions here: Repair Install) to see if that helps.

Alternatively, some viruses/malware have been known to pretend to be this system file. I would run a full antivirus scan with Microsoft Security Essentials with the latest definitions to make sure you don't have any virus/malware.

The only other explanation I can think of is that the SSD itself is bad and may need to be RMA'ed. Run an elevated command prompt (start>type "cmd">right click>click "Run as Admininstrator") and type "chkdsk c: /f /r" without the quotes. It will as k if you want to run on next reboot; type "y" for yes and hit enter. Reboot and let the scan run. It shouldn't take too long with an SSD but keep an eye on it while it's running to see if any errors pop up. If it does find errors it should fix it and generate a log file. To access this file, go to Start>type "eventvwr.msc" (without the quotes)>press Enter>Expand the Windows logs heading>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). Copy/paste the results into your next post.

The other dump file you uploaded was a 0x0C2 caused by fwpkclnt.sys. I'm not familiar with this file so I'll have to look into it. However Avast was involved so I suggest uninstalling Avast (using this utility: Avast Removal Tool) and installing Microsoft Security Essentials ( MSE) in its stead. I'll post back when I have more to add.

 

thought i'd do chkdsk test first...........

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 18/04/2012 00:31:11
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Mozart-PC
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is SSD Crucial 128GB.

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

CHKDSK is verifying files (stage 1 of 5)...
164864 file records processed.

File verification completed.
58 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)...
204194 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

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

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

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

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
164848 files processed.

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

Free space verification is complete.
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.

125032447 KB total disk space.
84255700 KB in 142576 files.
83972 KB in 19667 indexes.
0 KB in bad sectors.
271087 KB in use by the system.
65536 KB occupied by the log file.
40421688 KB available on disk.

4096 bytes in each allocation unit.
31258111 total allocation units on disk.
10105422 allocation units available on disk.

Internal Info:
00 84 02 00 ce 79 02 00 a6 e9 04 00 00 00 00 00 .....y..........
d0 01 00 00 2c 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.

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="2012-04-17T23:31:11.000000000Z" />
<EventRecordID>2985</EventRecordID>
<Correlation />
<Execution Processid='0' Threadid='0' />
<Channel>Application</Channel>
<Computer>Mozart-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is SSD Crucial 128GB.

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

CHKDSK is verifying files (stage 1 of 5)...
164864 file records processed.

File verification completed.
58 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)...
204194 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

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

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

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

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
164848 files processed.

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

Free space verification is complete.
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.

125032447 KB total disk space.
84255700 KB in 142576 files.
83972 KB in 19667 indexes.
0 KB in bad sectors.
271087 KB in use by the system.
65536 KB occupied by the log file.
40421688 KB available on disk.

4096 bytes in each allocation unit.
31258111 total allocation units on disk.
10105422 allocation units available on disk.

Internal Info:
00 84 02 00 ce 79 02 00 a6 e9 04 00 00 00 00 00 .....y..........
d0 01 00 00 2c 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.
</Data>
</EventData>
</Event>

 

You SSD seems to be fine; no bad sectors. Try uninstalling Avast and using MSE instead. At this point, it may not be a bad idea to test your RAM as well: RAM - Test with Memtest86+. Let Memtest run for at least 10 passes (letting it run overnight would be best).

 

I've been using Windows Firewall with no issues thus far and many Windows 7 "gurus" seem to highly recommend the MSE/Windows Firewall combo.
Personally I've found MSE to be a very good antivirus program. I installed it on some of the computers at my workplace and found viruses that Norton had overlooked. In addition, it's very lightweight and non-resource hungry. Best of all it's free with daily definitions updates! Very much up there in my books

Several of your BSOD's (including your newest one) involve a driver accessing either the RAM or readonly memory. I want to eliminate faulty RAM modules as a cause.
Also, it would help if you enable driver verifier (instruction here: Driver Verifier - Enable and Disable). With it enabled, Driver Verifier will trigger a BSOD if it finds a faulty driver. Be sure to upload all Verifier enabled dumps. Use your computer normally while Verifier is running.

I should have asked sooner but are you overclocking your RAM, CPU or GPU?

 

cool well i'm happy with mse..all good! thanks for recommendation!

so i better do a memory test then?

I don't do any of those mentioned overlocking tweaks.

the only thing my music samples require is lots of ram...i have 8gb and a windows 7 64bit managed paging file..i have played not with those settings...though there seems to be a 50% division of those who believe you dont need a paging file for an SSD drive.

 

Glad MSE is working well for you.

For now I would suggest enabling Driver Verifier and use your computer as you normally would. When you get a BSOD upload your new dump.

Run memtest as soon as you get a chance. I would suggest running it overnight as with 8GB of RAM it will take a while for a few passes to complete. I strongly suspect your RAM is to blame.

Personally I have page files disabled as I have 16GB of RAM which is usually more than enough unless I'm messing with high res photos in Photoshop.

 

no blue screens yet, still havent done the mem test! hope 8 hours will be enough.

Problem 2

Crackling and Stuttering Audio with internet.​

Sorry to keep pestering...but though my audio workstation is functioning well with no audio crackles. BUT I have started suffering from audio crackles n stuttering i.e on youtube or anything to do with the internet running audio/video.


I used DPC latency checker...i've posted results with (wireless on and off.
Never have i had this kind of crackling before in either IBM T61 or X61 with wireless switched on. Im using same programs and same audio drivers..shouldnt be an issue with T500.

It's better with wireless off. see pics.

Whats causing the Red spikes every few secs with wireless disabled??
My wireless adapter is wi fi link 5300 Agn.

i'll post a screen shot of my CPU as its happening...im sure its not normal.




wireless with firefox 11.0 running




Wireless off



CPU when audio crackles...sometimes % in the 90's



Worse





Many Thanks!

 

Advise: buy a Samsung SSD

 

Glad to hear that you haven't had any BSOD's.
As for your other problem, I'm not sure what the cause is or how to go about troubleshooting it. First thing I would try would be to see if there are any updates for your video, audio and wireless adapter drivers. If you're already using the latest version of the driver(s) try uninstalling them and then installing them again.

edit: Did you enable driver verifier? If you did and it's still enabled, you can disable it.

 

ok i'll try your suggestions.

Im going to disable it now, thanks for your help!


Update
Would you believe it..........
When you mentioned disabling the driver verifier...i remembered that these audio probs happened at the time of installing. I even forgot i installed it.
Guess what? It's all back to normal again!! I can't believe D Verifier was causing my system to slow down.!!even googled it to find it can cause dpc latency spikes. Yikes. i'll remember that next time!!

 

haha glad you figured it out

 

Hey hope you're well!
Im really happy with my computer all working...but...

I've had 2 crashes since... I wouldn't mind but these 2 were only a week apart...too close for my liking..

Pls have a look for me.
Many thanks when you get the time!
2 Minidumps.rar - 4shared.com - online file sharing and storage - download

 

I'm at work at the moment but I'll give those dump files a look when I get home later today.

 

Simple yet great fix is just formatting the damn thing... but glad you got it worked out

 

Both BSOD's were 0xF4 stop errors. The latest one was caused by wininit.exe and the one before that was caused by csrss.exe. Since you've already tried the SFC System Scan, I would suggest running memtest to see if any of your RAM modules are bad. Let the scan run for at least 7 passes (best to leave it to run overnight).
If it doesn't find anything, please try a Repair Install.

 

thanks v very much, im i right in thinking that this is related to windows OS? Will a reinstall fix this?

 

I can't say for sure but it may help. I would probably try a repair install first.

 

Any updates? haha, I've been following this post. I too have a thinkpad T500, and was considering getting the crucial M4(256GB), but I seem to find quite a few BSOD issues with people who have them and the T400/T500...is it more than a coincidence?