|
Login to view full posting options
|
| Author |
Message |
Google
AdSense
|
|
| Back to top |
|
 |
jdub
nFHQ Member
Joined: 09 Oct 2004
Posts: 42
|
 Posted: Thu Mar 09, 2006 9:31 am Post subject: bad_pool_header - random reboots and blue screens |
|
|
|
I was hoping rebuilding my system would help solve some of the random reboots, which it kinda has, now I get blue screens of death mere instants before the reboot. Worse It doesn't happen during intense gaming anymore, before once battle peaked in W3 (video card and processor intensive) the comp would reboot, but now it seems to happen sporadically. Just now it happened while watching a simpsons episode. I managed to read bad_pool_header before she went down.
No I am not overclocking.
Here are the logs of the incident:
http://rapidshare.de/files/15055443/sysdata.xml.html
http://rapidshare.de/files/15055483/Mini030906-01.dmp.html
and the manifest.txt:
| Code: |
Server=watson.microsoft.com
UI LCID=1033
Flags=1696082
Brand=WINDOWS
TitleName=Microsoft Windows
DigPidRegPath=HKLM\Software\Microsoft\Windows NT\CurrentVersion\DigitalProductId
ErrorText=A log of this error has been created.
HeaderText=The system has recovered from a serious error.
Stage2URL=
Stage2URL=/dw/bluetwo.asp?BCCode=19&BCP1=00000020&BCP2=84C2A270&BCP3=84C2A298&BCP4=0A050003&OSVer=5_1_2600&SP=2_0&Product=256_1
DataFiles=C:\WINDOWS\TEMP\WER1df9.dir00\Mini030906-01.dmp|C:\WINDOWS\TEMP\WER1df9.dir00\sysdata.xml
ErrorSubPath=blue
DirectoryDelete=C:\WINDOWS\TEMP\WER1df9.dir00
|
So far I've installed the latest nvidia system drivers and the latest ATI (by the way they released the 6.3's as well as the avivo encoder today) I did have the 6.2's running earlier but had issues all over the place so I upgraded. As for firewalls I had the nvidia software/included hardware firewall installed but de-activated. I'm really not running many programs or services and I was still had an incident before I installed and ran the usual (azureus, daemon tools and one or two other odd programs)
My current specs:
Software:
OS: Windows XP SP2, all hotfixes, dotnet architectures etc.
System Drivers: Nvidia Nforce 4 6.70
Video Drivers: ATI Catalyst WDM 30895 (Direct X: 9.0c)
Java: Sun Java JRE 1.5.0_06 (usually running with Azureus)
Mobo: MSI K8N Neo4 Platinum
Video: SAPPHIRE Radeon X1600XT 100146-BL
Proc: AMD Athlon 64 3000+ (Venice) Cooler: ZALMAN CNPS7700-CU 120mm
RAM: KINGMAX SuperRAM 1GB
Case: Lian Li V COOL PC-V1000APLUS
PSU: ENERMAX Liberty ELT400AWT
Opticals:
#1: NEC Black 16X DVD-RW ND-3540A - discontinued
#2: Lite-On 52X CD-RW SOHR-5238S - discontinued
Hard Drives:
Sata: Maxtor DiamondMax 10 250GB
Sata: SAMSUNG SpinPoint P80SD 160GB (Discontinued)
Sata: HITACHI Deskstar 7K80 80GB - MIA
IDE - Maxtor DiamondMax 10 6L200R0 200GB - Current boot drive.
Last edited by jdub on Thu Mar 09, 2006 9:32 am; edited 1 time in total |
|
| Back to top |
|
|
Screwy
nForced
Joined: 07 Jul 2003
Posts: 1195
Location: England Surrey\Japan Osaka
|
| Posted: Thu Mar 09, 2006 10:12 am Post subject: |
|
|
|
You can find out what the stop code Error is by doing the following.
1. Click the Start button, right-click My Computer, click Properties, click the Advanced tab, and then click Settings under Startup and Recovery.
2. Under System Failure, view the Automatically restart check box. If the Automatically restart check box is selected, Windows automatically restarts if the computer stops unexpectedly.
Have you found out if this problem happen when in safe mode? if it doesn't it may be a driver or some kind of configuration.
Stop code may well be useful to anyone wanting to help. |
|
| Back to top |
|
|
wonkanoby
Ultra nForced
Joined: 18 Apr 2002
Posts: 8512
Location: sunny south london [catford]
|
| Posted: Thu Mar 09, 2006 11:01 am Post subject: |
|
|
|
| memtest your ram |
|
| Back to top |
|
|
wardog
Exited the premises.
Ultra nForced
Joined: 28 Jan 2003
Posts: 2512
|
| Posted: Thu Mar 09, 2006 12:42 pm Post subject: |
|
|
|
| Screwy wrote: |
| Stop code may well be useful to anyone wanting to help. |
Yes, please post the whole stop error.
On a side note, if you be so kind, PM me with your feelings/experiences with Hamachi. |
|
| Back to top |
|
|
wardog
Exited the premises.
Ultra nForced
Joined: 28 Jan 2003
Posts: 2512
|
| Posted: Thu Mar 09, 2006 2:07 pm Post subject: |
|
|
|
Also, what BIOS revision is your board at?
Edit: Because if I remember right, since MSI nForce drivers 6.65(6.66?) and above req'd one to be at or above a certian BIOS revision.
Last edited by wardog on Thu Mar 09, 2006 2:16 pm; edited 2 times in total |
|
| Back to top |
|
|
jdub
nFHQ Member
Joined: 09 Oct 2004
Posts: 42
|
| Posted: Thu Mar 09, 2006 8:02 pm Post subject: |
|
|
|
| Screwy wrote: |
You can find out what the stop code Error is by doing the following.
1. Click the Start button, right-click My Computer, click Properties, click the Advanced tab, and then click Settings under Startup and Recovery.
2. Under System Failure, view the Automatically restart check box. If the Automatically restart check box is selected, Windows automatically restarts if the computer stops unexpectedly. |
And how will that stop my random reboots and blue screens of death?
Sorry, I can't give the stop code as the second I get a blue screen my comp dies.
This doesn't happen terribly often and im not about to spend a week in safe mode just trying to figure out if it too expiriences problems. Heck I've been gaming all day without a hitch, but I fully expect a crash within the next day or so, something that never really came up before this started.
My BIOS revision is 11/28/05 - I upgraded it awhile back.
Last edited by jdub on Thu Mar 09, 2006 8:03 pm; edited 1 time in total |
|
| Back to top |
|
|
Screwy
nForced
Joined: 07 Jul 2003
Posts: 1195
Location: England Surrey\Japan Osaka
|
| Posted: Fri Mar 10, 2006 3:16 am Post subject: |
|
|
|
| Not saying it's going to fix your problem but as you stated when the error occurs your pc automaticlly restarts - If you deselect the (Automatically restart check box) you should have time to write down the error stop code, it's a step in the right directions. |
|
| Back to top |
|
|
wardog
Exited the premises.
Ultra nForced
Joined: 28 Jan 2003
Posts: 2512
|
| Posted: Fri Mar 10, 2006 8:58 am Post subject: |
|
|
|
| jdub wrote: |
| Sorry, I can't give the stop code as the second I get a blue screen my comp dies. |
Well, until you correct for and then post those stop errors here's some data for you to mull over.
C:\Program Files\Support Tools>dumpchk Mini030906-01.dmp
Loading dump file Mini030906-01.dmp
----- 32 bit Kernel Mini Dump Analysis
DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 006f1000
PfnDataBase 81000000
PsLoadedModuleList 805531a0
PsActiveProcessHead 80559258
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 00000019
BugCheckParameter1 00000020
BugCheckParameter2 84c2a270
BugCheckParameter3 84c2a298
BugCheckParameter4 0a050003
PaeEnabled 00000001
[burger] 80544ce0
MiniDumpFields 00000dff
TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000658
DriverListOffset 00003268
DriverCount 00000080
StringPoolOffset 00005868
StringPoolSize 00001188
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack f78ea9a8
[burger] 00002fd8
[burger] 00000290
DataBlocksOffset 000069f0
DataBlocksCount 00000003
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Mar 09 02:52:24 2006
System Uptime: 0 days 3:54:15
start end module name
804d7000 806cd280 nt Checksum: 001F632B Timestamp: Tue Mar 01 19:
34:37 2005 (42250A1D)
Unloaded modules:
f7a47000 f7a49000 splitter.sys Timestamp: unavailable (00000000)
f7b34000 f7b35000 drmkaud.sys Timestamp: unavailable (00000000)
a8590000 a859d000 DMusic.sys Timestamp: unavailable (00000000)
f7a4d000 f7a4f000 MSKSSRV.sys Timestamp: unavailable (00000000)
a8ac1000 a8acf000 swmidi.sys Timestamp: unavailable (00000000)
a757f000 a75a2000 aec.sys Timestamp: unavailable (00000000)
a7b26000 a7b50000 kmixer.sys Timestamp: unavailable (00000000)
a7c14000 a7c37000 aec.sys Timestamp: unavailable (00000000)
a7cef000 a7cfc000 DMusic.sys Timestamp: unavailable (00000000)
a7e9f000 a7ead000 swmidi.sys Timestamp: unavailable (00000000)
f79f3000 f79f5000 splitter.sys Timestamp: unavailable (00000000)
f7a62000 f7a63000 drmkaud.sys Timestamp: unavailable (00000000)
f79e7000 f79e9000 MSKSSRV.sys Timestamp: unavailable (00000000)
f79d5000 f79d7000 MSPQM.sys Timestamp: unavailable (00000000)
f79cf000 f79d1000 MSPCLOCK.sys Timestamp: unavailable (00000000)
aad82000 aad91000 sysaudio.sys Timestamp: unavailable (00000000)
aad42000 aad51000 drmk.sys Timestamp: unavailable (00000000)
f7b9a000 f7b9b000 drmkaud.sys Timestamp: unavailable (00000000)
a87c0000 a87ea000 kmixer.sys Timestamp: unavailable (00000000)
a87ea000 a880e000 portcls.sys Timestamp: unavailable (00000000)
a8c01000 a8c0e000 DMusic.sys Timestamp: unavailable (00000000)
a880e000 a8831000 aec.sys Timestamp: unavailable (00000000)
aad62000 aad70000 swmidi.sys Timestamp: unavailable (00000000)
f7a37000 f7a39000 splitter.sys Timestamp: unavailable (00000000)
f77cf000 f77d4000 Cdaudio.SYS Timestamp: unavailable (00000000)
f7075000 f7078000 Sfloppy.SYS Timestamp: unavailable (00000000)
Finished dump check
Last edited by wardog on Fri Mar 10, 2006 8:59 am; edited 1 time in total |
|
| Back to top |
|
|
jdub
nFHQ Member
Joined: 09 Oct 2004
Posts: 42
|
| Posted: Sat Mar 11, 2006 6:50 pm Post subject: |
|
|
|
| Screwy wrote: |
| Not saying it's going to fix your problem but as you stated when the error occurs your pc automaticlly restarts - If you deselect the (Automatically restart check box) you should have time to write down the error stop code, it's a step in the right directions. |
I always thought that was like the VPU recovery in ATI's drivers, only when the CPU is locked up. But yeah, now I see what you mean. thanks. |
|
| Back to top |
|
|
Radiohead57
--?--
nForced
Joined: 13 Jan 2003
Posts: 1125
Location: Ontario, Canada
|
| Posted: Tue Mar 21, 2006 11:01 am Post subject: |
|
|
|
| Go to control panel> administrative tools> event viewer> system tb and simply look for save dump messages. The most important are the last two numbers of the first sequence ie 7E, 4F, 0A, 050, C1 etc. Often these will at least allow you to narrow down exactly what the source of the problem is. |
|
| Back to top |
|
|
Google
AdSense
|
|
| Back to top |
|
|
|
|
nForcersHQ supporters: Impar, wardog, MiniMax, envoid, jasonh, Krips, VAIOMAN, Zetro, sensai, me&er, RElliott, ScottRempel, JHogarth, IcemanIX, Etraman, KA, Tabajara, Xiomberg, ruddywarrior, hookahmike, MMoore, RHodgson, RGilson, powerarmour, Sepal, RRavat, DigitalRuin, HammerheadTech, Bane, DHunt, Fat Jez, baikal, Jumpin' Jon, MGadzikowski, JBishop, RDeBok, JDavies, HDHyland, TMorris
|
|
| |
