Windows 7 BSOD Madness

[Robvious82]

Been happening seemingly forever. I hope I uploaded everything I need.

 

[Trouble]

Hello and welcome to the forum.

Been happening seemingly forever. I hope I uploaded everything I need.

I would have expected more than a single dump file.
Looks like you have verifier enabled, probably time to turn it off. How to disable Driver Verifier Manager in vista - Microsoft Answers
I suspect your problem is likely the same one I wrote about here Link Removed
Most boards, when all four memory slots are populated with 667Mhz (1333) memory or faster, will require a slight bump in the memory controller voltage to compensate for the physical over burden. You should consult your Motherboard documentation in order to determine how to accomplish this or perhaps check the motherboard vendors support boards for your specific hardware and see if they have any suggestions.
I used this link here to help in my situation GA-870A-UD3 unstable with all four RAM slots in use and I choose to dumb down my memory to 533Mhz (1066) rather than to bump the voltage on the controller. My install has been stable ever since.
You can of course beat on your system, as I did, with MemTest86+ and Prime95 and see if yours exhibits similar symptoms or just cut to the chase and see if the solution works for you.
DUMP:

........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C1, {fffff98029b44c10, fffff98029b44c0b, c703e8, 32}
Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+108 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SPECIAL_POOL_DETECTED_[U][B][COLOR=#ff0000]MEMORY_CORRUPTION[/COLOR][/B][/U] (c1)
Special pool has detected [COLOR=#ff0000][U][B]memory corruption[/B][/U][/COLOR].  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff98029b44c10, address trying to free
Arg2: fffff98029b44c0b, address where one bit is corrupted
Arg3: 0000000000c703e8, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
Debugging Details:
------------------
BUGCHECK_STR:  0xC1_32
SPECIAL_POOL_CORRUPTION_TYPE:  32
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  [COLOR=#ff0000][U][B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B][/U][/COLOR]
PROCESS_NAME:  csrss.exe
CURRENT_IRQL:  1
LAST_CONTROL_TRANSFER:  from fffff80002d5dfe3 to fffff80002cd4c40
STACK_TEXT:  
fffff880`03f20448 fffff800`02d5dfe3 : 00000000`000000c1 fffff980`29b44c10 fffff980`29b44c0b 00000000`00c703e8 : nt!KeBugCheckEx
fffff880`03f20450 fffff800`02dd69b3 : 00000000`000000f0 00000000`00000000 fffff880`03f20c20 fffffa80`09e0bb30 : nt!MiCheckSpecialPoolSlop+0x83
fffff880`03f20490 fffff800`02e0293b : fffff800`02c58000 00000000`2b707249 00000000`00b55268 00000000`00000001 : nt!MmFreeSpecialPool+0x1d3
fffff880`03f205d0 fffff800`03179026 : fffffa80`07de0d02 fffffa80`07de0d60 00000000`00000000 fffff980`29b44c10 : nt!ExDeferredFreePool+0xf33
fffff880`03f20680 fffff800`031795ec : fffff800`02cc8296 fffff980`29b44c10 00000000`00000000 fffffa80`09d6e0b0 : nt!VfIoFreeIrp+0xe6
fffff880`03f206b0 fffff800`02cc8296 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IovFreeIrpPrivate+0x5c
fffff880`03f206f0 fffff800`02cda13d : fffffa80`09d6e060 00000000`00000000 fffff960`00118f70 00000000`00000000 : nt!KiDeliverApc+0x166
fffff880`03f20770 fffff800`02cd944a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000002 : nt!KiCommitThreadWait+0x3dd
fffff880`03f20800 fffff960`000b9968 : fffff900`00000002 fffffa80`098953c0 fffff900`00000001 fffff880`0000000d : nt!KeWaitForMultipleObjects+0x272
fffff880`03f20ac0 fffff960`000ba934 : 00000000`00000000 fffff900`c01c46d0 fffff960`00304560 fffff900`c01c4560 : win32k!xxxMsgWaitForMultipleObjects+0x108
fffff880`03f20b40 fffff960`00075128 : fffffa80`00000001 fffffa80`0000000c fffffa80`09d6e060 fffff6fc`4001f660 : win32k!xxxDesktopThread+0x254
fffff880`03f20bc0 fffff960`000f539a : fffffa80`00000001 fffff960`00304560 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x64
fffff880`03f20bf0 fffff800`02cd3ed3 : fffffa80`09d6e060 00000000`00000004 000007ff`fffac000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`03f20c20 000007fe`fdb51eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01f5fb08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdb51eea
STACK_COMMAND:  kb
FOLLOWUP_IP: 
win32k!xxxMsgWaitForMultipleObjects+108
fffff960`000b9968 8bf0            mov     esi,eax
SYMBOL_STACK_INDEX:  9
SYMBOL_NAME:  win32k!xxxMsgWaitForMultipleObjects+108
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: win32k
IMAGE_NAME:  win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5a
FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_win32k!xxxMsgWaitForMultipleObjects+108
BUCKET_ID:  X64_0xC1_32_VRF_win32k!xxxMsgWaitForMultipleObjects+108
Followup: MachineOwner

Regards
Randy

 

[Robvious82]

Thank you for your time and knowledge! Stupid question, but how exactly do I lower my RAM to the 533Mhz (1066)?

 

[Trouble]

You should consult your Motherboard documentation in order to determine how to accomplish this or perhaps check the motherboard vendors support boards for your specific hardware and see if they have any suggestions.

Thank you for your time and knowledge! Stupid question, but how exactly do I lower my RAM to the 533Mhz (1066)?

Not a stupid question but I suspect any attempt by me to answer might be stupid, in that every mother board manufacturer will probably be different in how you would go about performing the task. As I said above consult your motherboard documentation and or your motherboard vendors support forum and see if they might have some sticky threads regarding this task.
I can tell you how I did it on my particular Gigabyte board, but since I don't even really know what board you have your options may be completely different especially if it's a different manufacturer.

Restart computer
Hit Delete key during post to enter setup utility (BIOS)
Select M B Intelligent Tweaker
DRAM Configuration = Manual
DCTs Mode = Unganged
DDR3 Timing Items = Manuall
CAS# Latency = 7T
RAS to CAS R/W Delay = 7T
Row PreCharge Time = 7T
Minimum RAS Active Time = 20T
1T/2T Command Timing = 2T

But as I have already stated, yours may be different.
That is also the same location on my board where you can raise the DRAM Voltage incrementally say from 1.5 to 1.52 or 1.54

 

[Robvious82]

Thank you! I lowered my RAM clock speeds to 1067 in the BIOS and disabled Driver Verifier! Fingers crossed.

 

[Trouble]

Agreed. Fingers crossed here too. You may want to re-run CPUz and confirm that your settings are in effect what you expect and reflect your recent changes.

 

[Robvious82]

Everything was going well until a few mins ago...

 

[Robvious82]

Link Removed There is my file.

 

[Elmer]

....and?

Seriously, if you crashed can you attach the latest dump file.

And whilst I type it magically appears. Psychic powers or a greater force at work methinks.

 

[Trouble]

Check AMD or your motherboard manufacturer for an update for
AtiPcie.sys 5/5/2009 Link Removed
GEARAspiWDM.sys 5/18/2009 from here http://www.gearsoftware.com/support/drivers.php#
and
AsUpIO.sys 7/5/2009 from here likely Link Removed
Those all predate Windows 7 RTM.
Please re-run CPU-z and attach screen shots of all the tabs as well as all the slots under the SPD tab.
Thanks
Randy

 

[Robvious82]

AsUpIO.sys as well as the Bigfoot Networks drivers crash my system, even the latest versions on fresh install.

 

[Trouble]

AsUpIO.sys as well as the Bigfoot Networks drivers crash my system, even the latest versions on fresh install.

Not sure if that is a question or an answer, but have you check with your system vendor for an available BIOS update for your particular MoBo?

EDIT: What exactly is the Motherboard.... manufacturer, model name, model number and Rev. #?

 

[Robvious82]

I was unable to find a free BIOS update. The vendor's website takes me to a pay site. Also, I am not sure about my MoBo info. I may have the box that it came in, but I'll have to check that after work.

 

[Trouble]

I wouldn't recommend any paid for commercial resolution for a BIOS update. Normally these are provided free of charge through the manufacturer's website and are specific for their boards and their respective ICs and integrated devices.
Try using CPUz and check the mainboard tab or perhaps use something like Speccy which is referenced and linked to in this thread Link Removed

 

[Robvious82]

Link RemovedThanks for the help, and sorry about the delay. I updated my BIOS and the other things you recommended. Everything was going great until now. I am uploading the latest minidump as well as the tabs.

 

[Trouble]

There is a more current BIOS updated located here ASUSTeK Computer Inc. - Motherboards- ASUS M4A89GTD PRO/USB3 (3027 11/18/2011) you are currently at 2301 07/18/2011)
Additionally have you tried running the board without Cool n Quiet enabled just to check stability?
And it looks like you have reverted to standard 667Mhz (1333) timining for your memory which is a good thing (I have too), what are you currently showing for DRAM Voltage in the BIOS try 1.58, mine seems to have stabilized there, still working it out and may go to 1.6 if I get another one, but so far so good.
Regards
Randy

 

[Robvious82]

Thank you for the always quick reply. I will update the BIOS again and adjust the voltage this evening.


On a side note, it's kind of baffling that this stuff is so imprecise. I mean, having to be so precise and everything. I would have thought that by now, knowing that most users don't know a whole lot, these huge companies like Windows and ASUS would make their stuff easier to figure out and maintain. Would it be so hard for Windows to actually tell me what the exact problem was when it bluescreened? Why even bother with the "pfn list corrupt" as if 90% of people even have a clue what that means? /rant

 

[Robvious82]

It's back with a vengeance. I cannot remember where to locate my minidump files or how to post them here...