Product: Windows Operating System
ID: 1003
Source: System Error
Version: 5.2
Symbolic Name: ER_KRNLCRASH_LOG
Message: Error code %1, parameter1 %2, parameter2 %3, parameter3 %4,
parameter4 %5.


i keep getting a stop error 0x000000f4 and i cant figure out how to fix
this. I"m running windows server standard sp2, it hall all updates. with
nothing running, i'll get a stop error F4.

any ideas on how i can fix this problem? it comes and goes, sometimes the
bsod happens after 12 hours and other times after a few days, but the server
is literally running nothing, very light load.
i checked my drivers and there are no conflicts and i'm up to date on all of
them.

Quote:

Product: Windows Operating System ID: 1003 Source: System Error Version: 5.2 Symbolic Name: ER_KRNLCRASH_LOG Message: Error code %1, parameter1 %2, parameter2 %3, parameter3 %4, parameter4 %5. i keep getting a stop error 0x000000f4 and i cant figure out how to fix this. I"m running windows server standard sp2, it hall all updates. with nothing running, i'll get a stop error F4. any ideas on how i can fix this problem? it comes and goes, sometimes the bsod happens after 12 hours and other times after a few days, but the server is literally running nothing, very light load. i checked my drivers and there are no conflicts and i'm up to date on all of them.

Any info in the event viewer as to specific app or file causing the
problem? How new is the server?

- Thee Chicago Wolf

Error code 000000f4, parameter1 00000003, parameter2 890aa128, parameter3
890aa28c, parameter4 8094c6e6.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


if i look in event viewer thats what i get.
its not much to go on and when i research the 0x000000f4 error, all the
hotfixes i see pertain to sp1.
i've submitted a ticket to microsoft but i've not heard back from them and i
dont think i will.

if i format my computer and put winXP all works fine but if i put win2k3
with sp2 i get bsod, using all certified drivers, i tried swapping out ram.
the motherboard is win2k3 certified.
is it a hardware error? how do i tell if its a service, program causing this
bsod or if its hardware issue or driver and the bsod does not tell me
anything.


"Thee Chicago Wolf" wrote:

Quote:

Product: Windows Operating System ID: 1003 Source: System Error Version: 5.2 Symbolic Name: ER_KRNLCRASH_LOG Message: Error code %1, parameter1 %2, parameter2 %3, parameter3 %4, parameter4 %5. i keep getting a stop error 0x000000f4 and i cant figure out how to fix this. I"m running windows server standard sp2, it hall all updates. with nothing running, i'll get a stop error F4. any ideas on how i can fix this problem? it comes and goes, sometimes the bsod happens after 12 hours and other times after a few days, but the server is literally running nothing, very light load. i checked my drivers and there are no conflicts and i'm up to date on all of them. Any info in the event viewer as to specific app or file causing the problem? How new is the server? - Thee Chicago Wolf

Quote:

Error code 000000f4, parameter1 00000003, parameter2 890aa128, parameter3 890aa28c, parameter4 8094c6e6. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. if i look in event viewer thats what i get. its not much to go on and when i research the 0x000000f4 error, all the hotfixes i see pertain to sp1. i've submitted a ticket to microsoft but i've not heard back from them and i dont think i will. if i format my computer and put winXP all works fine but if i put win2k3 with sp2 i get bsod, using all certified drivers, i tried swapping out ram. the motherboard is win2k3 certified. is it a hardware error? how do i tell if its a service, program causing this bsod or if its hardware issue or driver and the bsod does not tell me anything.

It's really tough to diagnose when you say XP works fine but Server
2K3 SP2 acts abnormal. A quick Google search regaring Error code
000000f4 seemed to indicate it was hard drive related. Is this machine
SATA or PATA? If SATA, is that driver up to date?

I doubt it's service related. Is the system BIOS also up to date and
any firmware as well?

- Thee Chicago Wolf

d:\tempwork\WER7c57.dir00\Mini111207-01.dmp
d:\tempwork\WER7c57.dir00\sysdata.xml
i got the bsod again today, same thing 0x00000f4
when i search on technet it seems the 0x00000f4 error is realted to video
and the hotfixes are for thos on sp1. since i run sp2 none of the hitfixes
for thsi stop error work.

i formatted my system put winxp sp2 and put the normal software i use on
win2k3 also. basically replicate the setup to match as close as possible and
i dont seem to get the stop error. so i dont think its hardware problem and
faultiness in that matter.

when i put win2k3 sp2, its another story, maybe a day will pass or 3 then
bsod again.

i'm using sata2 hard drives with raid 5. then 1 sata hdd for the OS and a
2nd sata hdd for drive D, this is used to backup drive c to drive D.

here is some info on my system. i'm fully up to date on all drivers. thats
the first thing i've made sure of. same with bios and mobo drivers.

------------------
System Information
------------------
Time of this report: 11/15/2007, 14:14:09
Machine name: DEVILSRAGE
Operating System: Windows Server 2003, Standard Edition (5.2, Build 3790)
Service Pack 2 (3790.srv03_sp2_gdr.070304-2240)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: P35-DS3P
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4
CPUs), ~2.4GHz
Memory: 2046MB RAM
Page File: 529MB used, 4951MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.3790.3959 32bit Unicode

"Thee Chicago Wolf" wrote:

Quote:

Error code 000000f4, parameter1 00000003, parameter2 890aa128, parameter3 890aa28c, parameter4 8094c6e6. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. if i look in event viewer thats what i get. its not much to go on and when i research the 0x000000f4 error, all the hotfixes i see pertain to sp1. i've submitted a ticket to microsoft but i've not heard back from them and i dont think i will. if i format my computer and put winXP all works fine but if i put win2k3 with sp2 i get bsod, using all certified drivers, i tried swapping out ram. the motherboard is win2k3 certified. is it a hardware error? how do i tell if its a service, program causing this bsod or if its hardware issue or driver and the bsod does not tell me anything. It's really tough to diagnose when you say XP works fine but Server 2K3 SP2 acts abnormal. A quick Google search regaring Error code 000000f4 seemed to indicate it was hard drive related. Is this machine SATA or PATA? If SATA, is that driver up to date? I doubt it's service related. Is the system BIOS also up to date and any firmware as well? - Thee Chicago Wolf

Quote:

d:\tempwork\WER7c57.dir00\Mini111207-01.dmp d:\tempwork\WER7c57.dir00\sysdata.xml i got the bsod again today, same thing 0x00000f4 when i search on technet it seems the 0x00000f4 error is realted to video and the hotfixes are for thos on sp1. since i run sp2 none of the hitfixes for thsi stop error work. i formatted my system put winxp sp2 and put the normal software i use on win2k3 also. basically replicate the setup to match as close as possible and i dont seem to get the stop error. so i dont think its hardware problem and faultiness in that matter. when i put win2k3 sp2, its another story, maybe a day will pass or 3 then bsod again. i'm using sata2 hard drives with raid 5. then 1 sata hdd for the OS and a 2nd sata hdd for drive D, this is used to backup drive c to drive D. here is some info on my system. i'm fully up to date on all drivers. thats the first thing i've made sure of. same with bios and mobo drivers. ------------------ System Information ------------------ Time of this report: 11/15/2007, 14:14:09 Machine name: DEVILSRAGE Operating System: Windows Server 2003, Standard Edition (5.2, Build 3790) Service Pack 2 (3790.srv03_sp2_gdr.070304-2240) Language: English (Regional Setting: English) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: P35-DS3P BIOS: Award Modular BIOS v6.00PG Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz Memory: 2046MB RAM Page File: 529MB used, 4951MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.3790.3959 32bit Unicode

Ok, so I noticed your system is reporting physical RAM as 2046. Is it
possible this is an integrated VGA and it is consuming 2MB for VGA
memory? I am thinking your physical RAM should display as 2048.

If you could, please go out and download CPU-Z 1.41 and run it. With
CPU-Z running, go to the Memory tab and see how much system memory it
display in the "General" area. I'm pretty sure it should say 2048 and
not 2046.

Flailing that, you might want to give Memtest 1.70 (Download the
Pre-Compiled Bootable ISO (.zip) and burn it to a CD and boot off of
it) a go and see if it reports any anomalies in the RAM. XP is more
forgiving with memory errors than 2003 Server is.

- Thee Chicago Wolf

i finally found out whats causing the bsod but i dont understand why that
file is running...
event viewer:
Error code 000000f4, parameter1 00000003, parameter2 8936cd88, parameter3
8936ceec, parameter4 8094c6e6.

dr watson - crash.dmp view below:


Application exception occurred:
App: C:\WINDOWS\system32\OOBE\msoobe.exe (pid=2312)
When: 10/6/2007 @ 22:01:04.687
Exception number: c0000005 (access violation)

*----> System Information <----*
Computer Name: DEVILSRAGE
User Name: Administrator
Terminal Session Id: 0
Number of Processors: 4
Processor Type: x86 Family 6 Model 15 Stepping 11
Windows Version: 5.2
Current Build: 3790
Service Pack: 2
Current Type: Multiprocessor Free
Registered Organization: devilsrage
Registered Owner: ninja

*----> Task List <----*
0 System Process
4 System
336 smss.exe
384 csrss.exe
408 winlogon.exe
456 services.exe
468 lsass.exe
644 svchost.exe
708 svchost.exe
780 svchost.exe
816 svchost.exe
832 svchost.exe
948 spoolsv.exe
972 msdtc.exe
1120 svchost.exe
1180 svchost.exe
1688 Explorer.EXE
1976 wmiprvse.exe
1648 taskmgr.exe
1468 ch.exe
1808 msiexec.exe
1768 PDExplo.exe
1616 svchost.exe
1776 Iaantmon.exe
1452 Iaanotif.exe
1812 infinst_autol.exe
1732 setup.exe
2304 wmiprvse.exe
2432 IE7-WindowsServer2003-x86-enu.exe
2448 iesetup.exe
3268 DkService.exe
3624 DNS2GoClient.exe
2748 DefWatch.exe
2760 Rtvscan.exe
2880 ccSetMgr.exe
3020 ccEvtMgr.exe
3464 ccApp.exe
3712 vptray.exe
1040 mmc.exe
2312 msoobe.exe
1252 DWHWIZRD.EXE
1660 drwtsn32.exe

*----> Module List <----*
0000000001000000 - 000000000100a000: C:\WINDOWS\system32\OOBE\msoobe.exe
0000000001090000 - 0000000001659000: C:\WINDOWS\system32\ieframe.dll
0000000001b60000 - 0000000001e97000: C:\WINDOWS\system32\wmploc.dll
0000000048cd0000 - 0000000048d45000: C:\WINDOWS\system32\licdll.dll
000000004dd60000 - 000000004df07000:
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.3790.3959_x-ww_8251BDDE\gdiplus.dll
000000004f580000 - 000000004fb58000: C:\WINDOWS\system32\wmp.dll
000000005a940000 - 000000005a962000: C:\WINDOWS\system32\OOBE\MSOBCOMM.DLL
000000005b3b0000 - 000000005b4bc000: C:\WINDOWS\system32\SYSSETUP.dll
000000005dca0000 - 000000005dce5000: C:\WINDOWS\system32\iertutil.dll
0000000060820000 - 0000000060828000: C:\WINDOWS\system32\OOBE\MSOBWEB.DLL
0000000060830000 - 000000006083a000: C:\WINDOWS\system32\OOBE\MSOBSHEL.DLL
0000000060840000 - 00000000608cd000: C:\WINDOWS\system32\OOBE\MSOBMAIN.DLL
0000000066700000 - 0000000066947000: C:\WINDOWS\system32\sfcfiles.dll
0000000068000000 - 0000000068035000: C:\WINDOWS\system32\rsaenh.dll
0000000071b70000 - 0000000071ba6000: C:\WINDOWS\system32\UxTheme.dll
0000000071bb0000 - 0000000071bb9000: C:\WINDOWS\system32\wsock32.dll
0000000071bf0000 - 0000000071bf8000: C:\WINDOWS\system32\WS2HELP.dll
0000000071c00000 - 0000000071c17000: C:\WINDOWS\system32\WS2_32.dll
0000000071c40000 - 0000000071c97000: C:\WINDOWS\system32\NETAPI32.dll
00000000722f0000 - 00000000722f5000: C:\WINDOWS\system32\SensApi.dll
00000000748c0000 - 00000000748c7000: C:\WINDOWS\system32\POWRPROF.dll
0000000074de0000 - 0000000074df2000: C:\WINDOWS\system32\CLUSAPI.dll
0000000075360000 - 00000000753de000: C:\WINDOWS\system32\CRYPTUI.dll
0000000075fc0000 - 0000000075fe2000: C:\WINDOWS\system32\MSVFW32.dll
0000000076190000 - 00000000761a2000: C:\WINDOWS\system32\MSASN1.dll
00000000761b0000 - 0000000076243000: C:\WINDOWS\system32\CRYPT32.dll
0000000076290000 - 00000000762ad000: C:\WINDOWS\system32\IMM32.dll
0000000076300000 - 00000000764c0000: C:\WINDOWS\system32\netshell.dll
0000000076920000 - 00000000769e2000: C:\WINDOWS\system32\USERENV.dll
0000000076a80000 - 0000000076a98000: C:\WINDOWS\system32\ATL.DLL
0000000076aa0000 - 0000000076acd000: C:\WINDOWS\system32\WINMM.dll
0000000076b10000 - 0000000076b15000: C:\WINDOWS\system32\sfc.dll
0000000076b70000 - 0000000076b7b000: C:\WINDOWS\system32\PSAPI.DLL
0000000076b80000 - 0000000076bae000: C:\WINDOWS\system32\credui.dll
0000000076bb0000 - 0000000076bdb000: C:\WINDOWS\system32\WINTRUST.dll
0000000076be0000 - 0000000076c0b000: C:\WINDOWS\system32\sfc_os.dll
0000000076c10000 - 0000000076c38000: C:\WINDOWS\system32\imagehlp.dll
0000000076cf0000 - 0000000076d0a000: C:\WINDOWS\system32\iphlpapi.dll
0000000076e30000 - 0000000076e3c000: C:\WINDOWS\system32\rtutils.dll
0000000076e40000 - 0000000076e52000: C:\WINDOWS\system32\rasman.dll
0000000076e60000 - 0000000076e8f000: C:\WINDOWS\system32\TAPI32.dll
0000000076e90000 - 0000000076ecf000: C:\WINDOWS\system32\RASAPI32.dll
0000000076f10000 - 0000000076f3e000: C:\WINDOWS\system32\WLDAP32.dll
0000000076f50000 - 0000000076f63000: C:\WINDOWS\system32\Secur32.dll
0000000077010000 - 00000000770d6000: C:\WINDOWS\system32\COMRes.dll
00000000770e0000 - 00000000771e8000: C:\WINDOWS\system32\SETUPAPI.dll
0000000077210000 - 00000000772bb000: C:\WINDOWS\system32\WININET.dll
00000000772c0000 - 000000007736f000: C:\WINDOWS\system32\urlmon.dll
0000000077380000 - 0000000077411000: C:\WINDOWS\system32\USER32.dll
0000000077420000 - 0000000077523000:
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_D8713E55\comctl32.dll
0000000077530000 - 00000000775c7000:
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.3959_x-ww_78FCF8D0\COMCTL32.dll
0000000077670000 - 00000000777a9000: C:\WINDOWS\system32\ole32.dll
00000000777b0000 - 0000000077833000: C:\WINDOWS\system32\CLBCatQ.DLL
0000000077b90000 - 0000000077b98000: C:\WINDOWS\system32\VERSION.dll
0000000077ba0000 - 0000000077bfa000: C:\WINDOWS\system32\msvcrt.dll
0000000077c00000 - 0000000077c48000: C:\WINDOWS\system32\GDI32.dll
0000000077c50000 - 0000000077cef000: C:\WINDOWS\system32\RPCRT4.dll
0000000077d00000 - 0000000077d8b000: C:\WINDOWS\system32\OLEAUT32.dll
0000000077da0000 - 0000000077df2000: C:\WINDOWS\system32\SHLWAPI.dll
0000000077e40000 - 0000000077f42000: C:\WINDOWS\system32\kernel32.dll
0000000077f50000 - 0000000077feb000: C:\WINDOWS\system32\ADVAPI32.dll
000000007c800000 - 000000007c8c0000: C:\WINDOWS\system32\ntdll.dll
000000007c8d0000 - 000000007d0ce000: C:\WINDOWS\system32\SHELL32.dll

*----> State Dump for Thread Id 0x630 <----*

eax=772d6c69 ebx=00000000 ecx=0000558b edx=0000004c esi=00000000 edi=00000001
eip=772c59e4 esp=0006cdfc ebp=0006ce08 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\urlmon.dll -
function: urlmon!CoInternetIsFeatureEnabled
772c59d3 90 nop
772c59d4 8bff mov edi,edi
772c59d6 55 push ebp
772c59d7 8bec mov ebp,esp
772c59d9 51 push ecx
772c59da 53 push ebx
772c59db 8b5d10 mov ebx,[ebp+0x10]
772c59de 56 push esi
772c59df 33f6 xor esi,esi
772c59e1 8975fc mov [ebp-0x4],esi
FAULT ->772c59e4 8933 mov [ebx],esi
ds:0023:00000000=????????
772c59e6 e8fbefffff call urlmon!CoInternetIsFeatureEnabled+0x96
(772c49e6)
772c59eb 85c0 test eax,eax
772c59ed 0f845d360300 je urlmon!URLOpenBlockingStreamW+0xd924
(772f9050)
772c59f3 397514 cmp [ebp+0x14],esi
772c59f6 57 push edi
772c59f7 0f854b120100 jne
urlmon!CoInternetCreateSecurityManager+0x792 (772d6c48)
772c59fd 397508 cmp [ebp+0x8],esi
772c5a00 0f8554360300 jne urlmon!URLOpenBlockingStreamW+0xd92e
(772f905a)
772c5a06 6a18 push 0x18
772c5a08 e86cceffff call urlmon+0x2879 (772c2879)

*----> Stack Back Trace <----*
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\ieframe.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\OOBE\MSOBWEB.DLL -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\OOBE\MSOBSHEL.DLL -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\OOBE\MSOBMAIN.DLL -
*** ERROR: Module load completed but symbols could not be loaded for
C:\WINDOWS\system32\OOBE\msoobe.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\kernel32.dll -
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be
wrong.
0006ce08 772d6c80 00000000 772d6c54 00000000
urlmon!CoInternetIsFeatureEnabled+0x1094
0006ce20 011102d3 0006ce54 00000000 0006def8
urlmon!CoInternetCreateZoneManager+0x17
0006dea0 011f9808 000b7dbc 0006def8 60821110
ieframe!SoftwareUpdateMessageBox+0x15f5
0006decc 608223f2 000b1fa8 0006def8 60821110 ieframe!Ordinal164+0x1efcf
0006df34 60833ca2 007777cc 0006df88 00000000 MSOBWEB+0x23f2
0006e5a4 60856ba6 007742dc 60840000 000600a0 MSOBSHEL+0x3ca2
0006e5fc 608527d1 608522e0 7738b1f6 77e4ec94 MSOBMAIN!IsOemVer+0x4161
0006fb70 010012f3 00000000 00000000 000205e8 MSOBMAIN!LaunchMSOOBE+0x4f1
0006ffc0 77e6f23b 00000000 00000000 7ffde000 msoobe+0x12f3
0006fff0 00000000 01001274 00000000 78746341
kernel32!ProcessIdToSessionId+0x209

*----> Raw Stack Dump <----*
000000000006cdfc bc 7d 0b 00 00 00 00 00 - 00 00 00 00 20 ce 06 00
..}.......... ...
000000000006ce0c 80 6c 2d 77 00 00 00 00 - 54 6c 2d 77 00 00 00 00
..l-w....Tl-w....
000000000006ce1c f8 de 06 00 a0 de 06 00 - d3 02 11 01 54 ce 06 00
.............T...
000000000006ce2c 00 00 00 00 f8 de 06 00 - bc 7d 0b 00 10 11 82 60
..........}.....`
000000000006ce3c 08 df 06 00 f8 de 06 00 - 10 11 82 60 d0 dc 0e 00
............`....
000000000006ce4c 00 00 00 00 00 00 00 00 - 43 00 3a 00 5c 00 57 00
.........C.:.\.W.
000000000006ce5c 49 00 4e 00 44 00 4f 00 - 57 00 53 00 5c 00 73 00
I.N.D.O.W.S.\.s.
000000000006ce6c 79 00 73 00 74 00 65 00 - 6d 00 33 00 32 00 5c 00
y.s.t.e.m.3.2.\.
000000000006ce7c 6f 00 6f 00 62 00 65 00 - 5c 00 61 00 63 00 74 00
o.o.b.e.\.a.c.t.
000000000006ce8c 73 00 68 00 65 00 6c 00 - 6c 00 2e 00 68 00 74 00
s.h.e.l.l...h.t.
000000000006ce9c 6d 00 00 00 00 00 00 00 - 01 00 00 00 34 cf 06 00
m...........4...
000000000006ceac 58 1f 07 00 08 00 15 c0 - 00 00 00 00 04 07 00 00
X...............
000000000006cebc 02 00 00 00 38 cf 06 00 - 08 00 15 c0 00 00 00 00
.....8...........
000000000006cecc 00 e0 fd 7f 00 d0 fd 7f - f4 ce 06 00 2f d5 82 7c
............./..|
000000000006cedc 18 cf 06 00 50 cf 06 00 - 3c cf 06 00 f0 ce 06 00
.....P...<.......
000000000006ceec 58 1f 07 00 00 00 00 00 - 40 cf 06 00 bb d1 82 7c
X.......@......|
000000000006cefc 18 cf 06 00 50 cf 06 00 - 3c cf 06 00 38 cf 06 00
.....P...<...8...
000000000006cf0c 28 cf 06 00 c3 cc 82 7c - 44 01 07 00 2c cf 06 00
(......|D...,...
000000000006cf1c fe ce 82 7c 04 07 00 00 - 58 1f 00 00 38 cf 06 00
....|....X...8...
000000000006cf2c 6c cf 06 00 b0 ce 82 7c - 58 1f 00 00 5c 26 00 00
l......|X...\&..

*----> State Dump for Thread Id 0x324 <----*

eax=7c80e1fa ebx=008efef0 ecx=00000000 edx=00000000 esi=00000002 edi=00000000
eip=7c8285ec esp=008efea4 ebp=008eff48 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\ntdll.dll -
function: ntdll!KiFastSystemCallRet
7c8285ce e82c000000 call ntdll!RtlRaiseException (7c8285ff)
7c8285d3 8b0424 mov eax,[esp]
7c8285d6 8be5 mov esp,ebp
7c8285d8 5d pop ebp
7c8285d9 c3 ret
7c8285da 8da42400000000 lea esp,[esp]
7c8285e1 8da42400000000 lea esp,[esp]
ntdll!KiFastSystemCall:
7c8285e8 8bd4 mov edx,esp
7c8285ea 0f34 sysenter
ntdll!KiFastSystemCallRet:
7c8285ec c3 ret
7c8285ed 8da42400000000 lea esp,[esp]
7c8285f4 8d642400 lea esp,[esp]
ntdll!KiIntSystemCall:
7c8285f8 8d542408 lea edx,[esp+0x8]
7c8285fc cd2e int 2e
7c8285fe c3 ret
ntdll!RtlRaiseException:
7c8285ff 55 push ebp
7c828600 8bec mov ebp,esp
7c828602 8da42430fdffff lea esp,[esp-0x2d0]

*----> Stack Back Trace <----*
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be
wrong.
008eff48 7c80e4a2 00000002 008eff70 00000000 ntdll!KiFastSystemCallRet
008effb8 77e64829 00000000 00000000 00000000
ntdll!RtlSetLastWin32ErrorAndNtStatusFromNtStatus+0x301
008effec 00000000 7c80e1fa 00000000 00000000 kernel32!GetModuleHandleA+0xdf

*----> Raw Stack Dump <----*
00000000008efea4 fb 7c 82 7c bb e5 80 7c - 02 00 00 00 f0 fe 8e 00
..|.|...|........
00000000008efeb4 01 00 00 00 01 00 00 00 - 10 ff 8e 00 00 10 00 00
.................
00000000008efec4 88 1f 7b 00 c0 83 88 7c - 24 00 00 00 01 00 00 00
...{....|$.......
00000000008efed4 00 00 00 00 00 00 00 00 - 30 00 00 00 ff ff ff ff
.........0.......
00000000008efee4 ff ff ff ff 61 d3 80 7c - 00 00 00 00 7c 00 00 00
.....a..|....|...
00000000008efef4 88 00 00 00 08 00 00 c0 - 00 10 00 00 30 ff 8e 00
.............0...
00000000008eff04 d1 96 82 7c d6 96 82 7c - 00 10 00 00 00 a2 2f 4d
....|...|....../M
00000000008eff14 ff ff ff ff 00 e0 fd 7f - c0 83 88 7c 10 ff 8e 00
............|....
00000000008eff24 f0 fe 8e 00 e0 96 82 7c - 02 00 00 00 c0 fe 8e 00
........|........
00000000008eff34 ae e1 80 7c dc ff 8e 00 - 70 82 82 7c c8 d3 80 7c
....|....p..|...|
00000000008eff44 00 00 00 00 b8 ff 8e 00 - a2 e4 80 7c 02 00 00 00
............|....
00000000008eff54 70 ff 8e 00 00 00 00 00 - e0 93 04 00 01 00 00 00
p...............
00000000008eff64 00 00 00 00 00 00 00 00 - 00 00 00 00 7c 00 00 00
.............|...
00000000008eff74 88 00 00 00 00 10 00 00 - 88 1f 7b 00 00 10 00 00
...........{.....
00000000008eff84 90 2f 7b 00 80 70 88 7c - 00 00 00 00 30 00 00 00
../{..p.|....0...
00000000008eff94 a0 70 88 7c 00 10 00 00 - 80 70 88 7c 88 1f 7b 00
..p.|.....p.|..{.
00000000008effa4 00 00 00 00 a0 70 88 7c - e5 03 00 00 00 10 00 00
......p.|........
00000000008effb4 90 2f 7b 00 ec ff 8e 00 - 29 48 e6 77 00 00 00 00
../{.....)H.w....
00000000008effc4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
.................
00000000008effd4 c4 ff 8e 00 60 31 83 80 - ff ff ff ff 60 1a e6 77
.....`1......`..w



"Thee Chicago Wolf" wrote:

Quote:

d:\tempwork\WER7c57.dir00\Mini111207-01.dmp d:\tempwork\WER7c57.dir00\sysdata.xml i got the bsod again today, same thing 0x00000f4 when i search on technet it seems the 0x00000f4 error is realted to video and the hotfixes are for thos on sp1. since i run sp2 none of the hitfixes for thsi stop error work. i formatted my system put winxp sp2 and put the normal software i use on win2k3 also. basically replicate the setup to match as close as possible and i dont seem to get the stop error. so i dont think its hardware problem and faultiness in that matter. when i put win2k3 sp2, its another story, maybe a day will pass or 3 then bsod again. i'm using sata2 hard drives with raid 5. then 1 sata hdd for the OS and a 2nd sata hdd for drive D, this is used to backup drive c to drive D. here is some info on my system. i'm fully up to date on all drivers. thats the first thing i've made sure of. same with bios and mobo drivers. ------------------ System Information ------------------ Time of this report: 11/15/2007, 14:14:09 Machine name: DEVILSRAGE Operating System: Windows Server 2003, Standard Edition (5.2, Build 3790) Service Pack 2 (3790.srv03_sp2_gdr.070304-2240) Language: English (Regional Setting: English) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: P35-DS3P BIOS: Award Modular BIOS v6.00PG Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz Memory: 2046MB RAM Page File: 529MB used, 4951MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.3790.3959 32bit Unicode Ok, so I noticed your system is reporting physical RAM as 2046. Is it possible this is an integrated VGA and it is consuming 2MB for VGA memory? I am thinking your physical RAM should display as 2048. If you could, please go out and download CPU-Z 1.41 and run it. With CPU-Z running, go to the Memory tab and see how much system memory it display in the "General" area. I'm pretty sure it should say 2048 and not 2046. Flailing that, you might want to give Memtest 1.70 (Download the Pre-Compiled Bootable ISO (.zip) and burn it to a CD and boot off of it) a go and see if it reports any anomalies in the RAM. XP is more forgiving with memory errors than 2003 Server is. - Thee Chicago Wolf

yes i have cpu-z handy, i use it on all my machines along with memtest. in
the past 2 months i had some bad ram and swapped it out for new one, the bad
ram caused odd behaviour but it never bsod. i have checked this ram and works
ok and even swapped it out with other ram and ram passes all memtest runs for
hours, even overnight.
using cpu-z i look at ram and it says 2048 ddr2

i dont know why the windows system information reports 2046 when cpu-z says
2048.

i have already disabled all video options, its as vanilla as it can be with
latest drivers. all extra feature the video card has to offer have been
turned off.


"Thee Chicago Wolf" wrote:

Quote:

d:\tempwork\WER7c57.dir00\Mini111207-01.dmp d:\tempwork\WER7c57.dir00\sysdata.xml i got the bsod again today, same thing 0x00000f4 when i search on technet it seems the 0x00000f4 error is realted to video and the hotfixes are for thos on sp1. since i run sp2 none of the hitfixes for thsi stop error work. i formatted my system put winxp sp2 and put the normal software i use on win2k3 also. basically replicate the setup to match as close as possible and i dont seem to get the stop error. so i dont think its hardware problem and faultiness in that matter. when i put win2k3 sp2, its another story, maybe a day will pass or 3 then bsod again. i'm using sata2 hard drives with raid 5. then 1 sata hdd for the OS and a 2nd sata hdd for drive D, this is used to backup drive c to drive D. here is some info on my system. i'm fully up to date on all drivers. thats the first thing i've made sure of. same with bios and mobo drivers. ------------------ System Information ------------------ Time of this report: 11/15/2007, 14:14:09 Machine name: DEVILSRAGE Operating System: Windows Server 2003, Standard Edition (5.2, Build 3790) Service Pack 2 (3790.srv03_sp2_gdr.070304-2240) Language: English (Regional Setting: English) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: P35-DS3P BIOS: Award Modular BIOS v6.00PG Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz Memory: 2046MB RAM Page File: 529MB used, 4951MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.3790.3959 32bit Unicode Ok, so I noticed your system is reporting physical RAM as 2046. Is it possible this is an integrated VGA and it is consuming 2MB for VGA memory? I am thinking your physical RAM should display as 2048. If you could, please go out and download CPU-Z 1.41 and run it. With CPU-Z running, go to the Memory tab and see how much system memory it display in the "General" area. I'm pretty sure it should say 2048 and not 2046. Flailing that, you might want to give Memtest 1.70 (Download the Pre-Compiled Bootable ISO (.zip) and burn it to a CD and boot off of it) a go and see if it reports any anomalies in the RAM. XP is more forgiving with memory errors than 2003 Server is. - Thee Chicago Wolf

Quote:

i finally found out whats causing the bsod but i dont understand why that file is running... event viewer: Error code 000000f4, parameter1 00000003, parameter2 8936cd88, parameter3 8936ceec, parameter4 8094c6e6. dr watson - crash.dmp view below: Application exception occurred: App: C:\WINDOWS\system32\OOBE\msoobe.exe (pid=2312) When: 10/6/2007 @ 22:01:04.687 Exception number: c0000005 (access violation)

Ha ha ha, Out of Box Experience is crashing!? Ok, I remember seeing
some hotfix for OOBE, not specifically for MSOOBE.exe, but it was for
XP sadly. Can't help with that one, sorry.

- Thee Chicago Wolf

Quote:

yes i have cpu-z handy, i use it on all my machines along with memtest. in the past 2 months i had some bad ram and swapped it out for new one, the bad ram caused odd behaviour but it never bsod. i have checked this ram and works ok and even swapped it out with other ram and ram passes all memtest runs for hours, even overnight. using cpu-z i look at ram and it says 2048 ddr2 i dont know why the windows system information reports 2046 when cpu-z says 2048. i have already disabled all video options, its as vanilla as it can be with latest drivers. all extra feature the video card has to offer have been turned off.

I would imagine a cheap-o onboard VGA card would snag an MB or two
memory and then report back 2046 but I don't know what kind server
this is.

How about the system BIOS, is that up to date too?

Did I already send you the link to problem that occur after installing
SP2? Not at all related to your msoobe.exe error but something you
should be aware of nonetheless: http://support.microsoft.com/kb/944011

- Thee Chicago Wolf

what kind fo server? well the system info says it all which i posted, a
gigabyte.
its not a dell poweredge or anything like that if thats what you are
referring to.

bios is up to date, it has a $150 nvidia video card which is certified to
work on win2k3.

i also replaced video card, same problem.

if i could fifure out why the msoobe is running, i'm lost as to why for no
reason the msoobe decides to run.
and yes i have run a complete virus and spyware check, system is absolutely
clean.


"Thee Chicago Wolf" wrote:

Quote:

yes i have cpu-z handy, i use it on all my machines along with memtest. in the past 2 months i had some bad ram and swapped it out for new one, the bad ram caused odd behaviour but it never bsod. i have checked this ram and works ok and even swapped it out with other ram and ram passes all memtest runs for hours, even overnight. using cpu-z i look at ram and it says 2048 ddr2 i dont know why the windows system information reports 2046 when cpu-z says 2048. i have already disabled all video options, its as vanilla as it can be with latest drivers. all extra feature the video card has to offer have been turned off. I would imagine a cheap-o onboard VGA card would snag an MB or two memory and then report back 2046 but I don't know what kind server this is. How about the system BIOS, is that up to date too? Did I already send you the link to problem that occur after installing SP2? Not at all related to your msoobe.exe error but something you should be aware of nonetheless: http://support.microsoft.com/kb/944011 - Thee Chicago Wolf

Quote:

what kind fo server? well the system info says it all which i posted, a gigabyte. its not a dell poweredge or anything like that if thats what you are referring to. bios is up to date, it has a $150 nvidia video card which is certified to work on win2k3. i also replaced video card, same problem. if i could fifure out why the msoobe is running, i'm lost as to why for no reason the msoobe decides to run. and yes i have run a complete virus and spyware check, system is absolutely clean.

Yes, I was wondering if it was an HP or a Dell Poweredge or something
similar. I just thought of a quick and dirty fix which ought to work
if you feel like updating it. Perhaps just creating a new group policy
object to restrict msoobe.exe from running should stop it from
crashing when it tries to start...at least in theory. I'm not 100% if
there's a service that you could disable either but perhaps check that
out too.

Start > Run > gpedit.msc > Local Computer Policy > Windows Settings >
Security Settings > Software Restrictions > Additional Rules,
right-click in the right pane and add a new path rule msoobe.exe. If
it isn't possible to delete or rename msoobe.exe to something else to
keep it from starting up, the path rule should.

- Thee Chicago Wolf

today i got another BSOD
Error code 00000077, parameter1 c0000185, parameter2 c0000185, parameter3
00000000, parameter4 01a13000.

however i'm unable to open the minidump file to read it

can you advise how i would actually look at the minidump file.
i suspect it may be an IRQ conflict
0xC0000185, or STATUS_IO_DEVICE_ERROR: improper termination or defective
cabling of SCSI-based devices, or two devices attempting to use the same IRQ.

i dont run scsi so that leaves on IRQ and when i look at irq settings, which
i'm not able to change them, i see nvidia uses irq 16 which is same as my
raid intel chipset.


i tried to use dr watson to open the file but it wont. any ideas how to open
a mini dump crash log file?

thanks for all your help.



"john" wrote:

Quote:

d:\tempwork\WER7c57.dir00\Mini111207-01.dmp d:\tempwork\WER7c57.dir00\sysdata.xml i got the bsod again today, same thing 0x00000f4 when i search on technet it seems the 0x00000f4 error is realted to video and the hotfixes are for thos on sp1. since i run sp2 none of the hitfixes for thsi stop error work. i formatted my system put winxp sp2 and put the normal software i use on win2k3 also. basically replicate the setup to match as close as possible and i dont seem to get the stop error. so i dont think its hardware problem and faultiness in that matter. when i put win2k3 sp2, its another story, maybe a day will pass or 3 then bsod again. i'm using sata2 hard drives with raid 5. then 1 sata hdd for the OS and a 2nd sata hdd for drive D, this is used to backup drive c to drive D. here is some info on my system. i'm fully up to date on all drivers. thats the first thing i've made sure of. same with bios and mobo drivers. ------------------ System Information ------------------ Time of this report: 11/15/2007, 14:14:09 Machine name: DEVILSRAGE Operating System: Windows Server 2003, Standard Edition (5.2, Build 3790) Service Pack 2 (3790.srv03_sp2_gdr.070304-2240) Language: English (Regional Setting: English) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: P35-DS3P BIOS: Award Modular BIOS v6.00PG Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz Memory: 2046MB RAM Page File: 529MB used, 4951MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.3790.3959 32bit Unicode "Thee Chicago Wolf" wrote: Error code 000000f4, parameter1 00000003, parameter2 890aa128, parameter3 890aa28c, parameter4 8094c6e6. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. if i look in event viewer thats what i get. its not much to go on and when i research the 0x000000f4 error, all the hotfixes i see pertain to sp1. i've submitted a ticket to microsoft but i've not heard back from them and i dont think i will. if i format my computer and put winXP all works fine but if i put win2k3 with sp2 i get bsod, using all certified drivers, i tried swapping out ram. the motherboard is win2k3 certified. is it a hardware error? how do i tell if its a service, program causing this bsod or if its hardware issue or driver and the bsod does not tell me anything. It's really tough to diagnose when you say XP works fine but Server 2K3 SP2 acts abnormal. A quick Google search regaring Error code 000000f4 seemed to indicate it was hard drive related. Is this machine SATA or PATA? If SATA, is that driver up to date? I doubt it's service related. Is the system BIOS also up to date and any firmware as well? - Thee Chicago Wolf

Quote:

today i got another BSOD Error code 00000077, parameter1 c0000185, parameter2 c0000185, parameter3 00000000, parameter4 01a13000. however i'm unable to open the minidump file to read it can you advise how i would actually look at the minidump file. i suspect it may be an IRQ conflict 0xC0000185, or STATUS_IO_DEVICE_ERROR: improper termination or defective cabling of SCSI-based devices, or two devices attempting to use the same IRQ. i dont run scsi so that leaves on IRQ and when i look at irq settings, which i'm not able to change them, i see nvidia uses irq 16 which is same as my raid intel chipset. i tried to use dr watson to open the file but it wont. any ideas how to open a mini dump crash log file? thanks for all your help.

John,

Wow, I haven't heard the term IRQ conflict since the Win95 days before
PnP was smoothed out. Is there any way to move the VGA card to a
different slot? I am not sure what a .dmp file shows if opened in a
text editor but for any debugging I guess the MS Debugging Tools would
be a place to start:
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

What about booting into safe mode? In the BIOS, is there any option
that says dedicate an IRQ for the VGA adapter or some such setting? I
remember this from the PCI VGA card days but not sure if this is an
option in modern BIOS settings with AGP and PCI Express cards.

- Thee Chicago Wolf