have not got a clue

[pcboo]

constant bsods and no clue as to what to do.
here is the Who Crashed report,
[FONT=Segoe UI, Arial]System Information (local)[/FONT]
[FONT=Segoe UI, Arial]computer name: PCBOOS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 4293386240 total
VM: 2147352576, free: 1918844928


[/FONT]
[FONT=Segoe UI, Arial]Crash Dump Analysis[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Wed 09/01/2013 17:38:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC4 (0x62, 0xFFFFFA80062C9368, 0xFFFFFA800896DB80, 0x1)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 09/01/2013 03:12:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010913-37487-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7EFC0)
Bugcheck code: 0xC4 (0x62, 0xFFFFFA8008844718, 0xFFFFFA8008844550, 0x1)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 08/01/2013 02:21:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010813-36348-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7EFC0)
Bugcheck code: 0xC4 (0x62, 0xFFFFFA80080A7848, 0xFFFFFA800809F5C0, 0x1)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]Conclusion[/FONT]
[FONT=Segoe UI, Arial]3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

[/FONT]

 

[koolkat77]

Please post the following report before we proceed:

• Windows Genuine and Activation Issue Posting Instructions

 

[pcboo]

its okay. i found the problem my external 2tb drive had errors. its scanned and fixed now