Recently, I've been having system crashes with blue screens. Usually, it starts with a scratching sound from the left side of my HP ProBook 4510s. I have Win 7 32 bit, T5870, 4GB ram. I used bluescreen view to read the dump files and I need an analysis to know what causes the problem. Following are dump files from bluescreen view. I hope someone can help with this problem. 013011-21559-01.dmp 1/30/2011 4:27:01 PM 0xc000021a 0xc22ef598 0xc0000006 0x777891c5 0x0050ebec ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\013011-21559-01.dmp 2 15 7600 146,680 012911-25240-01.dmp 1/29/2011 11:28:41 PM KERNEL_DATA_INPAGE_ERROR 0x0000007a 0xc045b750 0xc000000e 0x67ffb860 0x8b6ea03a Ntfs.sys Ntfs.sys+c403a NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\012911-25240-01.dmp 2 15 7600 152,856 012711-22089-01.dmp 1/27/2011 5:47:45 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x872d04f0 0x872d065c 0x82e79dd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\012711-22089-01.dmp 2 15 7600 146,680 012611-27658-01.dmp 1/26/2011 9:09:48 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x872629c0 0x87262b2c 0x82e7ddd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\012611-27658-01.dmp 2 15 7600 146,904 011411-21153-01.dmp 1/14/2011 10:02:11 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x872f4030 0x872f419c 0x82e6bdd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\011411-21153-01.dmp 2 15 7600 146,744 011311-21590-01.dmp 1/13/2011 5:59:52 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x872e0830 0x872e099c 0x82e76dd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\011311-21590-01.dmp 2 15 7600 147,000 010911-19999-01.dmp 1/9/2011 6:30:13 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x871ff8f0 0x871ffa5c 0x82e3cdd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\010911-19999-01.dmp 2 15 7600 146,680 010811-22136-01.dmp 1/8/2011 11:53:50 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x872cf530 0x872cf69c 0x82e39dd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\010811-22136-01.dmp 2 15 7600 146,712 010711-30264-01.dmp 1/7/2011 6:31:40 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x872ff098 0x872ff204 0x82e34dd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\010711-30264-01.dmp 2 15 7600 146,712 010411-22042-01.dmp 1/4/2011 9:25:59 PM KERNEL_DATA_INPAGE_ERROR 0x0000007a 0xc045b850 0xc000000e 0x644a3860 0x8b70a900 Ntfs.sys Ntfs.sys+d6900 NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\010411-22042-01.dmp 2 15 7600 146,808 122710-28641-01.dmp 12/27/2010 12:20:03 AM KERNEL_DATA_INPAGE_ERROR 0x0000007a 0xc04e60d8 0xc000000e 0x02adfbe0 0x9cc1b000 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\122710-28641-01.dmp 2 15 7600 147,192 122510-19468-01.dmp 12/25/2010 2:18:34 AM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x8723ecf0 0x8723ee5c 0x82e61dd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\122510-19468-01.dmp 2 15 7600 147,512 122110-18751-01.dmp 12/21/2010 10:45:17 PM KERNEL_DATA_INPAGE_ERROR 0x0000007a 0x00000020 0xc000009d 0x8709360c 0x00000000 ntoskrnl.exe ntoskrnl.exe+832f4 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\122110-18751-01.dmp 2 15 7600 152,920 120810-40154-01.dmp 12/8/2010 11:48:46 AM REFERENCE_BY_POINTER 0x00000018 0x00000000 0x87502ca0 0x00000002 0xffffffff ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\120810-40154-01.dmp 2 15 7600 146,584 120610-19344-01.dmp 12/6/2010 11:55:28 PM KERNEL_DATA_INPAGE_ERROR 0x0000007a 0xc0604000 0xc000000e 0x58369880 0xc0800000 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\120610-19344-01.dmp 2 15 7600 146,776 120510-19749-01.dmp 12/5/2010 8:44:49 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x868fb600 0x868fb76c 0x82e7bdd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\120510-19749-01.dmp 2 15 7600 146,680 120110-24445-01.dmp 12/1/2010 8:32:36 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x872b6d40 0x872b6eac 0x82e6cdd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\120110-24445-01.dmp 2 15 7600 146,712 112810-19890-01.dmp 11/28/2010 9:03:51 AM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x87296d40 0x87296eac 0x82e3cdd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\112810-19890-01.dmp 2 15 7600 146,680 102410-20904-01.dmp 10/24/2010 1:38:00 AM KERNEL_DATA_INPAGE_ERROR 0x0000007a 0xc0604000 0xc000000e 0x6a06e880 0xc0800000 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\102410-20904-01.dmp 2 15 7600 146,744 090610-19890-01.dmp 9/6/2010 9:38:23 PM CRITICAL_OBJECT_TERMINATION 0x000000f4 0x00000003 0x86bfc310 0x86bfc47c 0x82c3ddd0 ntoskrnl.exe ntoskrnl.exe+dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) 32-bit C:\Windows\Minidump\090610-19890-01.dmp 2 15 7600 146,712

Bug Check Code 0xF4: The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. For more information, refer to this Microsoft article. Bug Check Code 0x7A: The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. For more information, refer to this Microsoft article. Bug Check Code 0x18: The REFERENCE_BY_POINTER bug check has a value of 0x00000018. This indicates that the reference count of an object is illegal for the current state of the object. For more information, refer to this Microsoft article. -------------------------------- Please use Windows Live Skydrive to upload dump files (c:\windows\minidumps) and post a link here so that I analyze them. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Thank you Mr.X, <!-- [if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves/> <w:TrackFormatting/> <w:PunctuationKerning/> <w:ValidateAgainstSchemas/> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF/> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>AR-SA</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> <w:DontGrowAutofit/> <w:SplitPgBreakAndParaMark/> <w:DontVertAlignCellWithSp/> <w:DontBreakConstrainedForcedTables/> <w:DontVertAlignInTxbx/> <w:Word11KerningPairs/> <w:CachedColBalance/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathPr> <m:mathFont m:val="Cambria Math"/> <m:brkBin m:val="before"/> <m:brkBinSub m:val="--"/> <m:smallFrac m:val="off"/> <m:dispDef/> <m:lMargin m:val="0"/> <m:rMargin m:val="0"/> <m:defJc m:val="centerGroup"/> <m:wrapIndent m:val="1440"/> <m:intLim m:val="subSup"/> <m:naryLim m:val="undOvr"/> </m:mathPr></w:WordDocument> </xml><![endif]--> Following is the link to Dump Files. http://cid-909873a7830a4bc2.office.live.com/browse.aspx/New%20folder?uc=5. I really appreciate your help as this is driving me crazy. Please note that I checked the HHD and its ok and I also checked the RAM and its ok. I did this with win7 utilities. Best regards.

Analyzed dump file: 122710-28641-01.dmp ------------------------------------------------------------ 0: 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: c04e60d8, lock type that was held (value 1,2,3, or PTE address) Arg2: c000000e, error status (normally i/o status code) Arg3: 02adfbe0, current process (virtual address for lock type 3, or PTE) Arg4: 9cc1b000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) Debugging Details: ------------------ ERROR_CODE: (NTSTATUS) 0xc000000e - Un p riph rique qui n'existe pas a t sp cifi . DISK_HARDWARE_ERROR: There was error with disk hardware BUGCHECK_STR: 0x7a_c000000e CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 82cc261a to 82cead10 STACK_TEXT: 8d74faf4 82cc261a 0000007a c04e60d8 c000000e nt!KeBugCheckEx+0x1e 8d74fb68 82cba0e5 87812864 8d74fbc0 82d42540 nt!MiWaitForInPageComplete+0x2fd 8d74fbfc 82c95e5f 82d42540 9cc1b000 878127d0 nt!MiIssueHardFault+0x3b2 8d74fc80 82c42259 00000001 9cc1b000 00000000 nt!MmAccessFault+0x2656 8d74fd10 82c41f7a 87a06d48 8d74fd30 00000000 nt!MiInPageSingleKernelStack+0x1cf 8d74fd44 82c9a023 87a06dbc 8d74fd90 82e1c6d3 nt!KiInSwapKernelStacks+0x41 8d74fd50 82e1c6d3 00000000 a48a5483 00000000 nt!KeSwapProcessOrStack+0x78 8d74fd90 82cce0f9 82c99fab 00000000 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiWaitForInPageComplete+2fd 82cc261a cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiWaitForInPageComplete+2fd FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete+2fd BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete+2fd Followup: MachineOwner --------------------------------------------------------------------------------------------------------- Bug Check Code 0x7A: The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. For more information, refer to this Microsoft article. Please use memtest86+ to check your RAM, if you find an error so replace the faulty one. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Analyzed dump file: 012611-27658-01.dmp ------------------------------------------------------------------- 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: 00000003, Process Arg2: 872629c0, Terminating object Arg3: 87262b2c, Process image file name Arg4: 82e7ddd0, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: 872629c0 IMAGE_NAME: csrss.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: csrss FAULTING_MODULE: 00000000 PROCESS_NAME: csrss.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - L'instruction 0x%08lx emploie l'adresse m moire 0x%08lx. Les donn es n cessaires n'ont pas t plac es en m moire en raison d'une erreur d'E/S de type 0x%08lx. BUGCHECK_STR: 0xF4_IOERR CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: 8f253c9c 82f310d7 000000f4 00000003 872629c0 nt!KeBugCheckEx+0x1e 8f253cc0 82eb4ed2 82e7ddd0 87262b2c 87262c30 nt!PspCatchCriticalBreak+0x71 8f253cf0 82eb6d6f 872629c0 8740f960 c0000006 nt!PspTerminateAllThreads+0x2d 8f253d24 82c9844a ffffffff c0000006 012ced24 nt!NtTerminateProcess+0x1a2 8f253d24 770364f4 ffffffff c0000006 012ced24 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 012ced24 00000000 00000000 00000000 00000000 0x770364f4 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0xF4_IOERR_IMAGE_csrss.exe BUCKET_ID: 0xF4_IOERR_IMAGE_csrss.exe Followup: MachineOwner --------- --------------------------------------------------------------------------------- Bug Check Code 0xF4: The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. For more information, refer to this Microsoft article. The BSOD is caused by csrss.exe. For more information about it, refer to this link. Please try to repair your windows install and check if this solve this problem. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Hi, Your .dmp files show csrss.exe and memory management as the cause for your crashes. Csrss.exe is the main executable for the Microsoft Client/Server Runtime Server Subsystem. However, csrss.exe is also a process which is registered as the W32.Netsky.AB@mm worm, the W32.Webus Trojan, Win32.Ladex.a, and more. I would advise you to scan your computer for viruses etc. You can refer to the following thread. http://social.answers.microsoft.com/Forums/en-US/vistasecurity/thread/ba80504b-61f1-4d71-960f-b561798b7b42 Best Regards, NikiPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks Niki, So mainly you think its a software problem and not a hardware one. What about the memory issues what causes the error. could it be a fault in the RAM. How can i deal with this. Regards,

What about the scratching sound that happens before the freeze. What causes this

You have a HDD hardware error , NO software error!: IOERR _IMAGE_csrss.exe ERROR_CODE: (NTSTATUS) 0xc000000e: // // MessageId: STATUS_NO_SUCH_DEVICE // // MessageText: // // A device which does not exist was specified. // #define STATUS_NO_SUCH_DEVICE ((NTSTATUS)0xC000000EL) DISK_HARDWARE_ERROR: There was error with disk hardware Check the cables and the HDD."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/