New
#11
BSOD playing Team Fortress 2/using After Effects cs5.5
-
-
New #12
oops, just saw you posted again. I updated my last post after reading your post once more. Here they are:
Error, Time, Source, ID
Error 10/20/2011 12:22:34 PM Kernel-EventTracing 3 Session
Error 10/20/2011 2:56:41 PM Disk 11 None
Error 10/20/2011 8:25:31 AM SideBySide 33 None
Critical 10/19/2011 11:16:04 PM Kernel-Power 41 (63)
Error 10/20/2011 1:13:55 PM Application Error 1000 (100)
Error 10/19/2011 11:16:27 PM BugCheck 1001 None
Error 10/20/2011 11:54:16 AM Dhcp-Client 1002 Address Configuration State Event
Error 10/19/2011 11:16:27 PM BugCheck 1005 None
Error 10/20/2011 3:52:42 PM Eventlog 1101 Event processing
Error 10/20/2011 3:52:42 PM EventLog 6008 None
Error 10/19/2011 6:23:44 PM Service Control Manager 7000 None
Error 10/20/2011 12:18:48 PM Service Control Manager 7001 None
Error 10/19/2011 6:23:44 PM Service Control Manager 7009 None
Error 10/20/2011 12:22:47 PM Service Control Manager 7023 None
Error 10/20/2011 1:51:15 PM Service Control Manager 7026 None
Error 10/20/2011 12:19:01 PM DistributedCOM 10005 None
Error 10/20/2011 8:25:31 AM SideBySide 33 None
-
New #13
-
New #14
Disk details are:
Log Name: System
Source: Disk
Date: 10/20/2011 2:56:41 PM
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Flynn-PC
Description:
The driver detected a controller error on \Device\Harddisk1\DR1.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Disk" />
<EventID Qualifiers="49156">11</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-10-20T21:56:41.701462300Z" />
<EventRecordID>1813</EventRecordID>
<Channel>System</Channel>
<Computer>Flynn-PC</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Harddisk1\DR1</Data>
<Binary>0E01800001000000000000000B0004C003010000000000000000000000082D000000000000000000C39003000000 0000FFFFFFFF0600000058000000000000000000061208000010000000003C000000000000000000000040A7DD0C80FAFFFF 000000000000000040E84B0D80FAFFFF00000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Bug check details are:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 10/19/2011 11:16:27 PM
Event ID: 1005
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: FLYNN-PC
Description:
Unable to produce a minidump file from the full dump file.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1005</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-10-20T06:16:27.000000000Z" />
<EventRecordID>916</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>FLYNN-PC</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>
-
New #15
Any ideas on what the problem is?
-
New #16
I've stopped getting BSOD altogether and now my system either freezes the screen or goes black. The last time I rebooted it suggested doing windows startup repair so I let that go for awhile. I also looked up the first error and tried to find a solution myself, so I tried doing a chkdsk on my hard drive but that didn't seem to help either. Is it something driver related or hardware issues?
-
New #17
Could be either. when you did the chkdsk did you use the "F" switch?
two more things you can try
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
Read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
Second driver verifier
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
-
New #18
Here's the CBS log:
cbs.log
I couldn't tell if it helped or not (I'm guessing its just meant for creating a log?) but it said that no issues were found, or something to that effect. I did the second part and am now stress testing my computer.
In regards to the chkdsk: I don't think I did. I just kind of went with the prompts and got it going.
-
New #19
Ok it just crashed to blue screen, and at the bottom it says Collecting data for crash dump... But it's been on that for the last five minutes. I waited an additional 20 minutes, and then forced shutdown. Took a little while to get it to reboot successfully, but when it did I went into safe mode w/networking and still no log. I'm really at a loss as to what to do next, I don't have money/resources to try and swap hardware out and see if one of them is the cause, so all I can do is make sure whether or not it is a driver or system file issue. Any useful info in the cbs log?Last edited by relliott1; 23 Oct 2011 at 21:58.
-
New #20
Still getting crashes and games seem to have taken a 50% fps hit too. I'm going to try testing my RAM with Memtest and see if that's it. Really I'm just posting in here now because if I find a solution myself others with this issue can fix it, because this thread fell back into page 4, so my chances of further help seem small. BUT I will gladly accept further help if anyone has any ideas
Quote
Related Discussions