BSOD

[americancritic]

Hello

This is the second time I had a BSOD in the last 45 days when I have been on the internet, the second is time today at 9:00 P.M. which is 5-18-2011, so this is what I have done besides pulling out my hair.

1. Clicked Start...
2. Clicked control panel...
3. Double Clicked system...
4. Clicked the advance tab...
5. Clicked Settings under the startup and recovery...
6. In the write debugging information list, I clicked small memory dump but mine does not show (64) mine is small memory dump (128)...I wrote the path down, I did the same for the kernel memory dump.

I closed everything and went back to my desktop.

1. Clicked start.
2. In the search box I typed %systemRoot%\minidump and I used .dmp also, it's tells me there if no file. Plus I tried it this way
systemroot\minidump...

I did the same thing with the kernel also. I have tried to type just minidump and with the .dmp also.

I have looked in the event viewer and the only that was there at the same time as the BSOD was this...

(A compatible trusted platform module (TBS) security device cannot be found on the computer) - TBS - could not be started...

My system seems to be running fine but it has happened twice now so I am very confident there will be more, but if I can't get to the report's or files it won't do me any good...

So please to all members who work with BSOD give me some suggestions on how to get the reports I need, they have to be somewhere in my computer. I, like a couple more members are just now starting to learn and we are being taught the BSOD. The one BSOD file that I can pull up it says the file is empty...

So anyone please give some of your expert advice on where and how to get to these reports..

Thank you all so very much...

americancritic

 

[richc46]

Tom
I have seen this problem before. For reasons that I do not know. Minidumps are not always created even if set to do so.

 

[kesume]

Not necessarily helping find the dump file but, can you get to the event log. Would that give us some clues?

 

[niemiro]

Hello all!

Tom
I have seen this problem before. For reasons that I do not know. Minidumps are not always created even if set to do so.

Commonest reason is the Page File.

Hello

This is the second time I had a BSOD in the last 45 days when I have been on the internet, the second is time today at 9:00 P.M. which is 5-18-2011, so this is what I have done besides pulling out my hair.

1. Clicked Start...
2. Clicked control panel...
3. Double Clicked system...
4. Clicked the advance tab...
5. Clicked Settings under the startup and recovery...
6. In the write debugging information list, I clicked small memory dump but mine does not show (64) mine is small memory dump (128)...I wrote the path down, I did the same for the kernel memory dump.

I closed everything and went back to my desktop.

1. Clicked start.
2. In the search box I typed %systemRoot%\minidump and I used .dmp also, it's tells me there if no file. Plus I tried it this way
systemroot\minidump...

I did the same thing with the kernel also. I have tried to type just minidump and with the .dmp also.

I have looked in the event viewer and the only that was there at the same time as the BSOD was this...

(A compatible trusted platform module (TBS) security device cannot be found on the computer) - TBS - could not be started...

My system seems to be running fine but it has happened twice now so I am very confident there will be more, but if I can't get to the report's or files it won't do me any good...

So please to all members who work with BSOD give me some suggestions on how to get the reports I need, they have to be somewhere in my computer. I, like a couple more members are just now starting to learn and we are being taught the BSOD. The one BSOD file that I can pull up it says the file is empty...

So anyone please give some of your expert advice on where and how to get to these reports..

Thank you all so very much...

americancritic

Hello Tom!

Since a Minidump or Small Kernal Dump is taken out of a Full Memory Dump, which is what is actually dumped, there are a few prerequisites for a successful Minidump generation:

FIrstly, please make sure that your PageFile: http://www.vistax64.com/tutorials/132201-virtual-memory-paging-file-change.html

is ENABLED, is set to expand at least the size of your total physical RAM (8GB according to your specs) + some extra MB. This extra is debated over, from about 1M to 250MB. I am not sure exactly which is correct. I think that 11MB is about correct. Give yourself a good GB over. It won't harm anyone, and will only expand as required. Also, the Page File must be on the same partition (usually C:\) as your Windows installation is on (this is because the NtSetFileInformation function cannot support Cross Partition Operations).

Summary:

PageFile = enabled
PageFile = Size of physical RAM + a bit (1GB for safety)
PageFile location = on partition of Windows installation.

I then want you to test it out for me. If you have corrected something on the above advice, then probably all will be well.

However, follow Step Two here: KB Parallels: How to generate a memory dump file by using the keyboard.

with the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters registry key.

Then by hold down the right CTRL key and press the SCROLL LOCK key two times.

Your computer will BSoD (save your work first!)

Then check to see if a minidump has been generated.

IF IT STILL HAS NOT:

There are still many more prerequisites! At that point, please run this tool dry: http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

and other files in it will help me analyse the cause.

Thanks a lot, and the very best of luck!

Richard

 

[americancritic]

Hello this is what I think your looking for, I'm attaching a screenshot for you to see, now what do you want me to do with it.

Sorry I have 8 GB Ram...

 

[americancritic]

Sorry I do not know anything about the registry or how to change anything, this will need to be detailed for me, Create a value etc is like asking me to build a space ship, I have no idea. But am will to learn...

 

[americancritic]

I put the reports in my first post, I hope you find something because it does not look like there was a dump and I do not know there should be sense it did the bsod...

 

[americancritic]

Plus my eldest son uses my admini account and both times after he has left I got the bsod's..

The first a while back and then the next day when I was on the internet it crashed and bsod'ed then yesterday after he left about 2 hours later I got another bsod so thinking about it I got them after he used the internet and both times I got the BDOD's I was on the internet. I have not had any when I am just using my computer say like MS word type of thing. I don't know if that means anything or not...

In my first post right after it happened I checked the event viewer and had the TBS error that happened at the exact time as the bsod...

 

[americancritic]

Is this it, nothing more.

 

[kesume]

I read the reports, but could not find anything to help?
I guess it must be down to the missing dump reports!
Sorry americancritic!

 

[mgorman87]

Check out this post and make sure everything is correct
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

Event[116]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-05-18T20:53:00.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Tom-PC
  Description: 
Fault bucket X64_0x4E_99_nt!MiBadShareCount+4b, type 0
Event Name: BlueScreen
Response: None
Cab Id: 0
 
Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 
 
Attached files:
[COLOR=red]C:\Windows\Minidump\Mini051811-01.dmp[/COLOR]
C:\Users\Tom\AppData\Local\Temp\WER-57283-0.sysdata.xml
C:\Users\Tom\AppData\Local\Temp\WER866D.tmp.version.txt

According to your event log a mini dump was created. Do you run any type of system cleaners?

[B]STOP 0x0000004E: PFN_LIST_CORRUPT[/B]
[URL="http://carrona.org/bsodindx.html#top"]
[/URL]
 
 Usual causes:  Device driver, ?memory

Enable driver verifier - Driver Verifier - Enable and Disable - Windows 7 Forums
Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+ - Windows 7 Forums
2. Prime95 - Run all three tests for 3-4 hours each or until fail - CPU - Stress Test with Prime95 - Windows 7 Forums

 

[americancritic]

I use CCleaner once every 2 months and I do not use registry cleaners at all. I do see a bosd report but it will not open it says access is denied and it will not open in windbg. I will bring it up and take a screenshot to upload.

New Ram is 5 months old DDR2 2gb x 4 sticks speed 800MHz...

Memtest done 6 weeks ago and was fine, online ram test says it's fine...

I will do the memtest again if I have to, but we all know it sucks to wait that long and I ran it for 8 pass's...

 

[mgorman87]

Ok. Then instead of running memtest, enable driver verifier and use the computer how you normally would

 

[americancritic]

I can do that here are the screenshots...

As you can see there is a bsod but nothing will open it, it is as if the file is empty but it still shows...

 

[americancritic]

Sense there was no bsod report as far as a minindump the windbg would not open it...

 

[mgorman87]

Can you upload the contents of your minidump folder?

 

[americancritic]

As you can see it says there is no file, why I have no idea because I save everything and the last time I used CCleaner was about 5 weeks ago, and like I said I do not use registry cleaners at all.

Plus this is what I get when I type verifier from the start do you run it with the elevated prompt. any ideas on the driver veirfier

 

[americancritic]

Hello Mgorman87

I posted right after you and your no where to be found as you logged out. Here is a look at my drivers, which some go back to 2005...

Maybe someone can help....

 

[americancritic]

Verifier.exe is started so we will see what happens, plus learning about the BSOD this will tell me whether or not I will use veifier.exe in the future as far as a OP goes...

 

[americancritic]

Hello just a small note when most OP's come here they know zero about computers so for them you might want to say Verifier.exe as I knew that but was curious if you would put it in there for me or not.

This is not about you and hope I have not hurt your feelings by saying the above but I am learning about ever aspect of the BSOD and if I was a OP which I am I would like that info because I would be back asking more questions on how to do it, your help on this is very kind and I hope you find the problem...

Thank you

Tom