BSOD after "starting windows" startup screen

[ColWar]

My system has continually played up since I bought it about 5 weeks ago.
My very first power up gave me three blue screen crashes with a "cpu fan error" and 2 beeps on POST. The system was bought overclocked (from 3.2 to 4 GHz) and I assumed this was the problem but during most of these crashes the BIOS reverted to default settings and still produced errors.
Eventually one of the BSODs corrupted my windows installation so I was forced to reload windows and was told by my suppliuer to run MemTest - this gave no errors after 2 hours so the computer was returned for inspection.
It was returned to me fairly promptly (not a good sign!) after the bios had been reset (same as I had done on numerous occasions) and tested without fault for 24 hours.
Guess what happened when I powered up - yes the dreaded BSOD after the " starting windows" screen appeared.
The BSODs vary and include stop:0x24, 0x50 and 0x3b errors. I also am now getting blank screens regularly after the starting windows message and the only way to get over this is to power down and restart. Once up and running the computer nearly always performs OK - it is just the starting phase that gives a problem.
I have tried many of the suggestions listed on this thread including reseating all connectors, memory sticks, video card, adjusting ram voltage , dram frequency, updated the bios, reloading windows (three times so far) without effect.
I have just ordered some different ram to try but am running out of ideas.
Event viewer bugcheck showed the following;

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 12/04/2010 16:00:19
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: COLIN-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff88006f3ae58, 0xfffff88006f3a6b0, 0xfffff8800123c3cb). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041210-19234-01.
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">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-04-12T15:00:19.000000000Z" />
<EventRecordID>16659</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>COLIN-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000024 (0x00000000001904fb, 0xfffff88006f3ae58, 0xfffff88006f3a6b0, 0xfffff8800123c3cb)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">041210-19234-01</Data>
</EventData>
</Event>

 

[zigzag3143]

My system has continually played up since I bought it about 5 weeks ago.
My very first power up gave me three blue screen crashes with a "cpu fan error" and 2 beeps on POST. The system was bought overclocked (from 3.2 to 4 GHz) and I assumed this was the problem but during most of these crashes the BIOS reverted to default settings and still produced errors.
Eventually one of the BSODs corrupted my windows installation so I was forced to reload windows and was told by my suppliuer to run MemTest - this gave no errors after 2 hours so the computer was returned for inspection.
It was returned to me fairly promptly (not a good sign!) after the bios had been reset (same as I had done on numerous occasions) and tested without fault for 24 hours.
Guess what happened when I powered up - yes the dreaded BSOD after the " starting windows" screen appeared.
The BSODs vary and include stop:0x24, 0x50 and 0x3b errors. I also am now getting blank screens regularly after the starting windows message and the only way to get over this is to power down and restart. Once up and running the computer nearly always performs OK - it is just the starting phase that gives a problem.
I have tried many of the suggestions listed on this thread including reseating all connectors, memory sticks, video card, adjusting ram voltage , dram frequency, updated the bios, reloading windows (three times so far) without effect.
I have just ordered some different ram to try but am running out of ideas.
Event viewer bugcheck showed the following;

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 12/04/2010 16:00:19
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: COLIN-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff88006f3ae58, 0xfffff88006f3a6b0, 0xfffff8800123c3cb). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041210-19234-01.
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">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-04-12T15:00:19.000000000Z" />
<EventRecordID>16659</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>COLIN-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000024 (0x00000000001904fb, 0xfffff88006f3ae58, 0xfffff88006f3a6b0, 0xfffff8800123c3cb)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">041210-19234-01</Data>
</EventData>
</Event>

Like I said in your other post we need the actual DMP file. use these instructions http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html


Ken

 

[ColWar]

I tried to get a zipped file but got "file not found or no read permission"?
Each time I untick the "Read only" bot and exit it resumes to read only.
I thought I was the administrator on my computer so don't know where I am going wrong?

 

[Capt.Jack Sparrow]

I tried to get a zipped file but got "file not found or no read permission"?
Each time I untick the "Read only" bot and exit it resumes to read only.
I thought I was the administrator on my computer so don't know where I am going wrong?

Hello Colwar Welcome to SF !!

Try running this Tool http://www.sevenforums.com/crash-lockup-debug-how/66913-sf-diagnostic-tool.html make sure when you run it Right Click and Run as administrator !!

Hope this helps,
Captain

 

[ColWar]

Thanks for that Captain!
I've now attached my latest dump file.
Hope someone can decipher it?

 

[Buildncastles]

It honestly might be the memory. I also have G.Skill memory for my build and it has been giving me many issues. I've recently been able to stabilize it by adjusting timings and voltage. I am afraid to shut down my computer for a long time though. Eventually I'll have to fix it but I'll just wait until that happens (don't fix what's not broken).

What was able to help also was running memtest86+ for a couple hours before booting the computer up in windows. My guess is that it's really the memory. I want to replace mine as well to see if that helps. I've bookmarked your post since your issues are very similar to mine. I hope someone can help you and in turn help me as well.

 

[Jonathan_King]

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

BSOD Index

Usual causes: System service, Device driver, graphics driver, memory

BSOD Index

Try testing your memory. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

Also run a system files check. Open an elevated command prompt and enter sfc /scannow.

 

[Capt.Jack Sparrow]

Thanks for that Captain!
I've now attached my latest dump file.
Hope someone can decipher it?

Hello !!

I don't believe its Driver Verfied Dump !! Still according to your Dump file i see there is a Bugcheck 0xc0000005 possibly your Antivirus / Firewall that can the cause. Uninstall it completely and also use Removal Tool to remove it completely. Google should help find it. Delete all the Minidump from the folder and let the Driver Verifier run atleast for 36 hours.

Hope this helps,
Captain

 

[ColWar]

First of all, many thanks for the replies to my posting.
I ran a system files check without error but Memtest86 (which I previously only managed to run under windows) showed up an error during the third or fourth pass.
I am therfore hoping that the new memory I have just installed ( Corsair CMX4GX3M2A1600C9) will prevent the dreaded BSOD when I fire up the computer in the morning. (I will also get the faulty ram replaced).
I will let you all know how the system performs over the next few days - fingers crossed.

 

[Buildncastles]

Yes, ColWar please let us know. If it is your RAM that would be really beneficial to me. I've held off on purchasing new RAM because I'm nervous that it might not be the whole reason my system is acting up. But if you're successful it might just push me towards purchasing some new sticks.

 

[ColWar]

Just to update those interested, since replacing my dodgy memory (I was sent some replacement from the computer builders very quickly - give them credit for something!!) I have not had any blue screens of death. I was getting blank/black screens after the "starting windows" screen loaded but I consider this to be unrelated to the memory and is a possible driver issue (which I think I have solved).
So Buildncastles if your system is acting as mine was I would recommend you bite the bullet and get some replacement ram - it seems to have worked for me.

 

[Buildncastles]

Thanks for the update! Glad everything is working out for your computer. I'll now have to do the same.