Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

BSOD Bad-pool-header on new custom pc


  • Please log in to reply

#1
seanstgermain1

seanstgermain1

    New Member

  • Member
  • Pip
  • 1 posts
I recently built my first gaming pc and after about a week of running I started encountering random occurrences of BSOD. The pc would always reboot again so I ignored it at first. I then noticed it more often usually while playing pc games or while running the internet. I was told by a friend to check and see if any drivers needed updating so I downloaded slimdrivers to see if this would help. I was also recommended to try cleaning the registry so i downloaded ccleaner and attempted that. The BSOD has occurred twice today alone. The latest BSOD said BAD-POOL-HEADER. Any help regarding this issue would be greatly appreciated.

My PC:
Intel i5 2500k cpu
MSI P67a-GD65/P67A-GD55/P67AGD53/P67S-GD53/P67a-SD60(one of these)
gigabyte 560 Ti video card
8 gig corsair vengeance ram
1TB seagate green
  • 0

Advertisements


#2
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
1. Welcome to Geeks to Go

2. I am sorry you have waited longer than we would wish for a reply
Sometimes this happens due only to the vast number of posts and one occasinally gets overlooked

3.

so I downloaded slimdrivers to see if this would help. I was also recommended to try cleaning the registry so i downloaded ccleaner and attempted that.

I regret that you have been given BAD advice

CCleaner is an excellent program, but generally speaking the registry cleaning aspect should not be used.

Even the file cleaning aspect of CCleaner requires knowledge as it deletes the log records of Micorosft Security Essentials which results in that program thinking something is wrong.
It also deletes records relating to Avast AV

Programs which monitor your drivers and recommend changes are OK providing that you VERIFY the recommendation with the motherboard, video card etc site, or in the case of an OEM computer such as Dell etc - recent model with that site.
It is NOT unknown by any means for the wrong driver to be recommended.

4.

so I ignored it at first

That is never a good idea, to ignore BSOD.
At the very least it is time to ensure that backup is up to date

5. Please provide the details of the crash using this
http://www.resplende...com/whocrashed/

free edition click analyse tab
copy and paste the results please
Intro is not needed simply crash reports and their conclusion.
Please do not attach as a file but as a copy and paste.

6. In view of the fact that you say after about a week
What new software, changes, overlclock etc ties in with this please.
  • 0

#3
seanstgermain11

seanstgermain11

    New Member

  • Member
  • Pip
  • 8 posts
I apologize for the wait. I had some issues with signing in. I ran whocrashed and this is what was reported:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 7/1/2012 10:53:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA8007572800, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/1/2012 10:53:30 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA8007572800, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
  • 0

#4
seanstgermain11

seanstgermain11

    New Member

  • Member
  • Pip
  • 8 posts
Within a week of the build I only added a couple new programs:
AVG2012 anti virus (free edition)
The witcher2 (game)
and some random program Super-charger.exe ( I believe it has something to do with the motherboard)
  • 0

#5
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
1. Turn Driver Verifier OFF please I think you have used it. It runs until you turn it off.
http://www.sevenforu...le-disable.html


2. Uninstall AVG 2012
Programs and features and then this please
Run the tool after the usual uninstall from programs and features.
Ensure you select the correct tool please

http://www.avg.com/ww-en/utilities

Install this please
http://windows.micro...rity-essentials

PLEASE DO NOT THINK that I am being so bold as to tell you which anti-virus to use.
You may of course select as you wish after we have solved your problem - hopefully,.
However for the time being please do as I ask
There are many reports of AVG2012 causing problems
I am not saying it is the cuase of YOUR problems, but lets eliminate it for the time being.


3. Check device manager for any warnings on drivers, click the view tab show hidden devices to ensure you have the view of all including the non plug and play drivers
If errors either deal with them please or post details if you require further advice

4. Run a chkdsk /f please on C Drive if of course that is the system drive
You mazy do this on cmd prompt or on the GUI of Computer by right clicking your drive, properties, tools, error checking

5. Run a system file check
sfc /scannow on cmd prompt

6. If CCleaner is commissioned to run at boot. Cancel it. In fact I recommend that on Windows 7 you do not use it at all
I could provide ample evidence of why not.
I have already mentioned two reasons.
It is a good program, but runnning it without knowing the implications is risky.

7. If you do NOT have automatic updates set
Update JAVA
Flash Player
From Control Panel and
ADOBE from the Help tab of the Adobe reader if you use it.

8. Go ot the motherboard site
Check for any driver updates STARTING with the updates for the chipset
Then the LAN Network driver
and the Audio driver.


Post back please when you have done these. Also include please the driver version installed for the Gigabyte 560
AND which AV did you have please before you installed AVG
  • 0

#6
seanstgermain11

seanstgermain11

    New Member

  • Member
  • Pip
  • 8 posts
Okay so i performed most of your tasks and every thing seemed to be going pretty well. I performed all except the system check, whick said something about have to be an admin and the turning of the driver verifier, in wich a performed all the steps but a window popped up saying no changes had been made. The computer ran fine and faster for a couple days and then crashed again. AVG has been the only anti virus on the pc since being built. Not sure on the gigabyte driver.

Here is the report:
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 7/10/2012 4:22:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-15444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80033A4D00, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 7/10/2012 4:22:18 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x23BF2)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80033A4D00, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 7/6/2012 9:36:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070612-19375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x411, 0xFFFFF680003AAE40, 0x4E00, 0xFFFFF68000000003)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/1/2012 10:53:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA8007572800, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#7
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
1. Driver verifier
Posted Image

right click the entry when it appears as in the top of the im age above and click run as admin.

2. the system file check
type cmd
and when it appears above right click again and click runs as admin

3. Did you run the chkdsk please
if so please check the results
Control panel
Event Viewer
Windows logs in left pane
Application
and then find in right pane and type
chkdsk
find the entry relating to that chkdsk and if you are in any doubt copy and paste

4. Not sure on gigabyte driver - please explain

5,. AVG may have been the only AV but please do uninstall and install MSE
You can change it back afterwards if you so desire
I need you to do that to eliminate it as a possible


6. Did you check device manager for me please

7. Please run this and post the URL
http://www.piriform....speccy/download

THE FREE edition
Here is how to send me the URL so that I may look at Speccy
  • 0

#8
seanstgermain11

seanstgermain11

    New Member

  • Member
  • Pip
  • 8 posts
1. I turned off the driver verifier

2. Then I ran the system file check twice and when it got to 44% done a message appeared saying it would not contine because of microsoft security program

3. Here is the CHKDSK report:

Log Name: Application
Source: Chkdsk
Date: 7/10/2012 4:53:34 PM
Event ID: 26212
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Sean-PC
Description:
Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
169984 file records processed.

File verification completed.
391 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
219526 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
169984 file SDs/SIDs processed.

Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
24772 data files processed.

CHKDSK is verifying Usn Journal...
33899144 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
149213988 KB in 137471 files.
91608 KB in 24773 indexes.
0 KB in bad sectors.
299679 KB in use by the system.
65536 KB occupied by the log file.
827052132 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
206763033 allocation units available on disk.

Event Xml:
<Event xmlns="http://schemas.micro.../events/event">
<System>
<Provider Name="Chkdsk" />
<EventID Qualifiers="0">26212</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-07-10T23:53:34.000000000Z" />
<EventRecordID>6275</EventRecordID>
<Channel>Application</Channel>
<Computer>Sean-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
169984 file records processed.

File verification completed.
391 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
219526 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
169984 file SDs/SIDs processed.

Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
24772 data files processed.

CHKDSK is verifying Usn Journal...
33899144 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
149213988 KB in 137471 files.
91608 KB in 24773 indexes.
0 KB in bad sectors.
299679 KB in use by the system.
65536 KB occupied by the log file.
827052132 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
206763033 allocation units available on disk.
</Data>
<Binary>00980200D0790200EDC70400000000009D4600004C0000000000000000000000</Binary>
</EventData>
</Event>

4. STill looking for current gigabyte driver

5. I also checked the device manager, with no errors reported

6. I downloaded speccy but I'm not sure how to give a url. I was however able to save it as text file.

7. I also uninstalled avg first and then installed microsoft security essentials.

Edited by seanstgermain11, 13 July 2012 - 06:28 PM.

  • 0

#9
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
1. Sorry my mistake missed off the link on post 7 - how to post speccy url

http://www.piriform....file-to-the-web

2 Re chkdsk

Run a chkdsk /f please on C Drive if of course that is the system drive
You may do this on cmd prompt or on the GUI of Computer by right clicking your drive, properties, tools, error checking


WARNING! F parameter not specified.
Running CHKDSK in read-only mode.


3. I really do need that Speccy report.

If you post it as soon as you have it I will look and post back before 1800hrs it is now 0148hrs.

4. I have to admit that I have not encountered that report on the system file check. It is not unknown for the sfc to report that errors cannot be repaired, although it is more unusual on Windows 7, due to the excellent backups built into the system files data base. I have not however come across that report that it cannot be completed due to a Microsoft Security program.
  • 0

#10
seanstgermain11

seanstgermain11

    New Member

  • Member
  • Pip
  • 8 posts
I found the gigabyte drivers:
NVIDIA Update 1.5.20
3D Vision Controller Driver 285.62
hd Audio Driver 1.2.24.0
Graphics Driver 285.62
3D Vision Drive 285.62

and i think the piriforms how to link is bad. I can't get a site to pop up

Edited by seanstgermain11, 13 July 2012 - 06:59 PM.

  • 0

Advertisements


#11
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Link now OK

Was that the exact message on the sfc /scannow - could you kindly run it and post the exact message received. - when you get chance please.


  • 0

#12
seanstgermain11

seanstgermain11

    New Member

  • Member
  • Pip
  • 8 posts
Here is the speccy url: http://speccy.pirifo...sSQjMzrvvdxkzzW
  • 0

#13
seanstgermain11

seanstgermain11

    New Member

  • Member
  • Pip
  • 8 posts
Heres the report from the system file scan.

"Beginning verification phase of system scan.
Verification at 97% complete.

Windows Resource Protection could not perform the requested operation."

It made it to 97% instead of 44 percent this time but the message is the same. And again thank you for your time and help with this matter.

Edited by seanstgermain11, 13 July 2012 - 07:21 PM.

  • 0

#14
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
I am signing off - goodnight

PLEASE do not run CCleaner it deletes - by default - the log setttings for Microsoft Security Essentials and will cause problems.

It is not only MSE that CCleaner efects it also deletes by default settings related to other anti virus programs.

I refer not to the registry cleaning aspect, but to the general use of CCleaner. My post 2 refers

I will post back as promised.
  • 0

#15
seanstgermain11

seanstgermain11

    New Member

  • Member
  • Pip
  • 8 posts
Just for the [bleep] of it I attempted another system file check. This time it went to 100% completion. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log windir\logs\CBS\CBS.log. For example C:\Windows\logs\CBS\CBS.log
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP