Random BSODs while playing WoW/TF2, browsing internet.

[Tenack]

Okay so I bought a new HDD(installed Windows 7 on it) and PSU(750W) and i'm STILL having these problems. I've RMA'd my RAM and ordered new ones in desperation because this is just getting ridiculous. They pass Memtest but other forums tell me my RAM is the problem considering one instance on bootup my computer started beeping quickly and loudly and didn't bootup until I rebooted it.

I've tried uninstalling and updating EVERY driver I have and NOTHING changes. What is the deal? Why am I having so many problems? Why are peers of mine not having as many issues as I am when they have the same setup(except that I'm the only one with a Radeon Graphics card)?

I've also tried following the directions in driver verifier but nothing happens, windows just boots up as normal...then sometime later when playing a game or browsing the net I get a bluescreen.

The most frequent BSOD's I get are BUGCODE USB DRIVER and DRIVERIRQL NOT LESS OR EQUAL. Sometimes it just says "theres a problem and windows was shut down to prevent...yadda yadda". Why am I still having these problems? This is a BRAND new HDD!!!!

I've been dealing with BSOD's since SEPTEMBER. I'm so tired of dealing with this

 

[writhziden]

For the USB crashes, I suggest going through the steps for http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html.

It sounds like a driver problem of some kind. Drivers can be updated/re-installed, but there still may be a conflicting driver on the system. If you follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html, I will take a look at your crash reports and see if any drivers stand out.

 

[Tenack]

Thank you for your patience. I really appreciate it.

Here is the new zip file. I noticed in perfmon that it says devices are disabled. I haven't disabled any devices so I'm unsure how this happened, but maybe its what is causing the problem, idk.

 

[writhziden]

You're welcome.

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\BSODDmpFiles\Tenack\Windows_NT6_BSOD_jcgriff2\021712-37830-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`032a6670
Debug session time: Fri Feb 17 10:55:53.348 2012 (GMT-7)
System Uptime: 0 days 0:01:27.550
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 11e002, 5, 1}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000011e002, page frame number
Arg3: 0000000000000005, current page state
Arg4: 0000000000000001, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003166d7c to fffff800030ddc40

STACK_TEXT:  
fffff880`09a88638 fffff800`03166d7c : 00000000`0000004e 00000000`00000099 00000000`0011e002 00000000`00000005 : nt!KeBugCheckEx
fffff880`09a88640 fffff800`030853d7 : 95b00001`1e002025 fffffa80`035a0060 fffff880`09a88848 fffff680`0000a9e0 : nt!MiBadShareCount+0x4c
fffff880`09a88680 fffff800`0310fbb7 : fffff880`00000000 fffff680`0000a9f8 fffffa80`09673960 00000000`07000001 : nt! ?? ::FNODOBFM::`string'+0x3309d
fffff880`09a88830 fffff800`03111569 : 00000000`00000000 00000000`0153ffff fffffa80`00000000 fffff683`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`09a889f0 fffff800`033f5221 : fffffa80`09755010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`09a88b10 fffff800`033f5623 : 0000007f`00000000 00000000`01530000 fffffa80`00000001 00000000`00540001 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09a88bd0 fffff800`030dced3 : 00000000`00000008 000007fe`f35c6480 fffffa80`09673960 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f
fffff880`09a88c20 00000000`76d315ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`005ee0a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d315ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`03166d7c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------

[*]
Loading Dump File [F:\BSODDmpFiles\Tenack\Windows_NT6_BSOD_jcgriff2\021412-16692-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0304d000 PsLoadedModuleList = 0xfffff800`03292670
Debug session time: Tue Feb 14 15:42:29.054 2012 (GMT-7)
System Uptime: 0 days 0:01:05.381
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800031f8617, fffff88002192f00, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+537 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800031f8617, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88002192f00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExAllocatePoolWithTag+537
fffff800`031f8617 48895808        mov     qword ptr [rax+8],rbx

CONTEXT:  fffff88002192f00 -- (.cxr 0xfffff88002192f00)
rax=0000000000000000 rbx=fffffa800183e2c0 rcx=fffff8a00200e2d0
rdx=0000000000000038 rsi=0000000000000005 rdi=0000000000000001
rip=fffff800031f8617 rsp=fffff880021938e0 rbp=0000000000001000
 r8=0000000000000001  r9=fffffa800183e2c0 r10=fffffa800183e148
r11=0000000000000001 r12=fffffa800183e140 r13=0000000000000000
r14=fffffa8003df1b60 r15=0000000020206553
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ExAllocatePoolWithTag+0x537:
fffff800`031f8617 48895808        mov     qword ptr [rax+8],rbx ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  services.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800031f8617

STACK_TEXT:  
fffff880`021938e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x537


FOLLOWUP_IP: 
nt!ExAllocatePoolWithTag+537
fffff800`031f8617 48895808        mov     qword ptr [rax+8],rbx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExAllocatePoolWithTag+537

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff88002192f00 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExAllocatePoolWithTag+537

BUCKET_ID:  X64_0x3B_nt!ExAllocatePoolWithTag+537

Followup: MachineOwner
---------


[/list]

1. Possible causes are Memory problems... Drivers...
2. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...

Given the number of blue screen reports that were corrupted, I am suspecting that you have more than one problem going on. The reports that were corrupted pointed to a driver causing the crashes. Unfortunately, due to the corruption, it was impossible to determine which driver. I believe you have a driver conflict on your system, and I also believe either your hard disk has errors on it that are causing the .dmp files to be corrupted, or you have Windows system files that are corrupted leading to corrupted .dmp files. You may still have a memory module issue (either bad RAM or bad motherboard slots or just a voltage issue that we can easily correct). Right now, I would like to focus on the data corruption I am seeing.

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

 

[Tenack]

I can't even make a detailed post without it BSODing. I followed your directions. Ran CHKDSK, no problems found.No bad sectors. Ran SFC three times no problems.

Like I said I replaced the HDD and the RAM. I'm getting alot of SYSTEM SERVICE EXCEPTION errors now. Google searches says thats a video driver problem. But I've updated my AMD Radeon 6800 series driver multiple times! Nothing changes. Frankly I'm surprised its gone this long without BSODing, usually I can't even make out a post.

I've also ran Startup Repair and it says that it can't detect/fix any problems. When I get back to the desktop Windows "checks for a solution" but never does anything.

-.-

 

[writhziden]

Download and install CPUZ and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Also, go into your BIOS and post all RAM and CPU Voltages and all RAM settings (timings, frequency, etc.)

Thanks to Dave76 for help learning RAM Stability

 

[Tenack]

i uninstalled my video driver and i don't really have any problems when running my computer

 

[Tenack]

alright so i tried installing a freshly downloaded driver from AMD and i booted up a game and bam, BSOD. so i'll follow your directions and get back to you

 

[Tenack]

Here are the screens. Unfortunately while I know how to access the BIOS I know next to nothing about how to navigate it.

 

[writhziden]

If you are not comfortable navigating the BIOS, I would not recommend it out of fear that something may be changed accidentally and cause more problems. Unfortunately, this limits us in debugging and we will have to hope that it not the RAM causing the problems. Given the graphics problem, this may be alright. I am starting to think there may be an issue with the card itself.

Before we do testing of the graphics card, I have a question: when you replaced the HDD, did you do a format and clean install of Windows 7?

I remember you having errors showing up running sfc /scannow before the HDD replacement.

 

[Tenack]

I did not format/reinstall windows on the other drive because it has all my music and stuff on it. Haven't gotten around to snagging the data off of it.

I swapped out the Radeon HD 6850 for an old Radeon HD 5450 and the only problem I've gotten so far is a BAD POOL HEADER BSOD.

 

[writhziden]

That means you have an underlying driver problem. If you would like to sort it out, we can help.

 

[Tenack]

I'd love the help, you guys have been great.

 

[writhziden]

Run Driver Verifier to find driver conflicts. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​

The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

 

[RxDawg]

Tenack, I have the EXACT same problems. I mean I could cut and paste everything you've said. I'm convinced it has to do with our video cards. I'm also convinced it has something to do with windows updates. Not the updates themselves directly, but something they do makes everything else seem to start messing up. I say this because when my system gets so bad I have to just reformat everything and start from scratch. When I do this is runs like a champ... until I start updating stuff again. Now I'm no tech person, I just wanted to bring this up here so maybe it will help out. I'm following along in this post and trying the same suggestions.

edit: I wanted to add one more thing. I do not think it's specificly Radion ATI video cards. I had the same problems with a singular NVIDIA card a while back. That prompted me to try a new video card and so I decided to go with ATI crossfire dual cards. And that worked... for about 2 months and whatya know the BSODs are back.

 

[Tenack]

Yeah the updates say they fix instabilities in Windows but things seem to only get worse. After I installed my new HDD I had a few days of bliss until Windows forced an update. From that point on I've had nothing but problems until I put in my HD 5450.

I'll work on running Driver Verifier. I've already tried this before though. Hopefully I see some success this time.

 

[RxDawg]

I think it's really odd how the problem seems to progressively get worse over time. Eventually if I'm forced into another clean install, I think I'm going to turn off all windows updates and see how that goes. I just wish Microsoft would come out and say "oh sorry guys, we figured out the problem. download this patch and everything will be fixed." It's obvious this is a very popular problem.

 

[Tenack]

Alright I haven't run Driver Verifier yet, but I'm encountering black screen crashes(comp is still running, have to press the restart button on case to get a display again) even though I switched graphics cards. This is rather disappointing, as I wasn't having too many problems until now.

Hopefully this information is of assistance when I run driver verifier.

 

[Tenack]

Welp while posting that last post I got another BUGCODE USB DRIVER error.

My computer is just all kinds of ****ed up

 

[writhziden]

What peripherals are you using via USB?

Also, I have seen instances where USB errors occur due to out of date chipset drivers or outdated BIOS version. You BIOS is up to date, so it is probably not to blame. Check TA785G3+ :: Motherboard :: BIOSTAR for chipset driver updates. If you chipset drivers are up to date re-install them to rule out a corrupted driver or set of drivers.

You could also try reflashing the BIOS with the latest version to rule out a bad flash.

USB errors can also occur if the USB ports enter an invalid power state to protect themselves from a power surge.

1. Shut down and turn off the computer.
2. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
3. Hold down the power button for 30 seconds. This closes the circuit and ensures all power from components is drained to clear the software connections between the BIOS and hardware and clear any corruption in the temporary memory.
4. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall.
5. Turn it on to reinitialize the software connections between the BIOS and hardware, and post back your results.