Random Crash problems (black screen). Diagnosis?

Hello! First time poster. I've searched everywhere on this forum and I can't find anything specific to my problems.

However, this thread is slightly similar:
http://www.windowsbbs.com/showthread.php?t=50346

Here is my story, my computer specs, and my problem:

-MSI K8N Neo4 Platinum mobo
-AMD Athlon 64 bit 3500+
-2 x 1 GB DDR400 OCZ RAM
-2 x 200 GB Western Digitial SATA hd's
-BFG Geforce6800GT
-Belkin F5D8000 Pre-N Wireless PCI card adapter
-HDA X-Mystique 7.1 soundcard.
-Antec NeoHE 500 Watt PSU
-Windows XP Professional + SP2

Problem:

About a month ago, my computer started to crash. Seems like it came out of nowhere. I play Battlefield 2 online quite a lot. All of a sudden, the game (as well as Windows) would crash randomly. Maybe 15 minutes into a game, maybe 2 hours. No blue screen of death. Just screen going black, the audio will continue to play, then lock up, and finally nothing. Sometimes, the CPU fan would stop, then spin back up. Every single time, the reboot button on the case would NOT reboot the system. I have to physically power off the computer and turn it back on. Sometimes, doing this would make my USB keyboard go undetected during the POST startup, which would require another turning off of the computer.

I thought it was just a software/driver problem with Battlefield 2 and/or Windows. However, now it happens during normal Windows operation. This happens under non-intensive operations such as listening to music or watching a movie or browsing the web. Same symptoms. Black screen, crash, audio continues playing for about 5-10 seconds, locks up, then nothing.

I've tried formating my harddrve and reinstalling Windows. Windows is always currently updated. MB drivers were updated. Video card drivers were updated (then I rolled back to an older version to test out. Didn't work. Still crashed.) Audio drivers are all updated.

I've exhausted almost everything. I took out the PSU, replaced with my buddies. Still crashes. Ran memtest86 for seven hours to test RAM. Not a single error.

Windows comes back after the crash with the same old "Your system has recovered from a serious error" message.

I am at a complete loss. What tools (I'm pretty knowledgable, but I won't know how to debug my own system) can I use to try and at least isolate the problem? Does this sound more hardware based or maybe driver/software based? I've looked through my system events folder, but can't seem to find anything relating to the crash. Where does Windows log more of this data?

Again, these crashes seem completely random. I may be on here for three hours, then crash. Maybe 15 minutes, then crash.

I thought maybe it was a heat problem. Definitely not. Cool n' Quiet is on, and my system (case) temperatures are only at about 100º F. CPU runs cool at about 98º. I'll test my voltages soon, but BIOS says they're all within norms. I do absolutely NO overclocking on this system btw.

Can ANYONE shed some light? If any other system info is needed, just tell me where to get it and I'll post. This is driving me absolutely insane!!

P.S.- I run ZoneAlarm software, and my system is completely clean of any viruses or malware.

P.P.S- Here is some more information of a current crash.

The files included in the error report are
\Temp\WER9d32.dir00\Mini043006-01.dmp
\Temp\WER9d32.dir00\sysdata.xml

When I check out my event viewer, I find the error.

Type: System Error
Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000.
Category 102, Event ID: 1003

0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 38 2c 20 000008,
0038: 38 30 30 34 32 30 30 30 80042000
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

However, this error doesn't always show. For example, my system just crashed and it didn't have any system error reported. Furthermore, windows didn't pop up with it's "System has recovered from a serious error" thingie.

This is sounding more like a motherboard problem to me. I just don't know...

 

Alrighty. Here is what my debuglog.txt reads for the last crash dump:


Loading Dump File [C:\WINDOWS\Minidump\Mini043006-02.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: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp.060315-1524
Kernel base = 0x80800000 PsLoadedModuleList = 0x8087c420
Debug session time: Sun Apr 30 04:30:35.562 2006 (GMT-4)
System Uptime: 0 days 0:16:03.188
Loading Kernel Symbols
.................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 0, 0}

Probably caused by : nv4_mini.sys ( nv4_mini+374e3 )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 00000000 to b265d4e3

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x374e3


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini+374e3
b265d4e3 e878ffffff call nv4_mini+0x37460 (b265d460)

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_mini+374e3

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43751a19

FAILURE_BUCKET_ID: 0x7f_8_nv4_mini+374e3

BUCKET_ID: 0x7f_8_nv4_mini+374e3

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

eax=00000000 ebx=89d426d8 ecx=00000000 edx=89d416f0 esi=00000007 edi=00000001
eip=b265d4e3 esp=bacc5000 ebp=00000000 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nv4_mini+0x374e3:
b265d4e3 e878ffffff call nv4_mini+0x37460 (b265d460)
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x374e3
start end module name
80800000 809f6700 nt ntkrnlpa.exe Wed Mar 15 20:09:36 2006 (4418BAD0)
80a00000 80a20280 hal halaacpi.dll Mon Nov 15 20:37:02 2004 (419959BE)
a691b000 a6945000 kmixer kmixer.sys unavailable (00000000)
a6c66000 a6ca7000 HTTP HTTP.sys unavailable (00000000)
a72be000 a72d2400 _______________________________________ ??????????????????????????????????????? Wed Aug 04 02:15:03 2004 (41107EE7)
a7b9b000 a7bc2f00 secdrv secdrv.sys Tue Aug 31 09:42:55 2004 (4134805F)
a7bc3000 a7c14300 srv srv.sys Mon May 09 20:22:19 2005 (427FFEBB)
a7c65000 a7c91400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
a8df3000 a8e09a80 dump_nvata dump_nvata.sys Tue May 17 20:45:07 2005 (428A9013)
a8e0a000 a8e1c000 LMouKE LMouKE.Sys unavailable (00000000)
a92f4000 a9303900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
a9304000 a930cd80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
a9314000 a931d000 LHidUsbK LHidUsbK.Sys unavailable (00000000)
a94be000 a94c1000 Dxapi Dxapi.sys unavailable (00000000)
a94fe000 a9503000 watchdog watchdog.sys unavailable (00000000)
a9516000 a951d000 LHidKE LHidKE.Sys unavailable (00000000)
a9823000 a9826a00 kbdhid kbdhid.sys Wed Aug 04 01:58:33 2004 (41107B09)
a9827000 a9829f80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
a982b000 a982d580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
a99af000 a99b6c00 usbccgp usbccgp.sys Thu Jun 16 20:18:03 2005 (42B216BB)
ad71f000 ad78d900 mrxsmb mrxsmb.sys Mon Oct 17 19:54:38 2005 (435439BE)
ad78e000 ad7b8a00 rdbss rdbss.sys Wed Oct 27 21:14:55 2004 (4180480F)
ad7b9000 ad7dad00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
ad7db000 ad7fc100 ipnat ipnat.sys Thu Oct 20 21:47:17 2005 (435848A5)
ad7fd000 ad856940 vsdatant vsdatant.sys Thu Mar 16 12:48:29 2006 (4419A4ED)
ad857000 ad87ec00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
ad87f000 ad8d7000 tcpip tcpip.sys Fri Jan 13 12:07:06 2006 (43C7DE3A)
ad8d7000 ad8e9400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
ad90a000 ad9805e0 VETMONNT VETMONNT.SYS Fri Apr 29 01:26:10 2005 (4271C572)
ad981000 ad99a320 VETFDDNT VETFDDNT.SYS Fri Apr 29 01:26:11 2005 (4271C573)
adaac000 adaad100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
adb7b000 adb7df00 ws2ifsl ws2ifsl.sys Fri Aug 17 16:55:58 2001 (3B7D84DE)
adb9b000 adb9d280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
b1a67000 b1a6d700 USBSTOR USBSTOR.SYS Tue Dec 28 18:58:15 2004 (41D1F317)
b1a8f000 b1a96880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
b1a97000 b1a9ba80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
b1a9f000 b1aa4200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
b21d5000 b21dd880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
b21f5000 b21fd700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
b2205000 b220d700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
b254a000 b257d180 update update.sys Wed Sep 01 18:27:22 2004 (41364CCA)
b257e000 b25ada80 rdpdr rdpdr.sys Wed Jun 01 21:42:19 2005 (429E63FB)
b25ae000 b25bee00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
b25bf000 b25d5680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
b25d6000 b25e9900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
b2612000 b2625780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
b2626000 b2984880 nv4_mini nv4_mini.sys Fri Nov 11 17:24:25 2005 (43751A19)
b2985000 b29b7d80 NVSNPU NVSNPU.SYS Wed Apr 06 06:22:01 2005 (4253B849)
b29b8000 b29f7f00 NVNRM NVNRM.SYS Wed Apr 06 06:22:11 2005 (4253B853)
b29f8000 b2a1ba00 portcls portcls.sys Tue Jan 31 20:31:45 2006 (43E00F81)
b2a1c000 b2b65440 cmuda3 cmuda3.sys Thu Jun 02 03:34:30 2005 (429EB686)
b2b66000 b2c1e000 wnihdd51 wnihdd51.sys Wed Aug 11 15:14:18 2004 (411A700A)
b2c1e000 b2c40700 ks ks.sys Wed Dec 28 19:29:29 2005 (43B32DE9)
b2c41000 b2c63f00 USBPORT USBPORT.SYS Tue Oct 25 19:39:41 2005 (435EC23D)
b2e25000 b2e26080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
b2e27000 b2e28080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
b2e29000 b2e2a080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
b2e2b000 b2e2cf00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
b2f65000 b2f68c80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
b2f81000 b2f83580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
b2f85000 b2f88c80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
b3181000 b318f280 usbhub usbhub.sys Mon Feb 13 20:16:57 2006 (43F12F89)
b3191000 b319af00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
b31a1000 b31a9900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
b31b1000 b31bcd00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
b31c1000 b31cb200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
b31d1000 b31dd880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
b31e1000 b31f0d80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
b32f1000 b32ffb80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
b3301000 b330f080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
b3311000 b331d180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
b3321000 b332b400 imapi imapi.sys Fri Aug 13 13:17:15 2004 (411CF79B)
b34c7000 b34cd180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
b34cf000 b34d4a00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
b34d7000 b34dd000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
b34df000 b34e3080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
b34e7000 b34eb580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
b34ef000 b34f3880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
b34f7000 b34fe000 fdc fdc.sys unavailable (00000000)
b34ff000 b3505a80 usbehci usbehci.sys Tue Oct 25 19:39:41 2005 (435EC23D)
b3507000 b350b280 usbohci usbohci.sys Wed Aug 04 02:08:34 2004 (41107D62)
b5310000 b5314f20 VET_FILT VET-FILT.SYS Fri Apr 29 01:26:09 2005 (4271C571)
b5338000 b533d000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
b563f000 b5642280 nvnetbus nvnetbus.sys Wed Apr 06 06:22:28 2005 (4253B864)
b670f000 b6718480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
b9597000 b95a5d80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
b9e2e000 b9e3c000 AmdK8 AmdK8.sys Mon Mar 07 16:58:10 2005 (422CCE72)
ba5a4000 ba5bda80 Mup Mup.sys Thu Sep 22 21:26:18 2005 (433359BA)
ba5be000 ba5eaa80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
ba5eb000 ba677600 Ntfs Ntfs.sys Mon Nov 28 20:19:54 2005 (438BACBA)
ba678000 ba68e780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
ba68f000 ba6a0f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
ba6a1000 ba6bf780 fltMgr fltMgr.sys Wed Aug 04 02:01:17 2004 (41107BAD)
ba6c0000 ba6d6a80 nvata nvata.sys Tue May 17 20:45:07 2005 (428A9013)
ba6d7000 ba6ec780 nvatabus nvatabus.sys Tue Dec 07 19:15:51 2004 (41B647B7)
ba6ed000 ba704580 atapi atapi.sys Tue Jul 05 19:45:22 2005 (42CB1B92)
ba705000 ba72a700 dmio dmio.sys Wed Aug 04 02:07:13 2004 (41107D11)
ba72b000 ba749880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
ba74a000 ba767580 pcmcia pcmcia.sys Fri May 06 19:42:29 2005 (427C00E5)
ba768000 ba778a80 pci pci.sys Thu Dec 16 13:34:40 2004 (41C1D540)
ba779000 ba7a6d80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
ba8a8000 ba8b0c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
ba8b8000 ba8c6f80 ohci1394 ohci1394.sys Fri Aug 12 20:11:00 2005 (42FD3A94)
ba8c8000 ba8d5000 1394BUS 1394BUS.SYS Tue Oct 19 19:49:17 2004 (4175A7FD)
ba8d8000 ba8e2500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
ba8e8000 ba8f4c80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
ba8f8000 ba900e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
ba908000 ba914180 CLASSPNP CLASSPNP.SYS Wed Oct 05 19:53:44 2005 (43446788)
ba918000 ba9253c0 Defrag32b Defrag32b.sys Sat Jun 25 20:52:16 2005 (42BDFC40)
baae8000 baaf53c0 Defrag32 Defrag32.SYS Sat Jun 25 20:52:16 2005 (42BDFC40)
bab28000 bab2e200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
bab30000 bab34900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
bab38000 bab3ce20 PxHelp20 PxHelp20.sys Tue Feb 01 18:23:42 2005 (42000F7E)
bac38000 bac3cfa0 WNIPROT5 WNIPROT5.SYS Wed Aug 11 15:15:39 2004 (411A705B)
bacb8000 bacbb000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
bad70000 bad739e0 VET_REC VET-REC.SYS Fri Apr 29 01:26:09 2005 (4271C571)
bad7c000 bad7f900 ndisuio ndisuio.sys Mon Feb 27 19:09:25 2006 (440394B5)
bada8000 bada9b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
badaa000 badab100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
badac000 badad700 dmload dmload.sys Fri Aug 17 16:58:15 2001 (3B7D8567)
bae04000 bae05a80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
bae68000 bae69100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
bae6a000 bae6b280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
bae70000 bae70d00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
baef3000 baef4000 dxgthk dxgthk.sys unavailable (00000000)
baf05000 baf05b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)
baf8d000 baf8dc00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
bf800000 bf9c1100 win32k win32k.sys Wed Oct 05 20:09:50 2005 (43446B4E)
bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf9d4000 bfd92400 nv4_disp nv4_disp.dll Fri Nov 11 17:18:35 2005 (437518BB)

Unloaded modules:
a0362000 a036c000 cKPiteM8
Timestamp: unavailable (00000000)
Checksum: 00000000
a71d1000 a71fb000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
baf19000 baf1a000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a729b000 a72be000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b5a4a000 b5a57000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b66ff000 b670d000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bae2e000 bae30000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b21e5000 b21ee000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b25fa000 b25fe000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b2225000 b2232000 i8042prt.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
b5f5a000 b5f5f000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
b2ca8000 b2cab000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Anyone?

 

Yup, I've already freshly installed both the newest Nvidia video card drivers as well as the Nvidia Nforce chipset drivers. Still getting crashes. This is driving me insane.

 

Bugcheck 7F with BP1 8 means double faulty. It is the double fault is caused by stack overflow and it is software error. Otherwise it is hardware error (ie faulty motherboard, ram or video card)

Attach the output of windgb !thread here in order to confirm whether is stack overflow or not. Attach all the system event 1001 and 1003 here as well.

According to my record, the nVidia Display card Driver with time stamp 4410CB0A (Fri Mar 10 08:40:42 2006) is unstable. Install nVidiia Display Card version 78.xx and it is stable version

 

Sorry, I'm a bit noob. What do you mean the output of windgb thread?

I thought that rolling back the Nvidia drivers would work as well, but I've been using 81.95 since it's initial release without problems (until about a week ago.) Why would this all of sudden happen with drivers?

I'll start posting the 1001 and 1003 events below

 

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 4/30/2006
Time: 11:38:54 PM
User: N/A
Computer: KEVINAMD
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x80f3a000, 0x00000002, 0x00000000, 0xb9cd1c06). A dump was saved in: C:\WINDOWS\MEMORY.DMP.


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 4/26/2006
Time: 4:23:11 PM
User: N/A
Computer: KEVINAMD
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini042606-03.dmp.

These pop up in my event viewer 10 times

Here are samples of the 1003:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 4/26/2006
Time: 4:23:33 PM
User: N/A
Computer: KEVINAMD
Description:
Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 38 2c 20 000008,
0038: 38 30 30 34 32 30 30 30 80042000
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000


These show up identically at different times. 9 times total. Also with the 1003 are DCHP warnings, in which deal with my computer trying to renew it's address.

Any more insight on this problem anyone?

 

Cany anyone help out? Please?

 

Use kd or windbg to process the minidump. Attach the output of the bebug log here.

c:\program files\debugging tools>kd -z C:\windows\Minidump\Minixxxxx-nn.dmp
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;!thread;.logclose;q

 

Is this what is required? Thanks for being patient with me. Debugging is completely new to me.



Opened log file 'c:\debuglog.txt'
kd> kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Numeric expression missing from '> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols'
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
WARNING: Whitespace at end of path element
kd> .reload;!analyze -v;r;!thread;.logclose;q
Loading Kernel Symbols
...............................................Unable to load image \SystemRoot\system32\DRIVERS\nv4_mini.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
..................................................................................
Loading User Symbols
Loading unloaded module list
............
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 89d416f0 to b265d4e3

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacc4ffc 89d416f0 00000007 00000001 00000007 nv4_mini+0x374e3
00000000 00000000 00000000 00000000 00000000 0x89d416f0


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini+374e3
b265d4e3 ?? ???

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_mini+374e3

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43751a19

FAILURE_BUCKET_ID: 0x7f_8_nv4_mini+374e3

BUCKET_ID: 0x7f_8_nv4_mini+374e3

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

eax=00000000 ebx=89d426d8 ecx=00000000 edx=89d416f0 esi=00000007 edi=00000001
eip=b265d4e3 esp=bacc5000 ebp=00000000 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nv4_mini+0x374e3:
b265d4e3 ?? ???
GetPointerFromAddress: unable to read from 80880e34
890a8da8 is not a thread object, interpreting as stack value...
Unable to read @ 808824d8
TYPE mismatch for thread object at 890a8da8
Closing open log file c:\debuglog.txt

 

Running it from the other minidump, I got this:


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 00000000 to b07824e3

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x374e3


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini+374e3
b07824e3 e878ffffff call nv4_mini+0x37460 (b0782460)

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_mini+374e3

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43751a19

FAILURE_BUCKET_ID: 0x7f_8_nv4_mini+374e3

BUCKET_ID: 0x7f_8_nv4_mini+374e3

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

eax=00000000 ebx=89c3e2e8 ecx=00000000 edx=89c3d6f0 esi=00000007 edi=00000001
eip=b07824e3 esp=bacc5000 ebp=00000000 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nv4_mini+0x374e3:
b07824e3 e878ffffff call nv4_mini+0x37460 (b0782460)
GetPointerFromAddress: unable to read from 80880e34
THREAD 8941a020 Cid 034c.0cac Teb: 7ffde000 Win32Thread: e12a7bb0 RUNNING on processor 0
IRP List:
Unable to read nt!_IRP @ 88d919a8
Not impersonating
GetUlongFromAddress: unable to read from 80880e44
Owning Process 893e6020 Image: BF2.exe
ffdf0000: Unable to get shared data
Wait Start TickCount 455948
Context Switch Count 490041 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.0000
KernelTime 00:00:00.0000
Start Address 0x7c810635
Win32 Start Address 0x00ab206e
Stack Init a7abf000 Current a7abeb20 Base a7abf000 Limit a7aba000 Call 0
Priority 8 BasePriority 8 PriorityDecrement 0 DecrementCount 16
ChildEBP RetAddr Args to Child
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x374e3

Closing open log file c:\debuglog.txt

 

Your minidump does not contain the thread informaton.
>>
GetPointerFromAddress: unable to read from 80880e34
890a8da8 is not a thread object, interpreting as stack value...
Unable to read @ 808824d8
TYPE mismatch for thread object at 890a8da8
<<


Can you process the another minidump and do you get the same result?


A sample output of thread information
kd> !thread
GetPointerFromAddress: unable to read from 8055ee34
THREAD 82d047b0 Cid 00f0.00ec Teb: 7ffdd000 Win32Thread: e17fb490 RUNNING on processor 0
IRP List:
Unable to read nt!_IRP @ 82f2bab8
Not impersonating
GetUlongFromAddress: unable to read from 8055ee44
Owning Process 82f1b9f0 Image: hl.exe
ffdf0000: Unable to get shared data
Wait Start TickCount 185736
Context Switch Count 158363 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.0000
KernelTime 00:00:00.0000
Start Address 0x7c810867
Win32 Start Address 0x01403811
Stack Init f6927000 Current f6926d44 Base f6927000 Limit f6918000 Call 0
Priority 11 BasePriority 8 PriorityDecrement 0 DecrementCount 0
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
f6926d30 805780dc 00000074 804de7ec 000007c4 0xa6a4bc
f6926d3c 00000000 00000000 00000000 00000000 nt!NtWriteFile+0x7 (FPO: [Non-Fpo])

 

Ok, I made another logfile using dbgwiz and analyzed it again using those commands you supplied. This was a minidump that was 3 crashes ago. Here's what the output is. Am I doing this right? Again, sorry for my inexperience on these.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 00000000 to b2a594e3

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x374e3


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini+374e3
b2a594e3 e878ffffff call nv4_mini+0x37460 (b2a59460)

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_mini+374e3

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43751a19

FAILURE_BUCKET_ID: 0x7f_8_nv4_mini+374e3

BUCKET_ID: 0x7f_8_nv4_mini+374e3

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

eax=00000000 ebx=89b844f8 ecx=00000000 edx=89b6d8d8 esi=00000007 edi=00000001
eip=b2a594e3 esp=bacc5000 ebp=00000000 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nv4_mini+0x374e3:
b2a594e3 e878ffffff call nv4_mini+0x37460 (b2a59460)
GetPointerFromAddress: unable to read from 80557e34
THREAD 88dfabc8 Cid 088c.08c8 Teb: 7ffdf000 Win32Thread: e29795e8 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from 80557e44
Owning Process 89b92da0 Image: Maxthon.exe
ffdf0000: Unable to get shared data
Wait Start TickCount 49483
Context Switch Count 29462 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.0000
KernelTime 00:00:00.0000
Start Address 0x7c810635
Win32 Start Address 0x0061a360
Stack Init a7132bd0 Current a7132670 Base a7133000 Limit a712c000 Call a7132bd4
Priority 8 BasePriority 8 PriorityDecrement 0 DecrementCount 16
ChildEBP RetAddr Args to Child
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x374e3

Closing open log file c:\debuglog.txt

 

Well, nevermind everyone. I appreciate all of the help these past days.

After looking all over, I was finally able to find someone who had a similar system to mine. I threw in my BFG card, and guess what happened to his computer? Crash. This video card is a pile of junk.

I will never buy another BFG card in my life. One blew up one me, I RMA'ed it, and they sent me another one. This one is crashing my computer. What a pile of **** company.

Thanks again guys. I really really appreciate your help!

 

Not stack overflow

The crashes does not relate to stack overflow as the stack has a lot of space. It implies the double fault is related to hardware error. You find out the problem is related to video card problem. Repost if you need further help.

>>
Stack Init a7132bd0 Current a7132670 Base a7133000 Limit a712c000 Call a7132bd4
<<