 | |
| |
| 03 Aug 2010 | #1 |
| | BSOD Hi guys. I'm new to the forum but I wanted to post to say I am getting very similar (or what I think is similar) BSoD as the OP. I also too have only recently built this system about 4 months ago so is a relatively new build. I get main MEMORY_MANAGEMENT blues and BAD_POOL_HEADER. However I do get quite a few others. Looking at the dumps from an uneducated PoV, I seem the memory management ones are all for rdyboost.sys. Not sure if this means much. I have done 3 fresh installs on a 1TB drive and have removed all non essential hardware and still getting the problems. I have done the Windows memory checker with no faults and I did MemTest86 for 7 passes with no errors. Corsair have said they won't point the finger at my RAM but will replace it if I want. I would rather avoid that if I can as that will take a couple of weeks for them to process. I have attached the dumps, be ready though - there is alot of them, also there are a few in there dated June. I reset the BIOS and forgot to change date before I did a Windows reinstall. Sorry to hijack your thread aswell by the way buddy! |
My System Specs | |
| 03 Aug 2010 | #2 |
| | 
Quote: Originally Posted by berlioze  Hi guys. I'm new to the forum but I wanted to post to say I am getting very similar (or what I think is similar) BSoD as the OP. I also too have only recently built this system about 4 months ago so is a relatively new build. I get main MEMORY_MANAGEMENT blues and BAD_POOL_HEADER. However I do get quite a few others. Looking at the dumps from an uneducated PoV, I seem the memory management ones are all for rdyboost.sys. Not sure if this means much. I have done 3 fresh installs on a 1TB drive and have removed all non essential hardware and still getting the problems. I have done the Windows memory checker with no faults and I did MemTest86 for 7 passes with no errors. Corsair have said they won't point the finger at my RAM but will replace it if I want. I would rather avoid that if I can as that will take a couple of weeks for them to process. I have attached the dumps, be ready though - there is alot of them, also there are a few in there dated June. I reset the BIOS and forgot to change date before I did a Windows reinstall. Sorry to hijack your thread aswell by the way buddy! EDited to add: I asked the moderators to take your post and start a new thread for you. |
| My System Specs |
| 03 Aug 2010 | #3 |
| | All of your dump files but one are Driver Verifier enabled dumps. Unfortunately only one of the Driver Verifier dumps points to a particular driver. The rest blame Microsoft system drivers which is very unlikely. Most of the Driver Verifier enabled dumps blame pool corruption and memory corruption. Please turn Driver Verifier off at this time. The one dump that is not a Driver Verifier dump shows a stop error code of 7E. Quote: STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control Code: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_080310-14093-01.zip\080310-12187-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`03042e50 Debug session time: Tue Aug 3 17:27:21.453 2010 (GMT-4) System Uptime: 0 days 0:00:15.578 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff88001050090, fffff8800437b8d8, fffff8800437b140} Probably caused by : rdyboost.sys ( rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88001050090, The address that the exception occurred at Arg3: fffff8800437b8d8, Exception Record Address Arg4: fffff8800437b140, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94 fffff880`01050090 440fb702 movzx r8d,word ptr [rdx] EXCEPTION_RECORD: fffff8800437b8d8 -- (.exr 0xfffff8800437b8d8) ExceptionAddress: fffff88001050090 (rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x0000000000000094) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 Attempt to read from address 0000000000000000 CONTEXT: fffff8800437b140 -- (.cxr 0xfffff8800437b140) rax=000000000019d370 rbx=0000000000000000 rcx=00000000000183fc rdx=0000000000000000 rsi=fffffa800bed2178 rdi=fffffa800bbc29a0 rip=fffff88001050090 rsp=fffff8800437bb10 rbp=0000000000000001 r8=0000000000000000 r9=00000000ffffffff r10=000000000011aa87 r11=0000000000000001 r12=fffffa800bed2160 r13=000000000018ae60 r14=0000000000001000 r15=fffff880009b7140 iopl=0 nv up ei ng nz ac pe cy cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010293 rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x94: fffff880`01050090 440fb702 movzx r8d,word ptr [rdx] ds:002b:00000000`00000000=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: NULL_DEREFERENCE PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ad0e0 0000000000000000 FOLLOWUP_IP: rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94 fffff880`01050090 440fb702 movzx r8d,word ptr [rdx] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff88001052894 to fffff88001050090 STACK_TEXT: fffff880`0437bb10 fffff880`01052894 : 00000000`00000000 fffffa80`0ca38060 fffffa80`0dbd0900 fffffa80`0ca38000 : rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x94 fffff880`0437bb50 fffff880`0105b607 : 00000000`0000000a 00000000`00000001 fffffa80`0dbd0900 fffffa80`0bed20b0 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageRemove+0x30c fffff880`0437bc80 fffff880`0105a3fe : fffffa80`0dbd0900 00000000`00000080 00000000`00000080 fffffa80`0bed2f88 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x22f fffff880`0437bce0 fffff800`0311aa86 : 00000000`00000000 fffff880`00000000 fffffa80`0bba4b60 fffffa80`09cfb9e0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152 fffff880`0437bd40 fffff800`02e53b06 : fffff880`009b2180 fffffa80`0bba4b60 fffff880`009bd1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0437bd80 00000000`00000000 : fffff880`0437c000 fffff880`04376000 fffff880`0437b820 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94 FOLLOWUP_NAME: MachineOwner MODULE_NAME: rdyboost IMAGE_NAME: rdyboost.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc48a STACK_COMMAND: .cxr 0xfffff8800437b140 ; kb FAILURE_BUCKET_ID: X64_0x7E_VRF_rdyboost!B_TREE_unsigned_long,ST_STORE_SMD_TRAITS_::_ST_REGION_ENTRY,4096,NP_CONTEXT_::BTreeSearchKey+94 BUCKET_ID: X64_0x7E_VRF_rdyboost!B_TREE_unsigned_long,ST_STORE_SMD_TRAITS_::_ST_REGION_ENTRY,4096,NP_CONTEXT_::BTreeSearchKey+94 Followup: MachineOwner --------- http://www.sevenforums.com/crashes-d...uring-use.html I find two out of date drivers on your system. I recommend updating these. Update them form than manufacturers' websites rather than using Windows Update or Device manager. 000.fcl Fri Sep 26 09:11:22 2008 - FCL Driver or Power Control [2009/08/05 18:02:32] or Power Control [2009/05/16 07:18:01] or Power Control [2009/05/11 22:49:34] belongs to the software {22D78859-9CE9-4b77-BF18-AC83E81A9263} or CyberLink FCL Driver or My Book Device Driver or PowerDVD Ultra or CyberLink PowerDVD or OpenOffice.org by Cyberlink Corp (www.gocyberlink.com). Update this driver or the software it is associated with. Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver Realtek Disable Driver Verifier, reboot, update these two drivers, reboot and run your system. Then let's see where you are. Post any new BSOD's and we will have a look. If you need assistance, please post. What antivirus and firewall are you using? |
| My System Specs |
| . |
| |
| 03 Aug 2010 | #4 |
| | Hey Carl, Thanks for looking into this with me, really appreciate it. WHat is interesting is that all of those dumps I posted should be driver verifier disabled as I only just enabled it last night. When I enabled it, I was unable to even get into Windows as I kept getting a ndis.sys stop screen. When going into safe mode, that gave me a stop screen aswell. What I can also say is that I decided to try a different Windows OS to see what happens and I installed an old copy of XP Home SP2 that I have and that is working fine with no BSoD as of yet. Just also to clarify on the 7E stop screen, where you have your usual causes, I know it's not insufficient disk space as I have over a terabyte of free space spread over 3 drives. I know it can't be the video card as I removed this physically and used the onboard and still got a blue screen. I have done enough memory checks to be happy that they are not the suspect, and really the system services should be fine as I did 3 fully clean installs. What does interest me is you saying that there was a Realtek driver out of date, now that wouldn't be the ndis.sys would it, but I'm sure they would be related. I also assume that the driver would be for an ethernet connection and not a wireless connect. I don't use ethernet and the driver was automatically obtained by Windows. Lastly, just so you know, I don't use any anti-virus on firewall. Defender keeps in check spyware and such and I know what sites I go onto. |
| My System Specs |
| 04 Aug 2010 | #5 |
| | ndis.sys is a Windows networking driver, but the Realtek one is the driver for the network adapter. Be sure to update that one, even if you don't use it. Windows Defender is not adequate protection. Be sure to install Microsoft Security Essentials: http://www.microsoft.com/security_essentials |
| My System Specs |
| 04 Aug 2010 | #6 |
| | Well, as I said XP is working fine so I confident it is a software problem rather than hardware which makes me feel a bit better! I will reinstall 7 now, see how I get along and will let you guys know after I jave vetted all the drivers and made sure each 1 is up to date. Also Jonathan, I didn't realise there was something like that available from Microsoft for free otherwise I would already have it! Thanks mate. |
| My System Specs |
| 04 Aug 2010 | #7 |
| | Right, I reinstalled Windows 7. The first thing I did was install the drivers for my wireless card as they don't get found automatically. This was from a supplied CD and there are no other updated drivers for it. As soon as that had done I went to open device manager and then got a stop screen with BAD_POOL_HEADER (dump attached). How can it already be doing stuff wrong? Also, I just checked to update the automatically supplied Realtek driver and it is nVidia nForce in device manager and tells me there is no new software for it. I have disabled it for now. |
| My System Specs |
| 04 Aug 2010 | #8 |
| | It now looks as if your Atheros drivers are the cause. Dated 2008, they are well suited for BSODs. If you can't find any updated drivers for the card, the next step would be to purchase a card that is compatible with Windows 7. |
| My System Specs |
| 04 Aug 2010 | #9 |
| | Mr King, I think I may have solved half the problem then. I check on the Abit website as it is a PCI-E Airpace Wifi. They don't supply Win 7 drivers and it was installing Vista drivers from CD. Quick search on this very forum and found out it is just an Atheros AR5006XS, so have installed the Win 7 driver built in so we will see how this goes. What still concerns me is that I was still getting the odd BSoD before I purchased this WiFi card which was only about a week ago. I will see how it goes and let you all know. Thanks. |
| My System Specs |
| 04 Aug 2010 | #10 |
| | Right, it was fine for about an hour. As soon as I went to install the official Creative driver for my SoundBlaster X-Fi, I got another blue screen. Dump attached. |
| My System Specs |
