Troubleshooting BSODs

[Duke{CLR}]

Yesterday when I got home from my trip I found the monitor, mouse, keyboard and speakers that will be gong along with the computer that I made for my friend. I set it all up and figured I would give it a workout with a little BC2. To my dismay I had 4 BSODs. The first two I don't remember too much about the conditions but I went to stock speeds and gave it try only to have two more. One happened while adjusting the sound quality settings and the other happened while talking on TS. I also had a BSOD when I first played BC2 on it but I thought it was because I had it OCed.

I updated the drivers for my audio and during this process I noticed that windows had installed a driver during the restart, is there a way to prevent this?

I looked for driver sweeper but it seems to be discontinued What can I use to scrub the old drivers off to be sure that I ave a clean install?

I found these dump files now what do I do with them?
http://dl.dropbox.com/u/3526765/053011-18096-01.dmp
http://dl.dropbox.com/u/3526765/061511-13790-01.dmp
http://dl.dropbox.com/u/3526765/061511-14305-01.dmp
http://dl.dropbox.com/u/3526765/061511-14757-01.dmp
http://dl.dropbox.com/u/3526765/061511-18018-01.dmp

I also ran a windows based memory test and it said there were no errors.

Any thoughts?

[juneau]

BSOD's are usually caused by RAM issues or drivers.

It would appear that you've eliminated option one so now it's onto the drivers.

Driversweeper is still going, however it's not partnered with guru3d anymore. You can download it from here.

Phyxion.net - Driver Sweeper

[Donziboy2]

Well i use This to help me read the dmp files.

I checked the first one and you have the same problem I had. Which is punkbuster fecking things up.

I actually had the same problem after putting my new rig togeather it would bsod in bc2. After figuring out how to read the dumps i found it was punkbuster.

Pretty sure you need to uninstall PB and then reinstall it. From what i see in the dump you have Win 7 like me and the PB file is a VISTA file....... Completely remove PB from the machine and reinstall it.

[Duke{CLR}]

Thanks guys I will get that driver sweeper and reinstall PB, heck I may even go over to a similar post on the Steam forums and post up this resolution and make myself look smart.

[Duke{CLR}]

I can't seem to find the path for Bc2 through Steam?

[Duke{CLR}]

I got PB up and running and was able to play a bit, because i thought it was stable I alt tabbed out ran Precession, TS and plugged in my wireless headset and started to play, 30 second later BSOD. I think I threw too much at it.

http://dl.dropbox.com/u/3526765/061611-17019-01.dmp

[Donziboy2]

Still getting punked by punkbuster....

Are you running any overclocking software, or have any installed. I had to uninstall my gigabyte tools cause there was an OC tool that was conflicting with punkbuster.

Just looked at the build for your friend on a previous thread and your using the same MOBO as me so its most likely gigabytes oc program



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Downloads\061611-17019-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`0329f650
Debug session time: Thu Jun 16 11:26:25.473 2011 (UTC - 4:00)
System Uptime: 0 days 0:28:55.317
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
..........................
Loading User Symbols
Loading unloaded module list
.......
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007d8f028, bf800000, 200001}

Probably caused by : hardware

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

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: PnkBstrB.exe

CURRENT_IRQL: f

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

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

[Duke{CLR}]

Is it causing a conflict when I use TS or Precession or both?

[Duke{CLR}]

Donzi, thanks for the info on TS, I uninstalled that overclocking tool, hopefully I wont have any BSODs the next time I get to try it out which should be tomorrow night.

[Duke{CLR}]

After removing that software mini was able to play several hours with no BSODs so now I can give it to my large friend without worrying about getting my arse kicked.

Thanks Donzi i wouldn't have found this without your help.