CACHE_MANAGER (34)
See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000050830
Arg2: fffff88003185708
Arg3: fffff88003184f60
Arg4: fffff800029eff8c
Debugging Details:
------------------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 34, {50830, fffff88003185708, fffff88003184f60, fffff800029eff8c}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
Followup: Pool_corruption
---------
Code:CACHE_MANAGER (34) See the comment for FAT_FILE_SYSTEM (0x23) Arguments: Arg1: 0000000000050830 Arg2: fffff88003185708 Arg3: fffff88003184f60 Arg4: fffff800029eff8c Debugging Details: ------------------
If you have a usb stick attached, it is causing the error right now. You should have just removed sptd.sys before as I said and then posted new crashes if needed.
Hi havocas
Your minidump revealed the following message
Sadly I'm new to reading minidumps and still a bit confused with the reported cause.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 34, {50830, fffff88003185708, fffff88003184f60, fffff800029eff8c} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 ) Followup: Pool_corruption ---------
Have you tried removing your memory modules and then re-seating them in the slots. I have had BSOD's related to badly seated hardware in the past. Definitely a thought worth thinking about.
I am trying to figure out why you have a driver dated back as far as 2006 on a fresh install.
Do you have a program installed called "Macrovision SafeDisc"? A quick search shows this program is the only one linked to the following driver.
secdrv.SYS Wed Sep 13 08:18:38 2006
Somehow, you do have a FAT volume on the pc, somewhere. It is causing the current issue.
Secdrv.sys is known well and that one never needs any attention. It can be ignored, always, regardless of date.![]()
No, 100% can not be power supply or keyboard, mouse or monitor.
1) Update Realtek Audio driver. Do exactly like this -
Open device manager. Right click it and choose uninstall. Then check the box to delete the driver. Hit ok and continue uninstalling:
RTKVHD64 RTKVHD64.sys Tue Aug 18 05:29:10 2009
When done, install this:
RtkHDAudio
Reboot.
2) Navigate to C:\Windows\System32\drivers
If RtHDMIVX.sys is there, rename it to RtHDMIVX.BAK.
Reboot.
3) Update Realtek lan driver:
Rt64win7 Rt64win7.sys Thu Jul 30 07:58:43 2009
RTL8111
4) Update video card driver:
atikmpag atikmpag.sys Wed Aug 25 21:20:56 2010
Drivers & Support | GAME.AMD.COM
---------
If you follow this precisely as shown, it will be cool. Let me know how you get on with it.![]()