Frequent multiple errors BSOD.

Senarium · 13 May 2015

Hi Everyone,

I have a weird BSOD problem which I cannot solve for a while.

The main strange thing about this is that I get BSOD only after cold boot.
So it acts like this:

1. start PC.
2. Get to Windows Logo Screen
3. BSOD
4. Restart
5. Get to menu where I can try to repair or Start Normally

If I Choose Repair, it will fail to repair and will try to restore

If I Choose Start Normally, it will start OK, no BSOD, can work normally, games, browse internet, everything is normal.

6. Shutdown PC
7. Next time when I start is all over again i.e. Go to Step 1

I have this problem for a while, so what I tried:
1. Another Windows 7
2. Another HDD
3. Only HDD connected
4. Changed RAM
5. Tried with built in GPU

Result is the same as above everytime.

Please suggest what could be the cause.
Logs and dumps attached.

Thank you

Arc · 15 May 2015

Code:

BugCheck 24, {1904fb, fffff88002fd7618, fffff88002fd6e70, fffff880012e9d93}

Probably caused by : CI.dll ( CI!I_ReloadCatalogs+15c )

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

Hi Senarium.

Only crash dumps will not be enough here. Let us see the complete zip as per the Blue Screen of Death (BSOD) Posting Instructions . The other files will be very important here.

Senarium · 16 May 2015

Seems that collector did not added them in the zip. Did the collection second time and seems Ok now. Please see attached.

Arc · 16 May 2015

OK now.

Test both the HDDs using Seatools.

SeaTools for DOS and Windows - How to Use

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

OEM on 7/2009 BIOS

Senarium · 18 May 2015

Hi Arc,

Thank you for your support!

Tested with Seatools, both HDDs. Both passed the test Long Generic.

Tested RAM with memtest86+: run for about 17h45m. 16 passes. 0 errors.

Arc · 18 May 2015

At the next step, I would like to make you aware of counterfeit windows installations, which are vulnerable to various threats including security threats and random BSODs.

Your product ID is of Dell OEM.

Code:

Product ID:                00426-OEM-8992662-00400

Whereas it is a custom built system, using an ASUS retail motherboard.

Code:

Motherboard ASUSTeK Computer INC. P5P41D (LGA775)

This discrepancy may cause various issues. So it is better to not use a counterfeit windows installation. I would suggest you to get a valid windows license and perform a clean reinstall with it.

In the mean time, you may use Windows 10 for free (for a few months till you get the license), by signing in windows insider program. https://insider.windows.com/

Senarium · 18 May 2015

Wow, that's interesting, I always been sure that I have a license. Bought it like this.

I guess will have to check with the vendors, but seems without success since this is quite old PC...

Till Windows 10 comes from out from Preview, is there any other suggestions to get rid of these BSODs?

Thank you.

Layback Bear · 18 May 2015

Arc is off line at this time.

Be advise that a legal Windows 7 installation and activation must be install first. Then we will be able to continue with BSOD help.

Please read the forum rules. Number 4 should cover this problem.

https://www.sevenforums.com/misc.php?do=showrules

Arc · 19 May 2015

Senarium said:

Till Windows 10 comes from out from Preview, is there any other suggestions to get rid of these BSODs?

Thank you.

If there is any further issue after having a legit OS, we are always here to help you. :)
But please understand that a counterfeit install is vulnerable by its own virtue. It is beyond troubleshooting.

Senarium · 19 May 2015

You are totally right, and I agree with you. I will check the issue with license, solve it, if possible or buy another. And if the problems still persists than I will open another topic.

Thank you a lot for your support. Appreciate it.

I will mark the topic as solved now.