Frustrating BSOD on start up

Hi.

I have had a start up problem for some time. Computer keeps crashing on start up.

After 7 or 8 attempts, sometimes using the repair routine, it will eventually start having crashed with BSOD a number of times.

I have run memtest and hard disk check.

Latest files attached in zip file.

Any help really appreciated.

Hi,

For some reason the collection application did not pick up any BSOD minidumps (it does this occasionally). Can you check C:\Windows\Minidump and upload anything you find there.

If there is nothing there and you have definitely got bluescreens then can you check the settings mentioned in this post to see if your system is set up correctly to collect dump files when it Blue Screens.

From your event logs I can see that you have had plenty of BSODs:

Code:

0x0000003b (0x00000000c0000005, 0xfffff800031b8a2f, 0xfffff88005e4a0c0, 0x0000000000000000)
0x00000050 (0xfffff8a0044344d4, 0x0000000000000000, 0xfffff8000316656d, 0x0000000000000000)
0x0000001a (0x0000000000005001, 0xfffff70001080000, 0x0000000000000695, 0x00000696fffffefe)
0x00000050 (0xfffff8a003dbfa9c, 0x0000000000000000, 0xfffff8000315c56d, 0x0000000000000000)
0x0000003b (0x00000000c0000005, 0xfffff8000315256d, 0xfffff88008c83750, 0x0000000000000000)
0x0000007e (0xffffffffc0000005, 0xfffff80002ef2ba0, 0xfffff880031854c8, 0xfffff88003184d30)
0x00000050 (0xfffff8a003e7b84c, 0x0000000000000000, 0xfffff800031a056d, 0x0000000000000000)
0x0000003b (0x00000000c0000005, 0xfffff960001b0768, 0xfffff880086b9020, 0x0000000000000000)
0x00000050 (0xfffff8a0030f8b9c, 0x0000000000000000, 0xfffff800031a056d, 0x0000000000000000)
0x0000003b (0x00000000c0000005, 0xfffff800031a256d, 0xfffff88007b90750, 0x0000000000000000)
0x00000050 (0xfffff8a003bbacec, 0x0000000000000000, 0xfffff800031a256d, 0x0000000000000000)
0x0000003b (0x00000000c0000005, 0xfffff80002ed9805, 0xfffff880090b4990, 0x0000000000000000)
0x0000007e (0xffffffffc0000005, 0xfffff88003e37c30, 0xfffff880031626c8, 0xfffff88003161f30)
0x0000003b (0x00000000c0000005, 0xfffff80002ffb90d, 0xfffff88004728e90, 0x0000000000000000)
0x0000007e (0xffffffffc0000005, 0xfffff8000316e4fc, 0xfffff88003185988, 0xfffff880031851f0)
0x000000c2 (0x0000000000000007, 0x0000000000001097, 0x00000000251d0000, 0xfffff900c0b0b010)
0x000000c2 (0x0000000000000099, 0xfffff8a0146ae240, 0x0000000000000000, 0x0000000000000000)
0x00000027 (0x00000000baad0073, 0xfffff88003b81bc8, 0xfffff88003b81430, 0xfffff80002ffb90d)
0x0000001e (0xffffffffc0000005, 0xfffff9600027aad8, 0x0000000000000000, 0xffffffffffffffff)
0x0000001a (0x0000000000005003, 0xfffff780c0000000, 0x00000000000050a4, 0x000050a60000a048)
0x0000003b (0x00000000c0000005, 0xfffff960001150b2, 0xfffff88006fbaa90, 0x0000000000000000)
0x000000f4 (0x0000000000000003, 0xfffffa800a1e5b30, 0xfffffa800a1e5e10, 0xfffff800031d5540)
0x0000003b (0x00000000c0000005, 0xfffff80002ff30bf, 0xfffff880085e3c80, 0x0000000000000000)
0x0000007e (0xffffffffc0000005, 0xfffff800031c34fc, 0xfffff88003185988, 0xfffff880031851f0)
0x0000007e (0xffffffffc0000005, 0xfffff8800109f920, 0xfffff880031695a8, 0xfffff88003168e10)
0x0000001a (0x0000000000005003, 0xfffff780c0000000, 0x00000000000016a8, 0x000009cc00002c50)
0x000000c2 (0x0000000000000007, 0x0000000000001097, 0x0000000000040102, 0xfffff8a00729bc10)
0x00000050 (0xfffff8a0075a64d4, 0x0000000000000000, 0xfffff800031ac56d, 0x0000000000000000)
0x0000003b (0x00000000c0000005, 0xfffff80002f6b56d, 0xfffff8800b48c750, 0x0000000000000000)
0x00000050 (0xfffff90100282310, 0x0000000000000000, 0xfffff960000ecc52, 0x0000000000000005)

Most of those mention memory corruption. The main causes for this on your system would be either Norton or a Hardware fault.

So, remove Norton . . .

Download the Norton Removal Tool (NRT); save to desktop. Boot into SAFEMODE - NO Networking. Tap F8 key during boot-up. Then go to desktop, RIGHT-click on the NRT icon and select Run as Administrator.

When complete - re-boot.

NRT - ftp://ftp.symantec.com/public/englis...moval_Tool.exe

Install MS Security Essentials --> http://www.microsoft.com/Security_Essentials/

Then reset the Windows Firewall to its default settings -
START -> type cmd.exe -> right-click -> run as administrator -> type netsh advfirewall reset press enter

. . . and run a Memtest

Memtest - Instructions:

Download the ISO (or the .exe for USB drives) from here Memtest86+ - Advanced Memory Diagnostic Tool

Then (if you have chosen the ISO) burn the ISO using IsoRecorder: ISO Recorder v3 Download (How to use IsoRecorder)

Boot from the CD/USB and run the test (at least 7 passes per test) with only one stick of RAM in place at a time.

It is a time consuming process but it is the only way to be sure it isn't a RAM fault.

For your final test, run the test with all the RAM in place.

Regards,
Reventon

Many thanks - will do all of these later today and post the results!!

Thanks.

Reventon,

Thanks. I have re-run the tool and I think it has now picked up the mini dumps attached.

Are they of any more use?

I will in the meantime run the memtst on each memory stick and then remove Norton (although I really like it!)

All the best.

Hi - do the mini dumps show anything different that I need to so?

Hi,

The only 3rd Party drivers mentioned in the dumps were symsnap.sys and eeCtrl64.sys both part of Norton/Symantec.

If you are still getting BSODs then there is another hidden cause - run Driver Verifier to try and bring it out into the open.

Regards,
Reventon

BUGCHECK SUMMARY

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Aug 12 06:44:21.061 2010 (GMT+12)
System Uptime: 0 days 0:04:13.684
BugCheck 1A, {5003, fffff780c0000000, 4285, 4a3e0000840a}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a1ef )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Aug 12 06:09:59.272 2010 (GMT+12)
System Uptime: 0 days 0:06:30.895
BugCheck 1E, {ffffffffc0000005, fffff88014b2b2d4, 1, 0}
Probably caused by : hardware ( dxgkrnl!DXGPRESENT::PrepareStagingBuffer+1b8 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  rundll32.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Aug 12 06:02:23.538 2010 (GMT+12)
System Uptime: 0 days 0:01:26.162
BugCheck 1000007E, {ffffffffc0000005, fffff800031ca4fc, fffff88003185988, fffff880031851f0}
Probably caused by : ntkrnlmp.exe ( nt!CmpRemoveKeyHash+4c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 06:11:28.979 2010 (GMT+12)
System Uptime: 0 days 0:01:53.618
BugCheck 50, {fffff8a0044344d4, 0, fffff8000316656d, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 06:08:46.050 2010 (GMT+12)
System Uptime: 0 days 0:01:38.689
BugCheck 1A, {5001, fffff70001080000, 695, 696fffffefe}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29961 )
BUGCHECK_STR:  0x1a_5001
PROCESS_NAME:  vds.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 06:06:04.194 2010 (GMT+12)
System Uptime: 0 days 0:01:49.567
BugCheck 50, {fffff8a003dbfa9c, 0, fffff8000315c56d, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 06:03:10.719 2010 (GMT+12)
System Uptime: 0 days 0:02:45.108
BugCheck 3B, {c0000005, fffff8000315256d, fffff88008c83750, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  hsplayer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 05:59:23.835 2010 (GMT+12)
System Uptime: 0 days 0:10:01.459
BugCheck 1000007E, {ffffffffc0000005, fffff80002ef2ba0, fffff880031854c8, fffff88003184d30}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetNext+5b )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 05:48:20.207 2010 (GMT+12)
System Uptime: 0 days 0:02:17.581
BugCheck 50, {fffff8a0050b184c, 0, fffff8000315656d, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x50
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 05:44:59.064 2010 (GMT+12)
System Uptime: 0 days 0:01:07.453
BugCheck 50, {fffff8a003e7b84c, 0, fffff800031a056d, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x50
PROCESS_NAME:  ie4uinit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 05:40:44.240 2010 (GMT+12)
System Uptime: 0 days 0:00:53.879
BugCheck 3B, {c0000005, fffff960001b0768, fffff880086b9020, 0}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x3B
PROCESS_NAME:  NOBuAgent.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 11 05:39:12.248 2010 (GMT+12)
System Uptime: 0 days 0:03:32.887
BugCheck 24, {1904fb, fffff88008f42298, fffff88008f41b00, fffff880012af933}
*** WARNING: Unable to verify timestamp for symsnap.sys
*** ERROR: Module load completed but symbols could not be loaded for symsnap.sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+213 )
PROCESS_NAME:  VProSvc.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 17:33:44.502 2010 (GMT+12)
System Uptime: 0 days 0:01:30.876
BugCheck 50, {fffff8a0030f8b9c, 0, fffff800031a056d, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x50
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 17:31:09.769 2010 (GMT+12)
System Uptime: 0 days 0:01:34.407
BugCheck 3B, {c0000005, fffff800031a256d, fffff88007b90750, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 17:28:55.422 2010 (GMT+12)
System Uptime: 0 days 0:01:50.045
BugCheck 50, {fffff8a003bbacec, 0, fffff800031a256d, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x50
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 17:26:20.966 2010 (GMT+12)
System Uptime: 0 days 0:04:24.605
BugCheck 3B, {c0000005, fffff80002ed9805, fffff880090b4990, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug  3 17:41:48.193 2010 (GMT+12)
System Uptime: 0 days 0:00:17.582
*** WARNING: Unable to verify timestamp for eeCtrl64.sys
*** ERROR: Module load completed but symbols could not be loaded for eeCtrl64.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88003e37c30, fffff880031626c8, fffff88003161f30}
Probably caused by : eeCtrl64.sys ( eeCtrl64+24c30 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 23:02:18.389 2010 (GMT+12)
System Uptime: 0 days 2:12:53.028
BugCheck 1A, {5003, fffff70001080000, 982, a3e00001204}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b86 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  VProSvc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 20:48:46.344 2010 (GMT+12)
System Uptime: 0 days 0:03:36.967
BugCheck 3B, {c0000005, fffff80002ffb90d, fffff88004728e90, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+53d )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  services.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 20:44:29.594 2010 (GMT+12)
System Uptime: 0 days 0:01:16.232
BugCheck 1000007E, {ffffffffc0000005, fffff8000316e4fc, fffff88003185988, fffff880031851f0}
Probably caused by : ntkrnlmp.exe ( nt!CmpRemoveKeyHash+4c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 20:35:12.805 2010 (GMT+12)
System Uptime: 0 days 0:02:37.428
BugCheck C2, {7, 1097, 251d0000, fffff900c0b0b010}
Probably caused by : win32k.sys ( win32k!FreeObject+58 )
BUGCHECK_STR:  0xc2_7_Gh14
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 19:59:55.246 2010 (GMT+12)
System Uptime: 0 days 1:48:53.620
BugCheck C2, {99, fffff8a0146ae240, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpFreeKeyControlBlock+123 )
BUGCHECK_STR:  0xc2_99
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

  

Reventon

Thanks again. I'll get on with all of this now and post back - I may be a few days!

Is there a known issue with NIS and Windows 7? Is Microsoft Security Essentials good enough as my only security package - I feel a bit nervous about it.

Regards.

slater said:

Reventon

Thanks again. I'll get on with all of this now and post back - I may be a few days!

Is there a known issue with NIS and Windows 7? Is Microsoft Security Essentials good enough as my only security package - I feel a bit nervous about it.

Regards.

Antivirus Review - AV-Comparatives picks six malware removal winners

MSE rates the same as Norton in terms of detection.