The screen of blue

[umax]

Hello there!

I built a computer about a year ago, but had not the chance to actually play around with it until now, it was at a friends house and he was using it and he told me about it having a lot of BSOD issues.

Anyways, now that I'm back and I've exhausted the resources I have with dealing with BSOD (which isn't much, I dont know how to read dump files ) -

Things I've tried
1) Virus/malware scan - returned 0 problems
2) Memory scan - I scanned all the sticks and they all checked good.
3) Updating drivers - I suspected an old video/audio driver so I updated them to no avail.


*I've been having problems with 1 of my harddrives corrupting files as well. I figured it could be linked, but I ran a few checks on it and its returning good. I usually just run chkdsk and it repairs the problems with the drive and its good to go again.

**Also the computer has been skipping for a lack of better words? It usually does it while doing multiple processor heavy things such as watching a movie, playing music, or playing a game.

I'm pretty sure they're all linked but I lack the experience with these problems to solve it

Here's the last BSOD that I had.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFFA600670A807
BCP3: FFFFFA60101A5FC0
BCP4: 0000000000000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini082210-01.dmp
C:\Users\Silver\AppData\Local\Temp\WER-73663-0.sysdata.xml
C:\Users\Silver\AppData\Local\Temp\WER3552.tmp.version.txt

I've attached the dump folder(you'll see that the BSOD is pretty frequent from the folder) and system info to this. Any help would be GREATLY appreciated.

 

[usasma]

56 memory dumps from 04 Nov 2009 to the present
Approximately 12 different BSOD error codes with at least 11 different causes blamed.
This is a hardware/compatibility error.

Unfortunately, the Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following (this will not affect the analysis of the current files - but it may help later files that are acquired):
- activate/validate the Windows installation at http://www.microsoft.com/genuine
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( http://support.microsoft.com/ph/14019 )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Start with these free diagnostics. Follow the directions at the links as they are likely to be different than the tests that you've run.

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

 

[usasma]

Due to the symbol issues, the memory dumps are still running.
I will post back with the results when they finish......

 

[usasma]

Please visit the hardware manufacturer's website and update your drivers. Also ensure that you visit Windows Update and get all available updates.

FYI - This is a list of the older drivers present in the memory dump files:

fffffa60`00fe9000 fffffa60`00ff1000 AtiPcie AtiPcie.sys Mon Nov 06 11:59:54 2006 (454F6A0A)
fffffa60`009c2000 fffffa60`009c9000 amdide64 amdide64.sys Thu Oct 11 21:40:08 2007 (470ED078)
fffffa60`09b1e000 fffffa60`09b29180 RecFltr RecFltr.sys Wed Jan 17 20:23:09 2007 (45AECBFD)
fffffa60`06d6c000 fffffa60`06d8a000 Rtlh64 Rtlh64.sys Mon Jun 25 01:37:13 2007 (467F5489)
fffffa60`009e4000 fffffa60`009ff000 jraid jraid.sys Mon Nov 03 21:20:09 2008 (490FB159)
fffffa60`00bd3000 fffffa60`00be6000 processr processr.sys Sat Jan 19 00:52:45 2008 (4791902D)
fffffa60`07322000 fffffa60`0734ee00 RtHDMIVX RtHDMIVX.sys Thu Dec 25 04:30:47 2008 (495352C7)
fffffa60`09b9b000 fffffa60`09bb6000 dump_JRAID dump_JRAID.sys Mon Nov 03 21:20:09 2008 (490FB159)
fffffa60`0c43b000 fffffa60`0c444000 gdrv gdrv.sys Fri Dec 05 19:57:14 2008 (4939CDEA)
fffffa60`0677f000 fffffa60`067b0000 Rtlh64 Rtlh64.sys Mon Nov 10 07:26:28 2008 (49182874)

BSOD BUGCHECK SUMMARY

[font=lucida console]
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Sun Aug 22 14:42:49.537 2010 (UTC - 4:00)
System Uptime: 1 days 8:57:15.943
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 3B, {c0000005, fffffa600670a807, fffffa60101a5fc0, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl+b9807 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Fri Aug 20 19:39:10.605 2010 (UTC - 4:00)
System Uptime: 1 days 4:34:50.142
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 50, {fffff7fffa8d3d80, 8, fffff7fffa8d3d80, 2}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!EngRestoreFloatingPointState+1c511 )
BUGCHECK_STR:  0x50
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Thu Aug 19 08:01:12.412 2010 (UTC - 4:00)
System Uptime: 0 days 2:18:05.954
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 3B, {c0000005, fffff800026e27a1, fffffa600bd2ddd0, 0}
Probably caused by : ntkrnlmp.exe ( nt!SeAccessCheck+11a1 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Wed Aug 18 15:43:17.079 2010 (UTC - 4:00)
System Uptime: 0 days 2:04:57.575
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 3B, {c0000005, fffffa6006f4256b, fffffa600cb65ab0, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl+d156b )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Wed Aug 18 13:36:56.168 2010 (UTC - 4:00)
System Uptime: 0 days 19:37:44.503
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 1000007E, {ffffffffc0000005, fffff800029258c5, fffffa6001b16898, fffffa6001b16270}
Probably caused by : ntkrnlmp.exe ( nt!NtWriteFile+ae5 )
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Tue Aug 17 16:47:12.344 2010 (UTC - 4:00)
System Uptime: 0 days 0:37:05.161
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 1E, {ffffffffc0000005, fffffa6000b3c2d9, 0, ffffffffffffffff}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for NETIO.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for tcpip.sys - 
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+39 )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Tue Aug 17 16:08:40.623 2010 (UTC - 4:00)
System Uptime: 0 days 10:57:41.514
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 3D, {0, 0, 0, fffffa6006fd8ef2}
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS - 
Probably caused by : usbohci.sys ( usbohci+1ef2 )
BUGCHECK_STR:  0x3D
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Tue Aug 17 05:09:16.937 2010 (UTC - 4:00)
System Uptime: 0 days 11:24:02.213
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 3B, {c0000005, fffff800026bdbb1, fffffa600c9b4270, 0}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!memset+f86 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Mon Aug 16 17:44:21.002 2010 (UTC - 4:00)
System Uptime: 2 days 3:32:18.237
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 3B, {c0000005, fffffa6006d2d43e, fffffa600f41c960, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl+be43e )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Debug session time: Sat Aug 14 14:11:02.393 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:37.455
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck 50, {fffff7fffa876658, 0, fffff800028ed0a0, 2}
Probably caused by : ntkrnlmp.exe ( nt!NtOpenProcess+920 )
BUGCHECK_STR:  0x50
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Aug 13 16:20:11.718 2010 (UTC - 4:00)
System Uptime: 0 days 2:04:02.864
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3D, {0, 0, 0, fffff800026b24d5}
Probably caused by : ntoskrnl.exe ( nt+5a4d0 )
BUGCHECK_STR:  0x3D
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Aug  4 19:37:52.463 2010 (UTC - 4:00)
System Uptime: 0 days 1:00:15.140
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff80002684200, fffffa600af5d0f0, 0}
Probably caused by : ntoskrnl.exe ( nt+2e200 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Aug  4 18:36:10.626 2010 (UTC - 4:00)
System Uptime: 0 days 2:49:14.876
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffffa6006d35807, fffffa600bac4fc0, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl+b9807 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Aug  4 15:45:30.635 2010 (UTC - 4:00)
System Uptime: 0 days 3:27:33.037
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck BE, {fffffa60001601c6, 1063f8121, fffffa600d307710, b}
Probably caused by : ntoskrnl.exe ( nt+5a4d0 )
BUGCHECK_STR:  0xBE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Aug  4 04:38:58.169 2010 (UTC - 4:00)
System Uptime: 0 days 6:20:40.901
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
BugCheck 1000007E, {ffffffffc0000005, fffffa6008a08d8f, fffffa60019c9418, fffffa60019c8df0}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for TDI.SYS - 
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for NETIO.SYS - 
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : netbt.sys ( netbt+2d8f )
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jul 29 17:51:48.575 2010 (UTC - 4:00)
System Uptime: 2 days 11:07:42.885
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff9600018dbcf, fffffa600a534250, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+cdbcf )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Jul 23 00:03:21.887 2010 (UTC - 4:00)
System Uptime: 5 days 10:55:05.330
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for hal.dll - 
BugCheck 124, {0, fffffa800a66f030, b2754000, 185}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for PSHED.dll - 
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sat Jul 17 12:37:54.505 2010 (UTC - 4:00)
System Uptime: 0 days 0:20:03.223
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff960000d2e59, fffffa600b616fd0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+32e59 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sat Jul 17 12:17:09.874 2010 (UTC - 4:00)
System Uptime: 1 days 18:10:54.565
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1000007E, {ffffffffc0000005, fffff80002509870, fffffa6001b2b808, fffffa6001b2b1e0}
Probably caused by : ntoskrnl.exe ( nt+ad870 )
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jul 15 18:04:50.736 2010 (UTC - 4:00)
System Uptime: 1 days 14:58:26.334
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff800026ffff6, fffffa600ca38010, 0}
Probably caused by : ntoskrnl.exe ( nt+29fff6 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue Jul 13 20:25:27.230 2010 (UTC - 4:00)
System Uptime: 1 days 9:17:34.911
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS - 
BugCheck 1000007E, {ffffffffc0000005, fffffa6006c1f492, fffffa600cc20978, fffffa600cc20350}
Probably caused by : USBPORT.SYS ( USBPORT+1c492 )
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Jul  9 16:50:19.293 2010 (UTC - 4:00)
System Uptime: 0 days 6:02:59.234
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D3, {fffff960002ce210, 2, 0, fffff800024e7b7e}
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+29e210 )
BUGCHECK_STR:  0xD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Jul  9 10:46:03.014 2010 (UTC - 4:00)
System Uptime: 0 days 0:34:53.825
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, 4000, fffffa600c140aa0, 0}
Probably caused by : ntoskrnl.exe ( nt+5a4d0 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jul  8 15:29:50.737 2010 (UTC - 4:00)
System Uptime: 0 days 3:58:36.238
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff800026ded54, fffffa600c5fb1d0, 0}
Probably caused by : ntoskrnl.exe ( nt+289d54 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Jun 30 14:08:12.175 2010 (UTC - 4:00)
System Uptime: 1 days 20:56:43.831
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1E, {ffffffffc0000005, fffff800024764d5, 0, ffffffffffffffff}
Probably caused by : ntoskrnl.exe ( nt+5e4d5 )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon Jun 28 04:30:47.865 2010 (UTC - 4:00)
System Uptime: 4 days 9:31:58.692
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff800026dc348, fffffa60095c5fd0, 0}
Probably caused by : ntoskrnl.exe ( nt+2c9348 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Jun 23 18:58:13.050 2010 (UTC - 4:00)
System Uptime: 0 days 20:42:02.660
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1E, {ffffffffc0000005, fffff800024624d5, 0, ffffffffffffffff}
Probably caused by : ntoskrnl.exe ( nt+5e4d5 )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon Jun 21 11:32:10.715 2010 (UTC - 4:00)
System Uptime: 4 days 9:39:48.930
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff800024556f8, fffffa60072651e0, 0}
Probably caused by : ntoskrnl.exe ( nt+a6f8 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jun 17 01:51:20.835 2010 (UTC - 4:00)
System Uptime: 6 days 5:24:53.369
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff9600010c7b4, fffffa6009d1a110, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+cc7b4 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jun 10 20:19:40.025 2010 (UTC - 4:00)
System Uptime: 0 days 21:34:08.199
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1E, {ffffffffc0000005, fffff800024b54d5, 0, ffffffffffffffff}
Probably caused by : ntoskrnl.exe ( nt+5e4d5 )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon Jun  7 11:56:04.921 2010 (UTC - 4:00)
System Uptime: 7 days 22:34:45.192
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck FC, {fffffa6000a00ffc, 8000000003b76963, fffffa600a6513f0, 2}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
Probably caused by : ntoskrnl.exe ( nt+5a4d0 )
BUGCHECK_STR:  0xFC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sun May 30 13:20:50.083 2010 (UTC - 4:00)
System Uptime: 0 days 6:44:08.016
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff9600015bdcb, fffffa600b6591a0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+cbdcb )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sat May 29 10:58:20.543 2010 (UTC - 4:00)
System Uptime: 1 days 7:26:27.752
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1A, {8887, fffffa8005601900, fffffa8004bfad40, 705}
Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED )
BUGCHECK_STR:  0x1a_8887
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu May 27 00:38:57.483 2010 (UTC - 4:00)
System Uptime: 0 days 21:33:39.876
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D3, {fffff960002aa160, 2, 0, fffff800024e8b7e}
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+29a160 )
BUGCHECK_STR:  0xD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue May 25 09:20:04.586 2010 (UTC - 4:00)
System Uptime: 0 days 21:14:42.268
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1E, {ffffffffc0000005, fffff8000271ac5c, 0, ffffffffffffffff}
Probably caused by : ntoskrnl.exe ( nt+2cfc5c )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue May 11 11:37:41.343 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:20.447
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff9600018c6cc, fffffa600b537290, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+cc6cc )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue May 11 11:14:11.610 2010 (UTC - 4:00)
System Uptime: 1 days 7:49:49.090
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D3, {fffff9600031a160, 2, 0, fffff800024dab7e}
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+29a160 )
BUGCHECK_STR:  0xD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon May 10 03:23:36.510 2010 (UTC - 4:00)
System Uptime: 0 days 18:55:42.821
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff8000247e726, fffffa600c3052e0, 0}
Probably caused by : ntoskrnl.exe ( nt+6e726 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sun May  9 08:26:37.763 2010 (UTC - 4:00)
System Uptime: 0 days 17:06:15.255
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff800026bf365, fffffa600a794c40, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : tcpip.sys ( tcpip+32500 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sat May  8 15:19:34.587 2010 (UTC - 4:00)
System Uptime: 0 days 3:38:08.023
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff800024994b7, fffffa600a235b70, 0}
Probably caused by : ntoskrnl.exe ( nt+3a4b7 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon May  3 12:13:34.018 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:16.695
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1E, {ffffffffc0000005, fffff800024bc1b5, 0, ffffffffffffffff}
Probably caused by : ntoskrnl.exe ( nt+5e1b5 )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Apr 29 01:11:31.883 2010 (UTC - 4:00)
System Uptime: 0 days 13:11:20.556
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D3, {fffff960002da160, 0, 0, fffff80002489b6e}
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+29a160 )
BUGCHECK_STR:  0xD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sun Mar 28 23:07:53.870 2010 (UTC - 4:00)
System Uptime: 1 days 0:06:59.686
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
BugCheck 24, {1904aa, fffffa600c43e5c8, fffffa600c43dfa0, fffffa60010a4411}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
Probably caused by : Ntfs.sys ( Ntfs+99411 )
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sat Mar 27 22:59:35.641 2010 (UTC - 4:00)
System Uptime: 2 days 4:36:23.279
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D3, {fffff9600033a160, 2, 0, fffff8000249fb6e}
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+29a160 )
BUGCHECK_STR:  0xD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Mar 17 08:15:30.653 2010 (UTC - 4:00)
System Uptime: 1 days 15:31:05.646
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D3, {fffff9600033a160, 2, 0, fffff80002499b6e}
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+29a160 )
BUGCHECK_STR:  0xD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Mar  5 14:24:36.916 2010 (UTC - 4:00)
System Uptime: 0 days 18:52:29.048
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff80002530f4a, fffffa6008e21f60, 0}
Probably caused by : ntoskrnl.exe ( nt+e1f4a )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue Feb 23 19:07:12.079 2010 (UTC - 4:00)
System Uptime: 1 days 23:47:39.597
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
BugCheck 24, {1904aa, fffffa600b51afb8, fffffa600b51a990, fffff80002479c38}
*** ERROR: Module load completed but symbols could not be loaded for tunmp.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
Probably caused by : Ntfs.sys ( Ntfs+1264f )
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue Dec 29 17:19:15.950 2009 (UTC - 4:00)
System Uptime: 1 days 23:42:25.977
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff9600011dae7, fffffa600a0bc250, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+cdae7 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sun Dec 27 17:36:05.065 2009 (UTC - 4:00)
System Uptime: 0 days 5:17:34.560
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck A, {7b, 2, 1, fffff80002479031}
Probably caused by : ntoskrnl.exe ( nt+28031 )
BUGCHECK_STR:  0xA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sun Dec 27 04:46:09.797 2009 (UTC - 4:00)
System Uptime: 5 days 0:38:07.691
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff800026d9d4c, fffffa6008e571a0, 0}
Probably caused by : ntoskrnl.exe ( nt+2bbd4c )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue Dec 22 04:07:11.982 2009 (UTC - 4:00)
System Uptime: 1 days 20:49:38.163
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
BugCheck 24, {1904aa, fffffa600c516658, fffffa600c516030, fffff800024a89ef}
Probably caused by : Ntfs.sys ( Ntfs+2010e )
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sun Nov 29 13:19:11.064 2009 (UTC - 4:00)
System Uptime: 2 days 3:13:03.597
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
BugCheck 24, {1904aa, fffffa60019a62b8, fffffa60019a5c90, fffff800024d5016}
Probably caused by : Ntfs.sys ( Ntfs+2010e )
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Nov 27 10:05:27.024 2009 (UTC - 4:00)
System Uptime: 2 days 10:48:56.317
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c0000005, fffff96000086378, fffffa600b708fc0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+46378 )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon Nov 16 21:32:15.715 2009 (UTC - 4:00)
System Uptime: 0 days 6:39:19.650
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1E, {ffffffffc0000005, fffff800022ab1b5, 0, ffffffffffffffff}
Probably caused by : ntoskrnl.exe ( nt+5e1b5 )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sat Nov 14 15:11:05.696 2009 (UTC - 4:00)
System Uptime: 0 days 4:58:13.213
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 50, {fffff7fffa2ecb49, 8, fffff7fffa2ecb49, 2}
Probably caused by : ntoskrnl.exe ( nt+5a450 )
BUGCHECK_STR:  0x50
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sat Oct 31 12:17:11.271 2009 (UTC - 4:00)
System Uptime: 0 days 0:26:12.945
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1E, {ffffffffc0000005, fffffa600c6ab800, 0, 0}
Probably caused by : ntoskrnl.exe ( nt+5a450 )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]

 

[umax]

Thanks a bunch man, really appreciated the help.

I think I found the main cause (bad memory stick). I used windows memory diagnostics before, but I should have known that would have been a POS.

As for those missing symbols, could I just throw in my vista disc and try to repair? I am using a genuine product.

 

[usasma]

You don't need the symbols unless you're analyzing the memory dumps - and since you've found the problem you shouldn't need to read the memory dumps.