BSOD Nightmare!

Nannoir · Aug 1, 2010

Hey everyone!

I've been getting BSOD's ever since last week and it's been a real annoyance. I really don't know what prompted these BSOD's; perhaps it had something to do with my weekly anti-virus/spyware updates. I've even taken desperate measures and re-installed (clean install, by the way) Windows 7 (64-bit) yesterday; hoping it'll fix everything. Unfortunately, it hasn't.

My computer has never given me any problems and it's relatively new (bought it almost two years ago). Hopefully you guys can help. I'm at my wits end.

I don't know if it'll help, but here are the following anti-virus/spyware programs I use:

Avast
Malwarebytes
Spybot

I also use Comodo's firewall and CCleaner.

Thanks.

zigzag3143 · Aug 1, 2010

Nannoir said:
Hey everyone!

I've been getting BSOD's ever since last week and it's been a real annoyance. I really don't know what prompted these BSOD's; perhaps it had something to do with my weekly anti-virus/spyware updates. I've even taken desperate measures and re-installed Windows 7 (clean install) yesterday; hoping it'll fix everything. Unfortunately, it hasn't.

My computer has never given me any problems and it's relatively new (bought it almost two years ago). Hopefully you guys can help. I'm at my wits end.

I don't know if it'll help, but here are the following anti-virus/spyware programs I use:

Avast

Malwarebytes

Spybot

I also use Comodo's firewall and CCleaner.

Thanks.

This crash is fairly straight forward Memory management. To test yours;
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Ken

Jonathan_King · Aug 1, 2010

Please enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Third party anti-virus programs and firewalls are notorious for causing crashes on Vista and 7 systems. To eliminate as much as possible, please remove them. If you later determine they were not the cause, go ahead and reinstall them if you like.

Avast removal tool: http://files.avast.com/files/eng/aswclear5.exe

MBAM removal too: http://www.malwarebytes.org/mbam-clean.exe | Note: This tool is meant to be used after a normal uninstall of MBAM and a reboot.

Install the free Microsoft Security Essentials instead: http://www.microsoft.com/security_essentials

...Summary of the Dumps:

Code:

[/SIZE][FONT=lucida console][SIZE=2]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 31 23:29:40.539 2010 (UTC - 4:00)
System Uptime: 0 days 3:23:29.801
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/SIZE][/FONT][SIZE=2]

Nannoir · Aug 1, 2010

zigzag3143 said:
Nannoir said:

Hey everyone!

I've been getting BSOD's ever since last week and it's been a real annoyance. I really don't know what prompted these BSOD's; perhaps it had something to do with my weekly anti-virus/spyware updates. I've even taken desperate measures and re-installed Windows 7 (clean install) yesterday; hoping it'll fix everything. Unfortunately, it hasn't.

My computer has never given me any problems and it's relatively new (bought it almost two years ago). Hopefully you guys can help. I'm at my wits end.

I don't know if it'll help, but here are the following anti-virus/spyware programs I use:

Avast

Malwarebytes

Spybot

I also use Comodo's firewall and CCleaner.

Thanks.

Click to expand...

This crash is fairly straight forward Memory management. To test yours;
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Ken

Hey Ken,
Just finished the Memtest86 scan (which lasted for two hours), and surprisingly, there are no errors. Weird.

Anyway, I'm going to uninstall Avast/Malwarebytes/Comodo to see if it'll help my situation.

Also, Jonathan_King, the "driver verifier" thread you linked sounds intimidating.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

Is it absolutely necessary to enable the driver verifier? Are there other ways around it? But if uninstalling my anti-virus/spyware programs won't work, then I suppose I might have to try it.

Wish me luck.

Thanks for the quick responses! I really appreciate it.

Jonathan_King · Aug 1, 2010

That tutorial isn't quite accurate...there is no reason to fear using it. Go ahead and enable it.

Nannoir · Aug 1, 2010

Okay. I've uninstalled Avast, Malwarebyes, Spybot and Comodo, and installed Microsoft Security Essentials at your suggestion. And I've also enabled the Driver Verifier.

Now the waiting begins...

Nannoir · Aug 2, 2010

I've left my computer on for a day now. There were no BSOD's and everything seemed to be fine, until my computer froze. Along with the numerous BSOD's I'd received since last week, my computer also freezes. How fun.

I forgot to mention it in my previous posts, but on several occasions, normally after a freeze, my monitor would become static-y. I don't know how to explain it exactly, so I've attached a picture.

Anyway, after I manually rebooted my computer today, I went into the minidump file in Windows to see if there had been any recent BSOD's when I was away. No new BSOD's; just that one "memory management" BSOD from yesterday.

I'm absolutely fed up with this computer and I'm at a loss of what to do. Hopefully someone can help.

And another thing before I go; Windows 7 isn't the original OS for my computer. Windows Vista was.

Jonathan_King · Aug 2, 2010

Make sure your monitor cable is plugged in securely, and your video card seated properly.

Nannoir · Aug 3, 2010

Another day, and no BSOD's. Not even one. Aside from my computer randomly freezing yesterday, nothing has happened.

I took your advice and checked my monitor to see if it is securely plugged and opened my computer to see if my video card is seated properly. Cleaned the dusty insides with a can of air duster, and with the help from my tech savvy brother, we checked to see if anything was off. Nothing was out of the ordinary, so we closed up the computer and plugged everything back.

I did move the monitor closer to the edge of my desk recently (before the invasion of BSOD's); and I guess the movement might have loosen the plug or something. But I find it strange that a loose monitor plug could be the cause of all these BSOD's and freezes.

Anyway, everything seems to be securely in place and I haven't received any BSOD's yet. I'll report to this thread when anything happens.

By the way, should I turn off the Driver Verifier now that it has been a couple of days? And reinstall the anti-virus/anti-spyware programs? My computer feels kind of naked and vulnerable with just MSE and Windows Firewall. lol

Jonathan_King · Aug 3, 2010

Yes, go ahead and turn off Verifier.

Do not reinstall the other security programs. Honestly, MSE is so lightweight it doesn't seem like it's protecting you, but it is. Look up its detection rates!

The Windows Firewall is just as secure as others, but it lacks the features, like telling you when a programs tries to access the internet.

Nannoir · Aug 6, 2010

Ok my computer was fine until a few minutes ago. I got another nasty BSOD.

I have attached the minidump file to this post.

Jonathan_King · Aug 6, 2010

It appears as if a bad driver caused it, but the debugger does not blame one outright.

If I had to take a bet on what it is, I would put my money on PC Doctor, so go ahead and remove that completely.

If that doesn't work, enable driver verifier again: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 1 for 080610-20186-01 (1).zip\080610-20186-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Fri Aug  6 20:05:29.803 2010 (GMT-4)
System Uptime: 0 days 0:04:12.660
Loading Kernel Symbols
...............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff3000c1fa898, 1, fffff880050bdfb5, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40e4b )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff3000c1fa898, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880050bdfb5, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d090e0
 fffff3000c1fa898 

FAULTING_IP: 
+325952f00e9dfdc
fffff880`050bdfb5 4889442440      mov     qword ptr [rsp+40h],rax

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002edc340 -- (.trap 0xfffff88002edc340)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800931e388 rbx=0000000000000000 rcx=fffff8a001632000
rdx=fffff88002edc510 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880050bdfb5 rsp=fffff88002edc4d0 rbp=0000000040000040
 r8=0000000000000001  r9=0000000000000000 r10=fffff80002a61000
r11=fffff8a001632000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff880`050bdfb5 4889442440      mov     qword ptr [rsp+40h],rax ss:0018:fffff880`02edc510=fffffa800931e388
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b50789 to fffff80002ad1600

STACK_TEXT:  
fffff880`02edc1d8 fffff800`02b50789 : 00000000`00000050 fffff300`0c1fa898 00000000`00000001 fffff880`02edc340 : nt!KeBugCheckEx
fffff880`02edc1e0 fffff800`02acf6ee : 00000000`00000001 00000000`00000000 fffffa80`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e4b
fffff880`02edc340 fffff880`050bdfb5 : 3d8836ad`3d90f60e 3d869507`3d9452ed fffff8a0`01638010 fffff8a0`01638010 : nt!KiPageFault+0x16e
fffff880`02edc4d0 3d8836ad`3d90f60e : 3d869507`3d9452ed fffff8a0`01638010 fffff8a0`01638010 3b67e19c`3b2acd1b : 0xfffff880`050bdfb5
fffff880`02edc4d8 3d869507`3d9452ed : fffff8a0`01638010 fffff8a0`01638010 3b67e19c`3b2acd1b bc85eb08`bc949ae3 : 0x3d8836ad`3d90f60e
fffff880`02edc4e0 fffff8a0`01638010 : fffff8a0`01638010 3b67e19c`3b2acd1b bc85eb08`bc949ae3 3c0b299a`3bf3b781 : 0x3d869507`3d9452ed
fffff880`02edc4e8 fffff8a0`01638010 : 3b67e19c`3b2acd1b bc85eb08`bc949ae3 3c0b299a`3bf3b781 00000000`00000000 : 0xfffff8a0`01638010
fffff880`02edc4f0 3b67e19c`3b2acd1b : bc85eb08`bc949ae3 3c0b299a`3bf3b781 00000000`00000000 fffffa80`0931e388 : 0xfffff8a0`01638010
fffff880`02edc4f8 bc85eb08`bc949ae3 : 3c0b299a`3bf3b781 00000000`00000000 fffffa80`0931e388 00000000`00000000 : 0x3b67e19c`3b2acd1b
fffff880`02edc500 3c0b299a`3bf3b781 : 00000000`00000000 fffffa80`0931e388 00000000`00000000 fffffa80`093fdb60 : 0xbc85eb08`bc949ae3
fffff880`02edc508 00000000`00000000 : fffffa80`0931e388 00000000`00000000 fffffa80`093fdb60 fffff800`02ad74da : 0x3c0b299a`3bf3b781


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+40e4b
fffff800`02b50789 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+40e4b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40e4b

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40e4b

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

2: kd> lmnt
start             end                 module name
fffff800`00ba3000 fffff800`00bad000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff800`02a18000 fffff800`02a61000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff800`02a61000 fffff800`0303d000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`00c2a000 fffff880`00c37000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`00c37000 fffff880`00c4b000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`00c4b000 fffff880`00ca9000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00ca9000 fffff880`00d69000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`00d69000 fffff880`00d79000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`00d79000 fffff880`00d93000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00d93000 fffff880`00dbd000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00dbd000 fffff880`00de8000   nvstor   nvstor.sys   Wed May 20 02:45:37 2009 (4A13A711)
fffff880`00e00000 fffff880`00e15000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e15000 fffff880`00e2a000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e2a000 fffff880`00e86000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`00e86000 fffff880`00e8d000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e8d000 fffff880`00e96000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e98000 fffff880`00f3c000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f3c000 fffff880`00f4b000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f4b000 fffff880`00fa2000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00fa2000 fffff880`00fab000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fab000 fffff880`00fb5000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`00fb5000 fffff880`00fe8000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fe8000 fffff880`00ff5000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01027000 fffff880`01089000   storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE)
fffff880`01089000 fffff880`01094000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`01094000 fffff880`010e0000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`010e0000 fffff880`010f4000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`010f4000 fffff880`01152000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`01152000 fffff880`011c5000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01248000 fffff880`013eb000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01430000 fffff880`01522000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01522000 fffff880`01582000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`01582000 fffff880`015ad000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`015ad000 fffff880`015f7000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`01853000 fffff880`0189f000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`0189f000 fffff880`018a7000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`018a7000 fffff880`018e1000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`018e1000 fffff880`018f3000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`018f3000 fffff880`018fc000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`018fc000 fffff880`01936000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`01936000 fffff880`0194c000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0194c000 fffff880`0197c000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`019d2000 fffff880`019fc000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)

Unloaded modules:
fffff880`06800000 fffff880`0680b000   pcdsrvc_x64.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0197c000 fffff880`0198a000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0198a000 fffff880`01994000   dump_storpor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01994000 fffff880`019bf000   dump_nvstor.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`019bf000 fffff880`019d2000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Nannoir · Aug 17, 2010

I have arrived with BSOD goodies for everyone.

I've been receiving BSOD's for the past couple of days. I really don't know what to do with this computer anymore; and I'm seriously considering getting a new machine. Perhaps someone can review the recent minidumps I've attached to this post and share some light as to what is happening to my computer.

Thank you, Jonathan, for helping me. I really do appreciate it.

Before I go, I should add that I disabled my internet connections yesterday, and it seemed to stop BSOD's from appearing. Does my internet have something to do with these problems? Maybe it's the driver or something? Sorry--I'm not too smart when it comes computer terminology.

Jonathan_King · Aug 17, 2010

One dump did blame tcpip.sys, which is a Windows networking driver. That supports the evidence of the networking adapter being the cause.

Your nVidia networking drivers are very old:

Code:

nvm62x64.sys Fri Oct 17 17:01:06 2008

Go ahead and install the latest nForce drivers. Try this: http://us.download.nvidia.com/Windo...ce_winvista_win7_64bit_international_whql.exe

...Summary of the Dumps:

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 16 20:14:56.254 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:31.501
BugCheck 1000007E, {ffffffffc0000005, fffff8800515fcee, fffff880043cc6a8, fffff880043cbf10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Aug 17 18:09:01.400 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:56.648
BugCheck A, {97f, 2, 0, fffff80002acf96d}
Probably caused by : tcpip.sys ( tcpip!TcpRestructureHashTable+53 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 16 20:07:30.098 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:28.345
BugCheck 1A, {5003, fffff70001080000, c6f, c70000018ce}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29731 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  LogonUI.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

BSOD Nightmare!

New member

My Computer

Account closed by request

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer