
Quote: Originally Posted by
tashie
Hi guys. I did as
this post asks and here goes my files. I also attached the error description that shows up when the system, recovers. Hope it helps.
My extra info:
My Win 7 is x64
It is the original installed OS on the system
It is an OEM
- What is the age of system (hardware)? - Less than a year. Computer bought on june/2010.
- What is the age of OS installation (have you re-installed the OS?) No, I haven't.
Thanks for all
These both contain little useful info but I do notice you are running sptd.sys. That is a huge cause of BSODs. They both were caused by memory corruption probably from a driver possibly sptd.sys
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.
They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.
Use this SPTD uninstaller
DuplexSecure - Downloads
when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.
I would also run a system file check to verify and repair your system files.
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
Read here for more information
SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
Old drivers needing update
Code:
pcouffin.sys 12/5/2006 10:39:30 AM fffff880`04110000 fffff880`04124380 0x00014380 0x457584a2
lmimirr.sys 4/10/2007 06:32:45 PM fffff880`0f211000 fffff880`0f218000 0x00007000 0x461c108d
snp325.sys 7/23/2007 10:22:27 PM fffff880`0589a000 fffff880`062d2f80 0x00a38f80 0x46a56263
LMIRfsDriver.sys 7/14/2008 12:26:56 PM fffff880`05881000 fffff880`05894000 0x00013000 0x487b7e50
RTL8187B.sys 3/24/2009 03:04:13 AM fffff880`03670000 fffff880`036df000 0x0006f000 0x49c885ed
spldr.sys 5/11/2009 12:56:27 PM fffff880`01b83000 fffff880`01b8b000 0x00008000 0x4a0858bb
RTKVHD64.sys 6/16/2009 06:12:51 AM fffff880`04e21000 fffff880`04fd1e80 0x001b0e80 0x4a377023
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page:
http://www.carrona.org/drvrdown.html Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\040911-19500-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03a03000 PsLoadedModuleList = 0xfffff800`03c48e90
Debug session time: Sat Apr 9 20:38:03.693 2011 (GMT-4)
System Uptime: 0 days 22:54:46.238
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80003b2b28f, fffff88008a42c50, 0}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
Followup: MachineOwner
---------