I've had this problem for a while now. BSOD at every startup, then starting up in memory recovery mode didn't work. Eventually after selecting Start Windows Normally 1-3 times it would work. I remember trying to get to the bottom of this but didn't know about dump files or how to get to them. And I couldn't read the BSOD because it was too fast. I happened to glance POOL_CORRUPTION or something like that, googled it and it brought me to a site explaining about dump logs and how to get to them/read them. I have the last dump file attached. Let me know what you think guys (and gals).

Thanks

I think I may finally be able to have a normal computer and not be afraid of restarting my computer. Here's hoping....


[year+ old attachment deleted by admin]Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply==================================================
Dump File : Mini040912-01.dmp
Crash Time : 4/9/2012 6:54:47 AM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000110b
Parameter 3 : 00000000`00010005
Parameter 4 : fffffa80`06c16570
Caused By Driver : ksecdd.sys
Caused By Address : ksecdd.sys+616c570
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini040912-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 274,248
==================================================1) What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

2) Please boot to your W7 dvd and run startup repair options.

3) If the problem persists try running sfc /scannow (http://support.microsoft.com/kb/929833). The problem is associated with a system file and it's possible that it has become corrupt somehow.I want to say it started after the integrated sound card stopped WORKING. It was faulty.

What's a W7? Windows 7? I have Vista installed. I've tried the system restore already and the . It seems to happen no matter what I do. I'll try that scannow thing tonight and get back to you in the morning.

Thanks for your help everyone.So did you replace the card? Please, tell us everything at once. Providing information one bit at a time makes it very difficult to offer appropriate advice.Okay, yes I replaced it with a PCI diamond audio pro 7.1 from C-Media Electronics, I believe.
I also replaced the graphic card, but that was the day I got the computer. I disabled the ATI RADEON HD 3200 and installed the ATI RADEON HD 4300/4500 series according to the manufacturers guidelines. It didn't start BSODing until around after I installed the sound card. I also had Kaspersky at the time. I don't know if any of this is RELEVANT but there it is.To *censored* with tomorrow morning. I just finished the system file checker and got these results when I entered this command after verification was complete.

findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt

And here are the results:


2012-04-09 16:52:45, Info CSI 00000171 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PUBLICKEYTOKEN = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-04-09 16:52:48, Info CSI 00000173 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-04-09 17:00:57, Info CSI 000002f7 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-04-09 17:00:57, Info CSI 000002f9 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

Okay, I'm not concerned with the settings.ini file for the sidebar (do you use the sidebar by the way?).

After reboot do you still get a blue screen error?

Please look in device manager - any yellow or red symbols?I never use the sidebar. Almost everytime I reboot whether I shut down or restart. The Gateway screen with F2 and F8 at the bottom will show , then it will be a BSOD. Something about POOL_CORRUPTION. Then it will go to the Gateway screen again. Then the Windows has had an unexpected shut down with two options, Memory recovery mode (which always leads me to the same screen of two options I'm describing here) or start windows normally. I choose start windows normally of course since it's the only option that works. Sometimes it will work the FIRST time I choose start windows normally. Sometimes it will BSOD again. Eventually Windows will load.

What about ksecdd.sys or ntoskrnl.exe? Were they in the system files we just checked?

There is a yellow ARROW by the old Graphics Card in device manager. It's been there for a while, way before this problem started.1) Uninstall the old display adapter in device manager

2) So you are saying that even after running sfc /scannow you still get the blue screen at boot, is that correct?I will uninstall the old driver and reboot then get back to you.

It used to only BSOD when I would restart. So I had to use only shut down. Then it started doing it no matter what I used.Okay, it restarted just fine. Although the old graphics card re-installed itself upon start up. I guess I should just disable it then?

So this system file checker, should it be a regular form of maintenance to prevent this from happening again? What is a good maintenance routine that I should adopt? I'm scared that one day my comp will crash and I wont be able to "resuscitate" it. I've already had to replace a faulty hard drive.

Thanks a TON for the help! I'm sorry that I was a pain. This problem started a while ago and I was slow to remember what exactly had happened.No, system file checker should NOT be used unless needed. You had at least one corrupt system file and we replaced it with an original version, that's all. As for regular maintenance, the MOST important thing any computer user can do is create regular back ups to off-disc media with disc imaging software. That way, if something like this happens again you can just restore the last image.