The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Win 7 Non-Stop Bluescreen Parade
HadjiQuest
Registered User regular
Registered User regular
So I installed Win7 last night, making it my first 64 bit OS. I had been on Vista since its first Service Pack, and I loved it. I accidentally received a trojan from some.... dubious software (I did it semi-purposely because I had the Win7 disc on hand). So I reformatted, and installed Windows 7.
Unfortunately, every few hours I've been bluescreening since the install. The reasons given on the blue screen are always different (sometimes win32k.sys, sometimes page memory, sometimes other things; always with different hex codes, 10e, 1F, 16e, 4e, and 3b are some of the ones I've written down). At first I thought it was a graphics driver issue, so I updated. No dice, still crashing.
Before the video drivers, it was kind of random. Now it's definitely happening when I load up Google Chrome with too many tabs at once, as well as some far-stretched random occurrences.
Here are my System Specs:
Athlon 64 X2 4400+
3GB DDR2 800Mhz RAM
Radeon HD 4670
And, of course, Windows 7 Professional 64bit.
Any help, folks?
Unfortunately, every few hours I've been bluescreening since the install. The reasons given on the blue screen are always different (sometimes win32k.sys, sometimes page memory, sometimes other things; always with different hex codes, 10e, 1F, 16e, 4e, and 3b are some of the ones I've written down). At first I thought it was a graphics driver issue, so I updated. No dice, still crashing.
Before the video drivers, it was kind of random. Now it's definitely happening when I load up Google Chrome with too many tabs at once, as well as some far-stretched random occurrences.
Here are my System Specs:
Athlon 64 X2 4400+
3GB DDR2 800Mhz RAM
Radeon HD 4670
And, of course, Windows 7 Professional 64bit.
Any help, folks?
HadjiQuest on
0
Posts
Tomorrow, I'll grab some.
Still, how could that have happened if they were all fine and working yesterday on Vista?
I only have 3 sticks. Could that be the issue? Do I need even pairs (I know you're supposed to have even pairs, but I've been cheap and lazy and it worked A-OK on Vista).
Edit: The Task Manager says I have 3070MB of RAM total, but only 2172 available. My total page file is autoset at 3070.
Another possibility is that your Vista install had some driver which your 7 install is missing. All you can do make a list of what hardware you have and hunt for drivers, really.
I already reinstalled once, and that didn't help. Guess I'll hunt for drivers, and then run memtest tomorrow.
There's a pretty good guide for generating and looking at these files on XP here. There are instructions on how to get Win 7 to generate the minidumps here, but I can't quite find any articles on how to analyze them in Win 7 yet. I'm not sure if the XP method would still work, but it might be worth a shot.
I've also never had the same error code twice; it's always been different.
Memory or hard disk! Or gnomes!
Half lead me to think drivers, half lead me to think RAM. I'm probably going to go out soon and run some errands, I'll grab some CD and DVD-Rs for MemTest.
Also, I had my friend give me a copy of Win7 32bit. If it's a driver issue, I figure I'll probably be out of the woods with 32bit. I've been told the same key will work for either version; is that true?
Here's hoping I'm fine now. If not, then it will either be a RAM problem, or the OS just doesn't like my mobo, and I'll drop back to 32bit.
Seconding this. A bad RAM stick causes Firefox to crash constantly (and then, Firefox to crash my PC). I found this out by doing a memcheck at startup (I forget how, part of the loading BIOS, that'll report a problem if it finds one), and restarting my PC removing each stick one by one.
A lot of RAM dealers cover their RAM indefinitely, which is nice. Better that than a socket, of course.
Going to check out the dump, but this looks like a RAM issue after all. How can I tell which stick is bad?
Edit: Anyone know debug dumps well?
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005005, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000000000
Arg4: 00000000000002db
Debugging Details:
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
BUGCHECK_STR: 0x1a_5005
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002a8401d to fffff80002ad5f00
STACK_TEXT:
fffff880`05c46818 fffff800`02a8401d : 00000000`0000001a 00000000`00005005 fffff700`01080000 00000000`00000000 : nt!KeBugCheckEx
fffff880`05c46820 fffff800`02afc9cd : 00000000`00002ef8 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1ff2a
fffff880`05c46880 fffff800`02afc353 : 6f800000`67e11025 00000000`67e11121 00000000`0036f470 00000000`0012e600 : nt!MiCompleteProtoPteFault+0x2cd
fffff880`05c46910 fffff800`02af1d9e : 00000000`00000000 00000000`774491fa fffff680`003ba248 fffffa80`03a953f8 : nt!MiResolveProtoPteFault+0x1d3
fffff880`05c469b0 fffff800`02aeff23 : 00000000`00000000 00000000`774491fa 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1de
fffff880`05c46ac0 fffff800`02ad3fee : 00000000`00000008 00000000`7540028d 00000000`7efdb001 00000000`0000c06e : nt!MmAccessFault+0x343
fffff880`05c46c20 00000000`774491fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0012d8c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774491fa
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+1ff2a
fffff800`02a8401d cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1ff2a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x1a_5005_nt!_??_::FNODOBFM::_string_+1ff2a
BUCKET_ID: X64_0x1a_5005_nt!_??_::FNODOBFM::_string_+1ff2a
Followup: MachineOwner
To tell which stick is bad you need to remove all the sticks and try them one at a time
at some point while running memtest it will tell you if the ram has failed
This, rather than Chrome, is where the problem happened. Unfortunately, that's a pretty generic executable that's causing the BSoD. This could be driver and/or memory related. It's hard to say. I had this executable show up in my minidump files when I was getting BSoDs a few years ago, and swapping RAM solved the problem.
My advice would be to test each stick of RAM independently in Memtest. I realize you don't have access to CDRs right now, but you might be able to run the test off a bootable USB stick if you've got one and your motherboard is decently modern.
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002bad4c1 to fffff80002bac00e
STACK_TEXT:
fffff880`0673c610 fffff800`02bad4c1 : fffff900`c020a518 fffff900`c1dd6480 fffff900`c1dd6490 00000000`00000000 : nt!ExDeferredFreePool+0x182
fffff880`0673c6a0 fffff960`00174ac0 : 00000000`00000001 00000000`00000000 00000000`3a616c47 00000000`00000001 : nt!ExFreePoolWithTag+0x411
fffff880`0673c750 fffff960`000c9e43 : 00000000`00000001 00000000`390a06e1 00000000`00000001 00000000`00000001 : wi!FreeObject+0x40
fffff880`0673c780 fffff960`0017d317 : 00000000`390a06e1 fffff880`0673cc1f 00000000`00000928 fffff900`c00d3010 : wi!bDeleteFont+0xf3
fffff880`0673c7e0 fffff960`00174920 : 00000000`00000928 fffff880`0673cc00 fffff900`c00d3010 fffff880`00000000 : wi!NtGdiCloseProcess+0x137
fffff880`0673c840 fffff960`00174063 : fffffa80`04173a00 fffff880`0673cc20 fffff880`06730000 00000000`00001000 : wi!GdiProcessCallout+0x200
fffff880`0673c8c0 fffff800`02d5c5e1 : fffffa80`04173a60 00000000`00000000 00000000`00000000 fffffa80`04c38b60 : wi!W32pProcessCallout+0x6b
fffff880`0673c8f0 fffff800`02d36b3d : 00000000`c0000005 00000000`00000001 00000000`78457300 00000000`00000000 : nt!PspExitThread+0x2b1
fffff880`0673c9c0 fffff800`02a56a43 : fffffa80`045d20e0 fffffa80`00000000 00000000`00000000 fffffa80`045d2010 : nt!PsExitSpecialApc+0x1d
fffff880`0673c9f0 fffff800`02a56e80 : 00000000`003cf800 fffff880`0673ca70 fffff800`02d37710 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0673ca70 fffff800`02a791f7 : fffffa80`04c38b60 00000000`0160eaa8 fffff880`0673cbc8 00000000`00fb8004 : nt!KiInitiateUserApc+0x70
fffff880`0673cbb0 00000000`742a2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0160ea88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x742a2dd9
FOLLOWUP_IP:
nt!ExDeferredFreePool+182
fffff800`02bac00e 4c3910 cmp qword ptr [rax],r10
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+182
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
STACK_COMMAND: .cxr 0xfffff8800673bc30 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+182
BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+182
Followup: Pool_corruption
The way you're getting inconsistent stop codes and different image names in your minidump reports is exactly what happened to me when my memory went bad. I'd recommend replacing the modules if you can do that. In the short term, you can try just running with a lower number of sticks, as recommended above.
I can only assume that either my realtek drivers (for onboard sound and NIC) or my ATi Drivers are busted and just don't really work for 64 bit. I just don't really know what to do now. Tomorrow I'll probably reformat and drop down to 32bit instead of 64bit. I can't believe software and drivers are still so poorly designed for 64bit OSes, after so many years. It's just really frustrating to me.
Unless, could my RAM still be bad somehow? Could having an Odd number of sticks be doing it somehow?
I am about 75% sure it is a 450W Antec, and it is definitely from mid 2007. I'll check for sure tomorrow, but I'm about to sleep.
This is still really perplexing to me, and I'm just extremely frustrated. I am strongly considering a downgrade to 32bit, but it's kind of upsetting to me that I should have to stick to 32 bit at this point in the game. Then again, maybe it's just chrome?
When I jumped to x64 from x32 the driver support in Windows 7 was pretty much spot on. I only had issues with my Creative Soundcard, but that wasn't a BSoD causing issue. Unless you're running some really obscure stuff, and haven't updated the drivers, I'd be surprised if that's it.
A few things about Memtest: First, an error pretty much confirms that you've got something wrong with your memory. But! No errors does not mean you are problem free. There is a good chance that you're okay, but proving a negative is difficult. When I went through this crap, Memtest didn't tell me shit - No errors at all. I just bit the bullet and got new RAM, and my problems were solved. Second, a single pass of Memtest tells you nothing. You want to run it at least 8, if not 24 hours.
Lastly, just out of curiosity, you aren't overclocking, are you? Have you modified the memory timings or clockspeeds for memory or CPU in the BIOS? If you've got an overclock, it might not play well with Win 7.
Edit: I forgot to mention - If you're running three sticks of memory, but you're using DDR2, then you're going to be fine - The memory will just run single-channel by default instead of double channel. If you're running DDR3, then having three sticks is normal. Either way, it shouldn't cause you any grief, unless one of the slots on your mobo is acting up.
You need to take them out and run one at a time until you find the one that's bad.
There's really nothing more to this.
I do, but I'm not really sure if they've been installing correctly. Nowhere in Catalyst control center does it say 10.1, and my device manager says the drivers were created on 12-19-09.
I still really don't think it's my RAM, but I guess if the fresh install doesn't work, it will really be time to start pulling sticks. I just wish the crashes were at least more regular. I could end up pulling sticks and thinking I'm fine afterward, because I can go up to 12 hours between blue screens.
The reason this didn't happen before is because 7 is utilizing your RAM differently than Vista. It's fairly common for these types of problems to be discovered upon switching operating systems. Maybe before, in Vista, those sectors weren't used very much? Maybe they held a system file that was hardly ever read from RAM.
Different error message every time for different programs? RAM! Whatever happens to be assigned to those sectors aren't being read back properly, causing a bluescreen.
Chrome crashes when you start loading up tabs? RAM! Each tab uses more space in memory, you finally get to that messed up spot with the nth tab.
If it was the same program or same error code every time it would not be your RAM. I don't understand how to stress this enough, reinstalling is not going to fix your problem. Drivers aren't going to fix your problem. You need to test your RAM. Memtest can be done from a USB memory stick, google it.
I ran Memtest for 3 hours last night with 0 errors, that's why I didn't think it was my RAM.
When I was having BSOD errors, 12 hours of Memtest didn't give me a single reported error. But when I got new sticks and everything was golden. A Memtest error means you have a problem - No errors in Memtest does not mean that you do not have a problem.
Also, keep in mind that there are more tests available than just the ones that automatically run. You might do well to put it through a few more passes with some of the more advanced options (Don't run bitfade, though).
The way the faulting module keeps jumping around on your minidumps seems to indicate you've got a memory, or a motherboard memory slot error, in my opinion.
Again, are you overclocking? Are your memory timings and speeds at stock? Even if an overclock was running stable on one OS, it might give you problems when you switch to a new one.
I pulled a stick of Ram at random. Going to see what that does for me.
Later, I put the stick back into a different slot and left my machine running overnight. No crashes.
Bad slot, then? How would I be able to test that?
I'd really like to add more RAM now that I'm 64bit, but it'd just be a waste of cash if the slot's the problem.
To my experience, there's no way to test the mobo other than what you've already done, unless you've got some sophisticated diagnostic hardware. I could be wrong about that. EDIT: To be sure, you might try running with a stick different from the original one in the 'bad' slot. If you get a crash, at least then you'll be reasonably more confident it was the slot and not the memory that was in there.
Honestly, though, you can upgrade your RAM without using that slot if you want to. Grab a two-pack of 2GB DDR2 sticks. You can get them for as low as ~$80 on Newegg.
The advantage here is that, if you use the paired slots that don't involve your damaged one (they should be color coded), you can run dual channel instead of single channel. Also, you'll not have to sacrifice any RAM for the error you're experiencing. 4 GB should be good for a while, too. If sometime down the line you need more than 4 GB, you'll probably be better off getting a new CPU and mobo anyhow.
Yeah, exactly.
Well, so far so good. I'm still going to order another 1gig stick since I need to get a few things online, anyway, but it does seem to be the slot so far.
Once I was unable to install any OS to my machine, it always got stuck while copying the install files... It was
RAM
It's always RAM.