BSOD making system unusable

DaleJrFan · 05 Jun 2015

Greetings;

I am at my wits end with this. Everything was running fine until about a week ago. I downloaded and tried to run the FlightGear flight simulator, which crashed every so often. My graphics software was a little messed up (the Catalyst Control Panel had gone bye-bye), so I reinstalled everything. My bad, I didn't uninstall first. Right after that, everything went ballistic. BSOD's, windows hung up, my graphics card would occasionally fail, you name it, I had it. My Win 7 system is so twitchy it bombs if I barely breath - other times it goes for an hour or more before crashing.

I used Guru's DDU (aka driver sweeper), got rid of the AMD drivers, reinstalled 2 different builds - even left out all the extras including CCC & Raptr - to no avail. Did the sfc /scannow thing (no effect, didn't have anything to fix), ran Memtest with no errors, even restored a back-up image I made 3 months ago - no effect. I even tried a repair install with my Win 7 upgrade disc (which I fooled into thinking it was upgrading Vista) which has worked before, but my system crashed before I got anywhere; I also tried a page file trick I picked up here, but that didn't help either. The system is stable in safe mode, which I've had to use with networking to go online.

I know, this is a long post, but I gotta add one more thing: I have a 2nd hd slaved to my computer running Win XP Pro SP3 that uses all the same stuff as my Win 7; when I swap over to that OS, it works like a charm; no faults, no crashes, beauty. So if the fault lies with my hardware, why is XP so stable?

Here's what I got using DM Log Collector. It's all Greek to me. Think if I can hold out till July 27, maybe Win 10 will make magic?

ICIT2LOL · 06 Jun 2015

Hello and welcome Dale now I am not sure why you are trying to fool the system with the upgrading?? For what it is worth why don't you just get an OEM 7 and have done with it because there are issues with updates in any case. There are some references to the memory not being accessed easily too.
Now as for the Windows 10 I hope you like it because (for example) my brother in the UK tried 8 on the 7 machine I made up for him managed it but didn't really like it and then ended up wanting to commit hari kari when he upgraded to 10 - the upshot was he reinstalled the original 7 that I gave him the disk for.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000109b, (reserved)
Arg3: 00010018, Memory contents of the pool block
Arg4: fea2a610, Address of the block of pool being deallocated
Debugging Details:
------------------
GetPointerFromAddress: unable to read from 831a684c
Unable to read MiSystemVaType memory at 83185f00
POOL_ADDRESS: GetPointerFromAddress: unable to read from 831a684c
Unable to read MiSystemVaType memory at 83185f00
 fea2a610 
BUGCHECK_STR:  0xc2_7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER:  from 97f102a4 to 8315dc6b
STACK_TEXT:  
9b2fbae4 97f102a4 fea2a610 00000000 fea2a644 nt!ExFreePoolWithTag+0x1b1
9b2fbb00 97ed01db fea2a610 00000000 fea2a610 win32k!HMFreeObject+0xb3
9b2fbb44 97ec8202 fea2a610 9b2fbb84 fe7d34f0 win32k!xxxFreeWindow+0x830
9b2fbb98 97f107c5 00000000 9b2fbbc0 97f0ff12 win32k!xxxDestroyWindow+0x534
9b2fbba4 97f0ff12 ff922508 00000000 fe7d34f0 win32k!HMDestroyUnlockedObject+0x1b
9b2fbbc0 97f0f8af 032af35e 00000000 00000001 win32k!DestroyThreadsObjects+0xa9
9b2fbc08 97f0d1bf 871e6510 871e6510 00f09500 win32k!xxxDestroyThreadInfo+0x467
9b2fbc1c 97f0d2dd 871e6510 00000001 871e6510 win32k!UserThreadCallout+0x77
9b2fbc38 832a6a59 871e6510 00000001 a71106d3 win32k!W32pThreadCallout+0x3a
9b2fbcb4 832ba6a3 40010004 871e7428 00000001 nt!PspExitThread+0x457
9b2fbccc 830ed380 871e7428 9b2fbcf8 9b2fbd04 nt!PsExitSpecialApc+0x22
9b2fbd1c 83079960 00000001 00000000 9b2fbd34 nt!KiDeliverApc+0x28b
9b2fbd1c 772e7074 00000001 00000000 9b2fbd34 nt!KiServiceExit+0x64
WARNING: Frame IP not in any known module. Following frames may be wrong.
03eaf898 00000000 00000000 00000000 00000000 0x772e7074

STACK_COMMAND:  kb
FOLLOWUP_IP: 
win32k!HMFreeObject+b3
97f102a4 668b460a        mov     ax,word ptr [esi+0Ah]
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  win32k!HMFreeObject+b3
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: win32k
IMAGE_NAME:  win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  55345e59
IMAGE_VERSION:  6.1.7601.18834
FAILURE_BUCKET_ID:  0xc2_7_win32k!HMFreeObject+b3
BUCKET_ID:  0xc2_7_win32k!HMFreeObject+b3
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0xc2_7_win32k!hmfreeobject+b3
FAILURE_ID_HASH:  {0eeb0e32-9ca3-f6c1-8bfe-526ea48c7963}
Followup: MachineOwner

DaleJrFan · 06 Jun 2015

I tried to reinstall 7 to see if it would fix my problems. My original system was an upgrade from XP to 7, that's why I have the upgrade disc. I don't see how using an OEM disc is going to make a difference. My system will still crash in the middle and I don't want to have to wipe my HD and start all over again; my older drive died last year and I had to buy a new one, install XP and then upgrade back to 7. I see a lot of blah, blah in the bugcheck but nothing to indicate what I can do to fix my system. Let's forget the attempt to repair install. What I want to find out is a) what went wrong and b) what can I do to fix it. Sorry, but I just don't understand what the analysis is saying; can you give me an explanation in plain English? Will I have to repeat what I did when I bought the new drive or is there another solution. Is buying an OEM of 7 and wiping my drive the only way? At this point I'm on the edge of selling everything as scrap and leaving the computer age entirely.

ICIT2LOL · 06 Jun 2015

Dale trashing the machine is too drastic and simplistic the dumps are full of issues and to be honest it would take a long time to go through the lot.
Now personally I would get say an SSD for the boot or larger spinner and install an OEM 7 onto it then transfer your data over to that drive. That way you are going to end with a system that is fresh and ready to go. I personally have never liked upgrades as I have had more than my fair share of problems using them.
While you are doing that the old drive should be removed / disconnected. I know it is a bit of work to do but for the time it takes to do that it will save you a lot of grief.

Someone else might see this thread and know a better way but that is how I see it.

DaleJrFan · 06 Jun 2015

Well, I can see your point. I guess I'll just have to bite the bullet on this one. I have a 1TB USB drive I can use to transfer all the critical files to, but I'd hate to give up on a less than 1 year old 320GB HD. Suppose I can lay my hands on a fresh, bootable OEM install - I could still use the disk, just wipe the partition and start fresh. Then transfer and/or reinstall my data and software. Done it before, I 'spose I can do it again. It's a matter of money, really: I can swing the cash for a new drive OR the 7 OEM, but not both. Unless Tiger Direct has a REALLY good price on an SSD; I THINK I've got a free SATA connection on this dinosaur of a motherboard.

If you can refer someone to this post who might have any alternatives, I'd sure appreciate it. Meanwhile, I'll see what I can do about your suggestion. Thanks and cheers. I'll mark this solved and rep you as soon as I can.

ICIT2LOL · 07 Jun 2015

Yep well I think that is the only option Dale now if you can borrow a 7 media disk then there are ways of downloading the OS onto a new drive using the ei.cfg removal tool - see this tutorial - as long as you use the original activation code and version.
https://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html <read the section Microsoft Software Recovery in Step 1 it sounds involved but is not in reality just a bit time consuming. But at least it will save you having to buy another OEM.

Your board only has two SATA ports P4M900-M7 FE :: Motherboard :: BIOSTAR and I suspect one would be for the optical drive one for the hard drive. So I suppose this limits you to either a 250GB SSD or a decent 500GB spinner (7200rpm) there are hybrid drives however that are a tad quicker - see this listing Search Results for hybrid hard drives at TigerDirect.com+ I have installed these before and although they say they are a lot quicker than SSD's they really are not THAT much quicker but better than a straight spinner - Seagate is my recommendation.

Anyway see what you think about this alternative.

DaleJrFan · 28 Jun 2015

Well, I don't know if you are still following this thread, but I have tried your suggestion about the OEM, etc and still have the same problem; no matter how I try to do it, the install crashes to a blue screen and fails. I've tried using a DVD & USB boot, but it just doesn't want to work. Just for gits & shiggles, I moved XP to the 320 gig drive & tried installing Vista on the smaller, 80gb hard drive and IT'S giving me the same symptoms that 7 developed! Appears that before I can run 7, 8 or 10 I'm going to have to do a total re-build (motherboard, HDD's, memory, basically a new computer) & make sure it's totally compatible

Thanks for your help, mate. Is there anyway to mark this not-quite-but-sort-of-solved?

ICIT2LOL · 29 Jun 2015

Hiyya Dale no need to solve it and sorry but I didn't get an email alert for your thread - must have been a glitch somewhere.

Yes mate I think a new build would the best way to go and if you are not looking for anything real fancy it can be reasonably inexpensive. Personally I would aim at an Intel based build.