[BrianR1976]

Twice in the last couple weeks I have gotten this BSoD. I don't know whats up here or how to fix it. I dont think in 5 or 6 years I have gotten a BSoD so something must be wrong. I looked at possible suggestions and I dont think I have updated any drivers or anything. It happened once at startup and once after I started the computer and opened Firefox up. The second time (Firefox) I had to unplug my router and plug it back in. Could be that the router is screwing things up?

Also In my startup files I have something new, dumprep 0 -k

Edited by BrianR1976, 24 August 2011 - 12:49 AM.

[Advertisements]

Download and run WhoCrashed, see what it tells you about the cause of the BSODs.

[Ztruker]

Download and run WhoCrashed, see what it tells you about the cause of the BSODs.

[BrianR1976]

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: REESECOMPUTER
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Pentium® 4 CPU 2.66GHz Intel586, level: 15
1 logical processors, active mask: 1
RAM: 1071644672 total
VM: 2147352576, free: 2052341760



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Wed 8/24/2011 5:16:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082311-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFF7848709)
Bugcheck code: 0x100000D1 (0xFFFFFFFF86C00000, 0x2, 0x0, 0xFFFFFFFFF7848709)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown CUSTOM_ERROR





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

1 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[Ztruker]

Rats, that was pretty useless. Please zip up the crash dump from C:\WINDOWS\Minidump and upload it here. Use the Browse and Attach This File buttons below/left of the text input area.

[BrianR1976]

I hope this is what you need.

[Ztruker]

Ummm, nothing there.

[BrianR1976]

Sorry not quite sure why it didnt upload.

Attached Files

•  Minidump82311.zip   13.57KB   127 downloads

[Ztruker]

No better, dump seems to be corrupted, sorry.

Leave the dumprep 0 -k

If another BSOD occurs, zip and upload that dump to a reply here. Hopefully it will have more information that can help determine what is causing the problem.

You may want to look at Event Viewer, see if it shows any problems around the time the BSODs occurred.

[BrianR1976]

three questions. if we wait for another BSOD will the thread go into lockdown or will it just float down the list till I need to use it again. When and if I do need to post again how will you know about it? And three, whats Event Viewer?

[rshaffer61]

if we wait for another BSOD will the thread go into lockdown or will it just float down the list till I need to use it again

Nope we do not close topics in this area even after they are resolved.

When and if I do need to post again how will you know about it?

Email notification of your response

And three, whats Event Viewer?

Please follow the steps below to enter the Event Viewer program in XP. This will give me more information into what is causing your issue.

Go to

Start and then click on Run
Type in eventvwr.msc and press Enter
On left side click on Applications On right side look for any RED X about the time of a incident
On left side click on System. On right side look for any Red X about the same time of a incident
Also look for any yellow exclamation mark at the same time in either of the above
If you find any double click on one at a time and take a screenshot.
To take a screenshot click on your Print Screen on your keyboard. It is normally the key above your number pad between the F12 key and the Scroll Lock key
Now go to Start
All Programs
Accessories
Paint
In the empty white area click and hold the CTRL key and then click the V
Go to the File option at the top and click on Save as
Save as file type JPEG and save it to your Desktop

Include as a attachment in your next reply

[Ztruker]

No, the thread will remain open. I'll be notified when a new post is made to this thread.

Info on Event Viewer: EVENT VIEWER - How to use, Windows Made Easy

I will be away for a week, but I'll have a laptop and have asked other techs here to keep an eye on topics I'm working on.

Edit: Ooops, see rshaffer61 already replied, sorry. Catching a plane at 11:30AM - Syonara

[BrianR1976]

These were the 4 event reports in System that happened around the time the problem last occurred. There was nothing in the Application area other than Search Index problems, and none around that day. The MCSTRM problem seems to happen every time I turn on my computer. Its up there constantly.

Attached Thumbnails

• 

[rshaffer61]

Go Start and then to Run ("Start Search" in Vista),
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.


If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.

Go Start and then Run
type in regedit and click OK


Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

You will see various entries Values on the right hand side.

The one we want is called: SourcePath

It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.

Now restart your computer and try sfc /scannow again!


Thanks to Broni for the instructions

[BrianR1976]

Sorry for the delay in responding to this. SFC came back with nothing

[rshaffer61]

Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to Winlogon and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.