Jump to content

EverIncompetent

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About EverIncompetent

EverIncompetent's Achievements

0

Reputation

  1. Got it I think, but its like 4gb, too big to upload. How can I send it to you? Whoops! Ran debugger, and it says partially corrupted. I will wait for another crash then reply here again.
  2. Ok I did that, when it crashes again I get a full dump?
  3. How do you make a paging file in the volume? I don't understand what that means. Is that just meaning that it has to be on the same Hard Drive? My paging file size will be 4096+64 = 4160 mb, what should the Initial size be..? I can't change the value without setting an "Initial" and a "Maximum" value The Registry value for dumps is set to 1 like you said. What else do I need to do?
  4. I can look for dumps. Meanwhile I will give you some specs/WhoCrashed info. Specs: Intel 2.00 GHz Dual Core Processor 4 GB Ram Windows 7 Home Premium 64 Bit On Fri 1/1/2010 9:03:57 PM your computer crashed This was likely caused by the following module: csrss.exe Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006C5BB30, 0xFFFFFA8006C5BE10, 0xFFFFF80002BD7240) Error: CRITICAL_OBJECT_TERMINATION Dump file: C:\Windows\Minidump\010110-26067-01.dmp file path: C:\Windows\system32\csrss.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Client Server Runtime Process The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Fri 1/1/2010 6:11:16 PM your computer crashed This was likely caused by the following module: csrss.exe Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006E73B30, 0xFFFFFA8006E73E10, 0xFFFFF80002BCD240) Error: CRITICAL_OBJECT_TERMINATION Dump file: C:\Windows\Minidump\010110-30139-01.dmp file path: C:\Windows\system32\csrss.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Client Server Runtime Process The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Fri 1/1/2010 5:25:48 PM your computer crashed This was likely caused by the following module: wininit.exe Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006E50B30, 0xFFFFFA8006E50E10, 0xFFFFF80002B98240) Error: CRITICAL_OBJECT_TERMINATION Dump file: C:\Windows\Minidump\010110-33197-01.dmp file path: C:\Windows\system32\wininit.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Windows Start-Up Application The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. Looks like all I got was a mini-dump, so how do I set it to give a full dump after it crashes? I thought I had but I guess it didn't work... I will check on the forums and get back to you
  5. So I was using my computer and it suddenly got a BSOD... again. I looked at several posts on this forum and did what it seems everyone wants in this situation, I tried to create a full dump file. I think I managed it with the instructions on one post using a directory called C:\adplus. The folder that it created is attached. Can anyone tell me what to do to fix the crashes? I have used WhoCrashed to determine that Csrss.exe was the process that ended most times, and once it was wininit. I don't have any idea what to do to read a crash report, maybe you guys do. Thanks for any help you can give. Crash_Mode__Date_01_10_2010__Time_16_24_27PM.zip
×
×
  • Create New...