Solved help please to fix BSOD

[bordercollie]

WOW ! I ran the Driver Verifier and almost didn't get my computer back. whew.
I think I have followed instructions and have all requested data.

Thanks in advance and I anxiously await your reply.

Sincerely,
Steve

 

[mgorman87]

[COLOR=Red]AutoReboot=TRUE[/COLOR]
Caption=
DebugFilePath=%SystemRoot%\MEMORY.DMP
[COLOR=Red]DebugInfoType=0[/COLOR]
Description=
ExpandedDebugFilePath=C:\Windows\MEMORY.DMP
ExpandedMiniDumpDirectory=C:\Windows\Minidump
KernelDumpOnly=FALSE
MiniDumpDirectory=%SystemRoot%\Minidump
Name=Microsoft Windows 7 Home Premium |C:\Windows|\Device\Harddisk0\Partition1
OverwriteExistingDebugFile=TRUE
SendAdminAlert=FALSE
SettingID=
[COLOR=Red]WriteDebugInfo=FALSE
WriteToSystemLog=FALSE[/COLOR]

Your not writing mini dumps when your computer crashes. Follow the instructions here -> http://www.carrona.org/setmini.html to fix that problem. Then re-enable driver verifier and get some more crashes for me and upload a new report.

 

[bordercollie]

will do. thanks mgorman87

I hope I can get back to running after re-enabling driver verifier.

wish me luck.

 

[bordercollie]

man, that had me all scared again thinking I had lost my 'puter.

ok, i set the mini dump thing, re-enabled driver verifier and it went straight to blue.

i re-ran Windows_NT6_BSOD and perf mon.

I hope this works.

 

[mgorman87]

man, that had me all scared again thinking I had lost my 'puter.

ok, i set the mini dump thing, re-enabled driver verifier and it went straight to blue.

i re-ran Windows_NT6_BSOD and perf mon.

I hope this works.

AutoReboot=TRUE
Caption=
DebugFilePath=%SystemRoot%\MEMORY.DMP
DebugInfoType=0
Description=
ExpandedDebugFilePath=C:\Windows\MEMORY.DMP
ExpandedMiniDumpDirectory=C:\Windows\Minidump
KernelDumpOnly=FALSE
MiniDumpDirectory=%SystemRoot%\Minidump
Name=Microsoft Windows 7 Home Premium |C:\Windows|\Device\Harddisk0\Partition1
OverwriteExistingDebugFile=TRUE
SendAdminAlert=FALSE
SettingID=
[COLOR=Red]WriteDebugInfo=FALSE
WriteToSystemLog=FALSE[/COLOR]

Still not enabled.

if you type advanced system settings in the start bar and hit enter and then under startup and recovery hit settings it should look like the screen shot below
View attachment 151985

 

[bordercollie]

OMG, I had to go thru TWO BSOD before I figured out to re-set the mini

I hope these are as you wish

 

[bordercollie]

previously, write to log was checked but not small memory dump as is n

it is correct this time. i swear it.

 

[mgorman87]

it is correct this time. i swear it.

Event[471]:
  Log Name: System
  Source: volmgr
  Date: 2011-04-29T20:20:16.764
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Steve-PC
  Description: 
Crash dump initialization failed!

This is usually caused by hardware issues. I would like you to run some tests and report back the results.

1. Memtest86 - Run for 7-8 passes - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
2. Prime95 - Run all three tests for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html
3. Hard drive scan usings SeaTools - http://www.seagate.com/ww/v/index.j...toid=480bd20cacdec010VgnVCM100000dd04090aRCRD - Both long and short tests

 

[bordercollie]

I don't think it's a hardware issue as I play America's Army almost every night for a 2 or 3 hours with no problems. However, I am starting to run the hardware tests you recommend. The stress test says to let it run for 6 hours which I am doing now. The memory test says to run it overnight. And I haven't even read about the Seagate Tool yet.
My BSOD started almost a year ago. I learned that if I re-boot my PC within a few minutes after an initial power-up, I am good to go. The computer will also be fine even if I re-boot almost immediately after an initial "cold" power-up. Usually I power-up from a "cold" state, read an email or two, run CCleaner and then hit Restart and it's good to go, even for hours of gaming. Now if I were to shut it down for a few hours and try to power up "cold," it would go to BSOD.
So again, I don't think it's hardware.

Isn't there another way to get my log files to you?

Thanks mgorman87
and where did those big red letters that said, "If I helped you ...?"
and how do I reply to that?

 

[mgorman87]

I don't think it's a hardware issue as I play America's Army almost every night for a 2 or 3 hours with no problems. However, I am starting to run the hardware tests you recommend. The stress test says to let it run for 6 hours which I am doing now. The memory test says to run it overnight. And I haven't even read about the Seagate Tool yet.
My BSOD started almost a year ago. I learned that if I re-boot my PC within a few minutes after an initial power-up, I am good to go. The computer will also be fine even if I re-boot almost immediately after an initial "cold" power-up. Usually I power-up from a "cold" state, read an email or two, run CCleaner and then hit Restart and it's good to go, even for hours of gaming. Now if I were to shut it down for a few hours and try to power up "cold," it would go to BSOD.
So again, I don't think it's hardware.

Isn't there another way to get my log files to you?

Thanks mgorman87
and where did those big red letters that said, "If I helped you ...?"
and how do I reply to that?

Cold boot issues usually have to do with memory from what i've seen in past experiences. Run the tests and let me know the results. It doesn't hurt to test. Also, the red stuff at the bottom had to do with +rep. It's the scales in the top right corner of the post.

Oh ya, stop running CCleaner. It does more harm then good. It also removes the memory dump files. I used to run it all the time, but then I learned on here that it isn't all that good.

 

[bordercollie]

Thank you, mgorman87

Well for the past six hours I've been running the Stress Test.
I'll run the Memory Test tonight as the instructions recommend and post these results Sunday AM along with the Seagate scan.

whew!

 

[bordercollie]

if I get BSOD running driververifier ...

doesn't that mean my problem lies with my drivers?

 

[mgorman87]

doesn't that mean my problem lies with my drivers?

If DV catches a driver then yes. Otherwise, probably not

 

[bordercollie]

doesn't that mean my problem lies with my drivers?

If DV catches a driver then yes. Otherwise, probably not

What do you mean by this?
I'm afraid to run Driver Verifier again for fear I'll never get my computer back.

I ran the Stress test for over SEVEN HOURS yesterday with no problems.
I ran the Memory test for NINE HOURS with no errors.

mgorman87 - please tell me how I can repair the faulty driver(s)

Thanks,
Steve

 

[mgorman87]

doesn't that mean my problem lies with my drivers?

If DV catches a driver then yes. Otherwise, probably not

What do you mean by this?
I'm afraid to run Driver Verifier again for fear I'll never get my computer back.

I ran the Stress test for over SEVEN HOURS yesterday with no problems.
I ran the Memory test for NINE HOURS with no errors.

mgorman87 - please tell me how I can repair the faulty driver(s)

Thanks,
Steve

If you make a system restore point before turning DV on, you should be able to restore back to it if your computer gets screwed up due to. There is no way to know what driver, if any, is causing your computer issues. The only way to know is by turning on DV and having it blue screen and then analyze the dumps.

You say you ran prime95 for seven hours? Was that just one of the tests? Did you run the other two?

 

[bordercollie]

I don't know "about the other two."
here's the results attached

when I run driver verifier and have a real hard time getting back to windows.
i mean it goes thru it's self repair for 30+ minutes and does nothing


but i thought my system wasn't even logging the dumps? so if i run driververifier, how can you analyse the dumps if we can't find them?

 

[mgorman87]

I don't know "about the other two."
here's the results attached

when I run driver verifier and have a real hard time getting back to windows.
i mean it goes thru it's self repair for 30+ minutes and does nothing


but i thought my system wasn't even logging the dumps? so if i run driververifier, how can you analyse the dumps if we can't find them?

That's right. I forgot about that. So yea, if your not logging dumps then there's no point to turn on DV. We need to figure out why your not logging dumps

As for the other two tests.
http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

There are three tests that need to be run with Prime95. Follow the tutorial above. It will explain it.

 

[cluberti]

Open regedit, and export the following 2 keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Change the two files you created via exporting those from .reg to .txt and post them here. Those should help us determine why you're not getting dumps.

 

[bordercollie]

OMG, you want me to run that stress test again? (I'M getting stressed, not the computer. LOL)
I've read http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html and I don't see where there are any "other" tests, ie test #2 nor test #3

thanks catherder but I don't know how to change the "stuff" in the crashcontrol folder so I hope these screen shots work. LOL


Thanks guys.

 

[mgorman87]

4. Select "Small FFTs", [B][U]or whatever tests someone asks you to run[/U][/B]. 
Prime95 will automatically select the maximum number of 
threads reported by Windows in the "Number of threads to run" box.

You need to run Small FFTs, In-place large FFTs, and the Blend test for 3-4 hours each.