BSOD - Caught!
Hey, After several days of no crashes I finally caught one (I so feel like a fisherman :-) ) My computer just crashed with a message saying that it crashed in the cache_manager (0x00000034). WhoCrashed says that there is no info in the minidump so I'm guessing that this is hardware based. So, any idea if this is RAM, hard drive or motherboard based? Or is there no way to tell?Thanks-- Rob
February 4th, 2009 10:31pm

Hi - Bugcheck 0x34 = aproblem occurred inthe cache manager. One fixis to add more RAM. However, this 0x34 BSOD could be the result of a rogue driver in need of an update. I'd like to get the dump files and some system info to take a look and see if anything evident. Please go to c:\windows\minidump andcopy all dump files out to another folder. Then run3 reports for me to go along w/ dumps:msinfo32 - NFO fileSTART | type msinfo32 | save in default NFO format (NFO = file ext)PERFMON - Vista system Health Report - HTML fileSTART | type perfmon /report | ~60 seconds viewer appears | save as an HTML fileDXDiag - DirextX Diag - START | dxdiag | save as text file (bottom-center "save ..") Zip the dumps, TEXT, NFOand HTML files up and send to me via email jcgriff2.BSOD*at*hotmail.comPlease place a link to this thread in the emailhttp://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/35468e8e-33cf-4f4b-bf4b-6746fa21469b/In the interim, I suggest that you run the Driver Verifier -START | type cmd.exe | right-click on cmd.exe uptop under programs | Run as Administrator | type verifier & hit enter - the Verifier screen will appear | do the following: 1. Select 2nd option - Create custom settings (for code developers)2. Select 2nd option - Select individual settings from a full list.3. Check the boxes Special Pool Pool Tracking Force IRQL checking4. Select last option - Select driver names from a list 5. Click on the Provider heading - sorts list by Provider6. Check ALL boxes where Microsoft is not the Provider7. Click on Finish 8. Re-boot If the Driver Verifier (DV) finds a violation (flags a driver), it will result in a BSOD. To see the status of the D/Verifier, bring up an elevated cmd/DOS prompt and type verifier - select the last option on the first screen - "Display information about the currently verified drivers..". If your system becomes too unstable (the d/v utilizes CPU & RAM), turn d/v off - type verifier /reset then re-boot. If you get a verifier-enabled BSOD, get the minidump and send it, please. Regards. . . jcgriff2 .
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2009 1:41am

You can run the analysis of the crash dump on your own system and then copy/paste the results back here for everyone to take a look at. Here's the link on how to do this: How to read the small memory dump files that Windows creates for debugging - JohnEDIT: FWIW the Debugging Tools help file states that this error is a problem with the file system cache manager. So, there'sseveral places to lookfirst - the file system (and the hard drive), the memory (since the error occurred in memory), and misbehaving drivers.Try running a hard drive diagnostic and a memory diagnostic first. That'll help to rule out hardware problems at the outset.Also, here's a suggestion from the Debugging Tools help file: Bug Check 0x34: CACHE_MANAGER The CACHE_MANAGER bug check has a value of 0x00000034. This indicates that a problem occurred in the file system's cache manager. Parameters The following parameters are displayed on the blue screen. Parameter Description 1 Specifies source file and line number information. The high 16 bits (the first four hexadecimal digits after the "0x") identify the source file by its identifier number. The low 16 bits identify the source line in the file where the bug check occurred. 2 Reserved 3 Reserved 4 Reserved Cause One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error. Resolving the Problem To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel. 2008Microsoft CorporationSend feedback on this topicDebugging Tools for WindowsAugust 24, 2008
February 15th, 2009 6:18pm

Rbdwarf said:Hey, After several days of no crashes I finally caught one (I so feel like a fisherman :-) ) My computer just crashed with a message saying that it crashed in the cache_manager (0x00000034). WhoCrashed says that there is no info in the minidump so I'm guessing that this is hardware based. So, any idea if this is RAM, hard drive or motherboard based? Or is there no way to tell?Thanks-- Rob if you are overclocking , try backing it off a bit...Just a thought...Kris -------- Gigabyte GA-EP45-UD3P, E7200 2.53@3.8ghz, 2x1gb OCZ Reaper1150@1203, EVGA 9800GTX+ N873 , BFG GS-650, Vista Ult 32 SP1 / Win 7 7000
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2009 8:23pm

This is what I get when I try to e-mail jcgriff2.BSOD*at*hotmail.com Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 Requested action not taken: mailbox unavailable (state 14).-- Rob
February 16th, 2009 4:41am

HiRob -My apologies to you -the account was not activated. Please tryemail again. The dump file - is it - 0 - bytes? Did you find it inc:\windows\minidump w/ filename = date/ time of BSOD?Please send any dumps found andthe other files I asked for. A minidump won't tell us CPU or mobo bad. It can indicate a direction in which to look. If software related, the driver verifier can be a big help to us.Pleaserun it as instructed.Thanks.Regards. . .jcgriff2.@ usasma - Thank you for the information on bugcheck 0x34. If being cautious re: sysinfo, I can assure you motives genuine.I am TechNet Plus subscriber and a Mod, MS Support at Tech Support Forum.com (usually stay in Vista) and have processed >> 10,000 dumps in the last year. Sysinfo used in conjuction w/ dumps - like this -[SOLVED] Windows Error RecoveryThis is me -http://www.techsupportforum.com/members/185203.htmlKind Regards. . .JC
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2009 7:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics