windows 7 clean install freezes on starting screen Results


Page 2 of 2.
Results 21...33 of 33

Sponsored Links:



Hey guys I'm a first time poster to these forums. I'm currently experiencing an issue with my computer. About 2 months ago I started getting random freezes and would have to do a hard restart on my computer to restart. To see if it was a virus or any kind of malware, I did a clean reformat of my hard drive and was still having issues. Eventually it started taking forever to boot up and load files and I got a SMART status bad message. So I wound up replacing my hard drive with a brand new one and did a clean install of Windows 7. That seemed to fix the slow boot and file load times but now I'm still getting freezes. However they are not random. They seem to happen when I don't touch the computer for awhile, whether I have a program such as something downloading in the background or not. They also seem to happen when I close the computer and put it to sleep and leave it like that for awhile. I try to wake it up and I only get a black screen, however my computer is on as I can hear the components.

The strange thing is as long as I am actively using the computer it doesn't seem to do this. I was on it for about 6 hours yesterday night and nothing happened and the computer was working fine. I did various hard disk scans even though I know it can't be the hard drive seeing as I just replaced it. it also isn't my graphics card as i uninstalled the driver and let my computer run for awhile with the standard VGA adapter and it still froze after me not touching it for awhile. I also did a windows memory diagnostic scan and nothing came up. I'm thinking there are 2 seperate problems with my computer, one that I fixed by replacing the hard drive (the slow boot time and file loading times, it took me 20 minutes to open up windows explorer, it doesn't anymore.) and another that I am unsure of. Should I do more memtest passes? i heard that one is not enough and that you should do up to 7 to make sure your RAM isn't faulty. Any feedback on this would be awesome. The computer is only a year and a half old and I'd like to make it last another year and a half at least.

Here are my computer specs:

Model: Samsung R780

OS: Windows 7 Home Premium (64-bit)

Processor: Intel Core i5 2.27 GHZ

RAM: 4GB DDR3

Graphics Card: Nvidia GeForce GT 330M (1GB Video Memory)

Hard Drive: 500 GB Hybrid SATA/Solid State (4GB of solid state memory), this is the new hard drive that I purchased.

If there's anything else you want to know about my computer, feel free to ask. Again, I'd greatly appreciate any feedback!

EDIT: So I tried downloading updates for a game and it immediately froze. So maybe the freezing is still happening on a random basis... I still don't understand what could be wrong...




Problem Description

After booting, the computer freezes at the welcome screen after logging in as any of the users. Sometimes it will restart automatically, other times it has to be "hard shut down". It freezes at the same time, consistently.

Occasionally, through an unknown set of steps, I can get the computer to boot properly. It crashes after a short while of using it, and then once again crashes at the welcome screen. Every time it has crashed so far it was while playing a game (not necessarily graphics-intensive). Again, after this crash the computer returns to just crashing at the Welcome Screen.

Booting to safe mode works every time.

Attempted Solutions

Malware Scan with Malware Bytes (clean)
Memory test with Windows Memory Diagnostic (clean)
Ran Driver Detective (said I needed an update on my Video, Audio and Network Drivers)

Various System Restore and Last Known Good Configuration (occasionally works for a short while, but then computer freezes during use and problems return)
Clean Boot (does not work, still hangs at login)
Disabled network card, sound card, and display adapter through device manager (does not work, still hangs at login)
Reinstalled latest version of Video and Audio Drivers (no change in behavior)
Reinstalled Windows 7 completely (computer seemed to work fine for a while, then had same problem)

About my Computer

My computer is a newly purchased computer from ibuypower.com (about 1 month old).

Motherboard: Gigabyte GA-770T
Processor: AMD Phenom II X4 925 2.81 GHZ
8 GB RAM
NVidia GeForce GTS 450
700 Watt Power Supply
2 Hard Drives
Flash 64 GB Drive (has OS)
1TB Western Digital Drive (data)

Windows 7 64-bit

About 2 weeks ago, I had another problem where the computer would randomly freeze during use, after login. To fix it, I installed new Display Drivers for my video card. The problem disappeared and the PC has been running fine until now.

Personal Thoughts

I'm at a bit of a loss now about what to do. The next step for me is to try taking out all but one stick of ram and seeing if there is still a problem. If it were a RAM problem, it just seems so unlikely that the problem would be as consistent as it is. I would also think I would occasionally get problems in Safe Mode.

I also may reinstall Windows 7 again and be more careful about which updates/drivers I install. After the reinstall I started doing Windows Updates, which might have caused me problems. I may also install Windows on my Data Drive and see if that makes a difference.

Any thoughts or suggestions are helpful. Thanks for your time!

Other info

CPU-Z Screenshots

Attached - SF Diagnostic Tool Log Files Seven Forums.zip




Hi everyone,

I just did a clean restore on my PC because I thought the issue was a virus or something. After a clean install of Windows 7, I'm still getting the following errors (which I had before my restore as well):
- computer wouldn't start up, stuck at motherboard logo screen or "starting windows" screen.
- bios would be on and off on detecting my hard drive, (and therefore would not start up windows)
- if I actually do make it to the desktop, I would have random reboots in a wide range of time (1hr - 5hrs). It would also freeze by even the slightest work (opening firefox, word, itunes)

I'm assuming it's a hardware issue, but I don't know what it is. The CPU runs low and doesn't go over 45C. The computer is only a little less than 2 years old.

Here are the computer specs.
Intel core 2 Quad Q6600 2.4ghz
Foxconn P45A-S Mobo
Antec 650W PSU
G.Skill 4gb ddr 800 RAM
Sapphire Radeon HD 3870 512mb
WD 500gb sata hard drive
Windows 7

Any help please?




I recently built a new computer with a 1GB NVIDIA GeForce 9500GT graphics card and installed Windows 7 Ultimate 64-bit on it. I formatted the hard drive and did a clean install of everything. I am not overclocking any of the components, and I have checked the GPU temps and ran stress tests, and the GPU doesn't get very hot, maybe around 50C.

Every time I try to game on it, even with a game as simple as Portal, the game will freeze up and the graphics driver will crash. The screen will flash black for a second, and the monitor will stop recieving a signal from the graphics card temporarily. After 2 or 3 seconds, the system starts working properly again. This is the error it's giving me: "Display driver NVIDIA Windows Kernel Mode Driver, Version xxx.xx stopped responding and has successfully recovered."

I have tried this using the default drivers that came with the card, the most up to date drivers on NVIDIA's website, and an older version of the drivers from NVIDIA's website. No matter what driver version I have installed, this still happens. It has even happened before when I wasn't even running a game, just using Firefox.

I have checked Windows Update for any updates, uninstalled the drivers and used Driver Sweeper to fully remove them before installing a new version, and no matter what I cannot seem to fix the error. Any suggestions?

The rest of my specs:
Diablotek 450-watt PSU
ASROCK P43DE Motherboard
2 GB DDR2 667 MHz
2.8 GHz Pentium 4 with Hyper Threading

(yes, I know the CPU and RAM aren't great, I'm upgrading both as soon as I can, but it still should be enough to run a game like Portal, and I don't think it is related to the cause of this error)




Hi, I'm far from new to computers and I don't want to upset too many people
but I have a major disappointment (and that's trying to be humble) with SP2.

This is what I've found out so far concerning the issues with:
- boot failures
- lock-ups of system after re-boot
- AGPCPQ.SYS or AGP440.SYS freeze in safe-mode after install.
- UPDATE.SYS
- KB885626 FIX failure

1) First, I did what most users did. Update through Windows Update. Managed
to download SP2 after an eternity (2 days) Broadband connection 10Mbit on my
side...But I wasn't in a hurry.

2) Install, everything seems ok. Reboot. "Blue screen of death" for half a
millisecond and then autorestart. No safe-start, or any option makes system
available!!! I'm basically locked out! Reinstall (Many thanks to Imaging
Software!)

3) Update all drivers, update Bios. Download SP2 full file for IT
professionals and wait the 60 minuts it takes to reinstall SP2 (hugh)

4) Re-boot. Computer dead again! In safe mode however, I get a stop at file
AGPCPQ.SYS (just after AGP440.SYS) which to some might cause a "bling" since
it coincides with a previous problem in Windows2000. However, I enter NTFSDos
and remove the files for fun, this time process freezes at another file than
the ones listed above. So thus, it is not an AGP drive issue like Microsoft
Support throws in your face. I have updated the AGP to the very latest (and
they are new). SIS645dx version 1.17e and also graphic card.

5) Check support and get info on kb885626 Prescot computers. Verify with
Intel Frequency ID Utility what processor I have. It reads Family: F, not a
Prescot, but a Northwood - thus it is in the range of processors affected of
the known issue with microcoding. Info is given to update BIOS or run the
FIX. I do the latter since there is no newer fix than I already have.

6) Restart after install of the fix (SP2 yet not installed!) and after 30-60
seconds system freezes completely. Please note SP2 not installed and this is
the fix that causes the problem with freeze! The same fix that is supposed to
fix the install of SP2. Well, thank you! I'm not very positive about the
outcome...

7) Restart in safe mode and it works ok though. I then decide to, what the
heck...

8) Install SP2 - Reboot. Works ok, for about 30-60 seconds, then it's dead
again, just like with the fix. But Halleluja. The SP2 installed this time and
reboot works!! Safe-mode is ok and does not freeze up like normal mode. Good,
now I can play.

9) I get pe:d off and check the system files and do some real-playing around
since MICROSOFT Support for SP2 does not offer any helpful advice and knows
less than what I've figured out so far (have you updated your drives,
unplugged usb's, bios updated, checked that the power-chord is plugged in
(!??!) - Well, yes I have. And raindance and running around computer
clock-wise three times. Erhh... let me get back on the issue they say.
Haven't heard from them)

10) I decide to do exactly what the KB885626 says I shouldn't do. I make a
copy of the UPDATE.SYS from my original XP SP1a installation and save it.
Then I do another (about the 10th installation of SP2) after the KB885626 fix
that causes my computer to freeze after install. Then I rename the SP2 203 kb
UPDATE.SYS and replace it with UPDATE.SYS (SP1a file - about 130kB). Double
Halleluja. It works. NO freezes, NO lock-ups, NO problems... so far.

Now to questions for you who made it through this post so far:
- KB885626 does not work as it should! Faulty Fix for my type of processor?
Not Prescot, but Northwood?
- SP2 writes some bad code into UPDATE.SYS that causes processor to fail -
is this needed in the file?
- UPDATE.SYS - what does it do? Why does this file lock up my system, and
without it, it works ok? Is it really that needed???
- How come Microsoft says to us victims out the Update your BIOS:es. It's
not really our fault. If 20 motherboard manufacturors suddenly have to sit
down and write BIOS codes for computers they don't even sell anymore, what
kind of attack on this issue is that when it is an SP2 issue!!
- And no, I don't sit on a crap computer. It is a laptop, top of the art 10
months ago, and I can still play Far Cry on it. With laptops you have other
issues as well - trying to find drives. I can't just unplug a device that
easy or update a funky processor to check with another.

So please all SP2 worshipers out there. There are issues with SP2. Full
stop. It has not been Beta tested properly and several IT consultants are
warning for issues of more than 10% of computer installations going funky.

And please, Mr Microsoft. It's time to fix the issue properly (FIX for the
885626fix or whatever). In this case the unsupported processors...

My Info:
- OS: Tried on XP Home, XP Pro, XP PRO Slipstreamed SP2. (slipstreamed
freezes at installing devices (33 minutes reamining!) KB885626 not slipped or
run into the installation disk, so it explains...
- All tests on clean install (no antivirus, no other software, even without
firewalls- Nada!)
- Test has been made with standard drivers, complete update of drivers and
even BIOS update (newest available on the market at this moment about 5
months old!)
- It has been tested with Windows Update and downloaded as an independent
SP2 file.

Computer:
- Gericom Laptop 3.06 GHz, 512MB
- ATI 9000 Mobility Radeon
- WLAN SIS
- HD Toshiba MK4025GAS
- Mat****a UJ-815A
- Smart Link modem

Processor:
Intel(R) Processor Frequency ID Utility
Version: 7.1.20040716
Time Stamp: 2004/10/18 18:18:14
Number of processors in system: 1
Current processor: #1
Processor Name: Intel(R) Pentium(R) 4 CPU 3.06GHz
Type: 0 ---------------------------- Funky Type?
Family: F ---------------------------- Funky Family!
Model: 2
Stepping: 7 ---------------------------- Funky Stepping?
Revision: 27
L1 Trace Cache: 12 K┬╡ops
L1 Data Cache: 8 KB
L2 Cache: 512 KB
Packaging: FC-PGA2
MMX(TM): Yes
SIMD: Yes
SIMD2: Yes
SIMD3: No
NetBurst(TM) Microarchitectu Yes
Expected Processor Frequency: 3.06 GHz
Reported Processor Frequency: 3.06 GHz
Expected System Bus Frequency: 533 MHz
Reported System Bus Frequency: 533 MHz
************************************************** *****

Many thanks.




My main work machine has started to freeze (and when it feels for it: reboot).

@#!% Give me a "clicking" hard drive and I know what is wrong and what to do.
Give me some leaking capacitors and I at least see the problem and know what to do.
Give me a virus and I handle it.
But this ...

Third attempt to post.
2.5 years ago, I had problem with some memory, so I thought, and bought some new. After testing back and forth there was no evidence of problem later, so I did let it run with both 256 + 256 MB.

7 months ago, in October, I had escalating problems with freezing; no BSOD, no reboot, just stop or monitor went blank. IIRC it happened anytime; in Windows, at BIOS post screen, in CMOS setup, in Recovery Console (from CD). I went trough every connection inside the machine and took out the oldest memory. I think I also moved the "new" memory from first to second slot. At that second, minute, the freezing stopped. It worked happy until about three-four weeks ago. Only thing during the 7 months was some odd flash (off/on) of the monitor when I scrolled the wheel mouse in Firefox.

In mid April (had not installed anything for some time, and I always wait a little with MS patch), I installed a new zip-program to try. Three hours later freeze/reboot started and then some later that evening. As I did not like this! And not the zip-program as well, I did uninstall the program. The severity of the problem made me use System Restore, but the restore to a recent RP did not take care of file associations, so I went back again to first situation, with the program uninstalled and went forward with rebuilding file associations.

Now, I do not blame this particular zip-program. But you all know how the questions go: have you installed something lately? In my case after 7 months working, it took 3 hours after install to break loose.

Since then I have updated graphic drivers, should have done maybe earlier (from Nov 2004). Some week ago, I did some cleaning inside the machine; removed the graphic card, NIC and memory and reseated everything. Seemed to work for some day or two. Did do testing with MS Win Memtest for some hour, seemed OK, no errors. Then another time it froze, no error in test, just froze.

Some days ago it rebooted and saluted me with a "CMOS checksum error - Defaults loaded". I went into CMOS Setup and changed frequncy, since default is 100 (and I need 133x11.5). This has happened once before on this machine post 315,869 Restarted and did a chkdsk on C: went OK. Run for 2.5 hour, shut down. Frooze on new boot.

As I said, I do not know where to look; new memory always this tip, but I have not found any errors so far on the memory modules. Graphic card, I have heard that they can produce similar errors as memory modules. CPU and motherboard? If I change MB with MS new rules I cannot run my OEM OS, great another $120-130 for OS. I have other projects this spring/summer and cannot spend so much on the PC.

Last year I changed, on this machine, CPU cooler and PSU.
Spec.
OS: WinXP SP2
CPU: AMD 1800+
Mem: 256 MB
PSU: ~400 W

Any thoughts appreciated.




Hello,

I've installed Windows 7 build 7600 (32 bit) and within a couple seconds to a half hour the computer will freeze up and require a hard reset. It doesn't matter what I'm doing. I could just leave it alone and it eventually locks up. Running programs doesn't seem to make it freeze any faster.

Checking the logs reveals no pattern and there is no bluescreen or .dmp in the minidump folder.

I have a 2.2ghZ AMD Athlon processor, an ATI Radeon 9550 video card, 2Gb of RAM (two 1gb sticks) and a motherboard with onboard sound and NIC (Via chipset).

Here's what I've tried so far:
-Ran the memory test and chkdsk. No problems found in either one.
-Tried each stick of RAM individually and swapped slots.
-Used the verifier tool to check the drivers and received no blue screen.
-Made sure each driver is up to date.
-Kept tabs on CPU and RAM usage, neither of which ever come close to maxing out.
-Wiped the drive, did a clean install.
-Started in diagnostic mode via msconfig
-Booted into safe mode

Everything eventually results in a lock up.

Any ideas?

Edit: Just noticed my typo in the title. Could a mod please fix that?




I am Having problems after doing a full clean install of windows 7 64 bit on my pc about two weeks ago I was pleased to see that everything seemed to be working well but over time the nagging faults have started to creep in it has started to restart itself just after the log in screen and also to randomly freeze and last night my 32 bit browser programs stopped working Internet explorer 32bit firefox and msn messenger all say that a internet connection is not availiable however the 64 bit version of internet explorer is working fine and is able to connect to the internet without any problems
please help
all these programs were working perfectly for about two weeks untill yesterday and I have done nothing to change any thing when I turned it off everything was working fine when I turned it back on the next morning different story.

System Info;
Mainboard : Gigabyte GA-73PVM-S2
Ram: 4 GB
OS: Windows 7 64bit
Graphics: ATI Radeon HD 3850
Sound: Creative Sound Blaster X-Fi




Computer Freezes with Solid Red Screen. Error 124 is what windows tells me.

I had posted this on another forum, but nobody there has responded for several days now. So i'm gonna quote what i told them.

I have the same exact problem as the OP has told us about. out of no-where, the screen will turn solid red. It has happened about 5 times already, and started yesterday night shortly after installing my new GTX 680 and Asus Motherboard. Out of those 5 times, I only got a error dump once from windows.

Error code 124. BlueScreenView says it has something to do with NTOSKRNL.EXE. Upon further research, this error is related to Hardware Failure.

I'm a computer technician, do it for a living, so i've done extensive testing on all of my hardware. Memory test were fine after 3 passes. Hard Drive test is fine. Stress test CPU is fine,, Stress test GPU is fine. I can play any game, including Battlefield 3 maxed out, without any problems. The red screen only happens while i'm doing stuff on desktop. So far anyways.....

Just before this started happening i was getting the famous BSOD 116 while gaming (before i bought this new GTX 680 and Asus Rampage III Motherboard). This is usually a problem with thegraphics card or PSU. So i bought a new Motherboard, and Graphics Card. Got the new motherboard since it was on sale and i wanted something that supported USB 3.0 and Sata 6. I had doubts about it being the power supply, since corsair usually makes good ****, and the PSU was only 7 months old. So I just ran with the new mobo and Graphics card to see if my problems would end.

Current Hardware Specs:

Intel i7 920 D0 Stepping (no overclocks on anything while trying to debugg this problem)Asus Rampage III Formula 1366 Motherboard (newest bios)Asus GTX 680 DC2O Graphics Card (newest driver)Corsair 6GB DDR3 Ram Tri-Channel CX1600C8XXXXCorsair TX 850 V2 Power SupplyDual Seagate 1TB Drives in RAID 0Maxtor 500GB Hard drive dock connected with e-sata on front portsDual Screen Monitors. 1 is DVI, the other is VGA connected to GTX 680 via a VGA to DVI AdapterSwiftech Water Cooling Kit. CPU only.

Swapped out the Graphics Card and motherboard yesterday (05/31). Everything ran fine for a few hours. Then out of no-where, my screen turns red while i was checking my email on the desktop. I proceeded to game all night playing DoTA 2 and BF3. No more problems all night.

Today i get up, check email, browse reddit, BAM, Red Screen on both monitors. (it will stay red until i cut the power) the computer does not restart on its own.

After testing everything, i have come to the conclusion that the Power Supply is at fault. I think on the GTX 680 Chipset, the Red screen happens when there is not enough power or there is a TDR Stop error. The GTX 480's and 580's would just throw out a 116 Error Stop when this would happen.

I suggest trying a different power supply before you RMA any hardware. I am ordering a replacement power supply, probably a Corsair TX 850w from amazon with overnight shipping saturday priority. I will post back if this fixed the issue. It may be a few days, because i cannot replicate the problem. It just happens randomly.

Here is the Mini-Dump (Edit: OLD Windows install, Disregard): http://dl.dropbox.com/u/3783766/dump%20rsod.zip

Here is a pic of the Red Screen:

Since this post, have replaced the Power Supply. I ordered a Corsair TX 850w V2.

So a quick recap of what i've replaced since i started having problems:

Graphics Card: Had GTX 580, Replaced with Asus GTX 680 DC2O (Brand New, from newegg.com)Motherboard: Had Asus Rampage II Extreme; Replaced with Asus Rampage III Formula (Refurbished from newegg.com)Power Supply: Had Corsair TX750 V2 7 months old; Replaced with Corsair TX 850 V2 (Brand New from Amazon.com)

Did a clean format 2 days ago since i was afriad that some of the old motherboard drivers were causing this problem. The computer ran fine for 2 days, then i just now got my 1st red screen since format.

I got another Error Dump from windows, Error 124 again.

Here is the 2nd Dump from today (on new windows install): http://dl.dropbox.com/u/3783766/060312-22900-01.dmp

I'm at a loss. I've tested 5 passes on memory and used SeaTools on the Hard Drives. Both found 0 Errors.

Using latest drivers on everything.

For reference, here is my forum post on another forum.

Please help. Many thanks

EDIT: it looks like lots of ppl with 680's are having this issue. Some say it has something to do with the way certain programs access the Graphics Card Bios to Poll for information such as Temps, Voltages, Fan speed, etc... For some reason, the GTX 680's do things differently than other cards.

Found this thread on EVGA's Forum




Hello! Yesterday Bought new HDD(WD Caviar Black 750gb) So i reinstalled my system

Reinstalled W7U SP1 did 'clean install' with my old drive format and the new drive format and installed OS on the new drive! And yesterday was up until midnight until I installed all the needed drivers..
Today I wanted to install GTA SanAndreas for the but As I press next and he starts to install everything freezes and after 3,4 seconds BSOD -

***STOP: 0x00000101 (0x0000000000000031,
0x0000000000000000, 0xFFFFFA60021D21B0,
0x0000000000000003)

Ok I reseted CMOS I had 20% overclock

But still the same but now I got strange XP BSOD -

***STOP: 0x0000000D1

I could just reinstall windows but I want to know what caused this Error

P.S. Bios is nevest for my motherboard, Video driver nevest and have installed nevest Nforce drivers
b4 I reinstalled I used the same Windows 7 version just it was on the now old WD drive and everything was fine

Included CPU-Z screens and Minidump zip file
______________
OS - Windows 7 Ultimate SP1 64Bit
Motherboard - ASUS Striker II Extreme
Processor - Intel Core 2 Quad Q9400 ( 2.66GHz, 1333MHz, 45nm, 6MB L2 Cache Total)
RAM - OCZ RPX HPC DDR3 1333MHz 4096MB Kit(2x2gb)
VIDEO - EVGA GeForce GTX 280 1GB GDDR3 Attached Thumbnails а а а Attached Files Minidump.zip (72.0 KB, 118 views) Share Share this post on Digg Del.icio.us Technorati Twitter
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left; а JavaScript must be enabled 03-17-2011 #2 cybercore Premier Member Enjoys Windows 7 Forums а
Join Date Jul 2009 Posts 7,900 Re: BSOD STOP: 0x00000101 Ok I reseted CMOS I had 20% overclock

But still the same but now I got strange XP BSOD -

***STOP: 0x0000000D1

I could just reinstall windows but I want to know what caused this Error
-----> Overclocking causes your blue screens.

CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

1. Reset the clocks and voltages to the optimized defaults as recommended for your hardware.

2. Uninstall Daemon Tools DuplexSecure - FAQ

3. Update nForce:

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

4. Update ASUS ATK0110 ACPI Utility

ASACPI.sys Sun Mar 27 22:30:36 2005
Again, Reset the clocks and voltages to the optimized defaults as recommended for your hardware. Overclocking crashes you.

Crash Dumps:

Code: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:aMinidumpD M PDMP31711-31668-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c5de90 Debug session time: Thu Mar 17 12:42:28.271 2011 (UTC - 4:00) System Uptime: 0 days 0:38:37.582 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {31, 0, fffff880009e8180, 1} Unable to load image SystemRootSystem32Driverssptd.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for sptd.sys *** ERROR: Module load completed but symbols could not be loaded for sptd.sys Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009e8180, The PRCB address of the hung processor. Arg4: 0000000000000001, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: d STACK_TEXT: fffff800`0420be68 fffff800`02aefa89 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009e8180 : nt!KeBugCheckEx fffff800`0420be70 fffff800`02aa2eb7 : 00000000`00000000 fffff800`00000001 00000000`00002710 fffff880`010499d2 : nt! ?? ::FNODOBFM::`string'+0x4e2e fffff800`0420bf00 fffff800`0300c895 : fffff800`030323c0 fffff800`0420c0b0 fffff800`030323c0 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff800`0420c000 fffff800`02a94b73 : fffffa80`05e79000 fffff880`0102da0d fffff880`0462b094 fffffa80`05e79000 : hal!HalpHpetClockInterrupt+0x8d fffff800`0420c030 fffff800`02b3dcb8 : fffffa80`07fc5110 00000000`00000000 fffffa80`07fc5110 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff800`0420c1c0 fffff880`0104a6c4 : fffff880`0104a514 fffff800`0420c268 fffff880`00000002 00000000`00000002 : nt!KeIpiGenericCall+0x138 fffff800`0420c230 fffff880`0104a514 : fffff800`0420c268 fffff880`00000002 00000000`00000002 00000000`00000000 : sptd+0x496c4 fffff800`0420c238 fffff800`0420c268 : fffff880`00000002 00000000`00000002 00000000`00000000 fffff880`0104fed0 : sptd+0x49514 fffff800`0420c240 fffff880`00000002 : 00000000`00000002 00000000`00000000 fffff880`0104fed0 00000000`00000002 : 0xfffff800`0420c268 fffff800`0420c248 00000000`00000002 : 00000000`00000000 fffff880`0104fed0 00000000`00000002 fffff880`01049cd8 : 0xfffff880`00000002 fffff800`0420c250 00000000`00000000 : fffff880`0104fed0 00000000`00000002 fffff880`01049cd8 fffff800`0420c2e0 : 0x2 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:aMinidumpD M PDMP31711-36660-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`02a4b000 PsLoadedModuleList = 0xfffff800`02c90e90 Debug session time: Thu Mar 17 13:33:15.362 2011 (UTC - 4:00) System Uptime: 0 days 0:30:59.064 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {31, 0, fffff88003163180, 2} Unable to load image SystemRootSystem32Driverssptd.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for sptd.sys *** ERROR: Module load completed but symbols could not be loaded for sptd.sys Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff88003163180, The PRCB address of the hung processor. Arg4: 0000000000000002, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: set8EE6.tmp CURRENT_IRQL: d STACK_TEXT: fffff800`04220a98 fffff800`02b22a89 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03163180 : nt!KeBugCheckEx fffff800`04220aa0 fffff800`02ad5eb7 : 00000000`00000000 fffff800`00000002 00000000`00002710 fffffa80`07725930 : nt! ?? ::FNODOBFM::`string'+0x4e2e fffff800`04220b30 fffff800`02a0c895 : fffff800`02a323c0 fffff800`04220ce0 fffff800`02a323c0 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff800`04220c30 fffff800`02ac7b73 : 00000566`f8d74a70 fffff800`04220ce0 00000000`00000031 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d fffff800`04220c60 fffff800`02a122c3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff800`04220df0 fffff800`02a11a7b : 00000000`00000001 00000000`00000032 00000000`00000000 63006f00`52000000 : hal!HalpTscStallExecutionProcessor+0xbf fffff800`04220e50 fffff880`010dfaf9 : 00000000`00000001 fffffa80`04a67640 fffffa80`04a676a8 fffff880`0f2065d3 : hal!KeStallExecutionProcessor+0x183 fffff800`04220e80 00000000`00000001 : fffffa80`04a67640 fffffa80`04a676a8 fffff880`0f2065d3 fffffa80`08302000 : sptd+0x48af9 fffff800`04220e88 fffffa80`04a67640 : fffffa80`04a676a8 fffff880`0f2065d3 fffffa80`08302000 fffff880`010d9150 : 0x1 fffff800`04220e90 fffffa80`04a676a8 : fffff880`0f2065d3 fffffa80`08302000 fffff880`010d9150 00000000`00000000 : 0xfffffa80`04a67640 fffff800`04220e98 fffff880`0f2065d3 : fffffa80`08302000 fffff880`010d9150 00000000`00000000 fffffa80`08303210 : 0xfffffa80`04a676a8 fffff800`04220ea0 fffff800`02ad6b1c : fffff800`02c3de80 fffffa80`00000000 fffffa80`08302000 00000000`000000f8 : portcls!CServiceGroup::ServiceDpc+0xa7 fffff800`04220f00 fffff800`02ace165 : 00000000`00000000 fffffa80`04d81b60 00000000`00000000 fffff880`010d9110 : nt!KiRetireDpcList+0x1bc fffff800`04220fb0 fffff800`02acdf7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 fffff880`09fc6bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:aMinidumpD M PDMP31711-39561-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c46e90 Debug session time: Thu Mar 17 13:43:45.555 2011 (UTC - 4:00) System Uptime: 0 days 0:02:08.334 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 2, 8, 0} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000000000000000, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb20e8 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: +3364613036316532 00000000`00000000 ?? ??? PROCESS_NAME: System CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: fffff8800318baf0 -- (.trap 0xfffff8800318baf0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8800316dfc0 rbx=0000000000000000 rcx=fffff80000b9c2b8 rdx=fffff880010e7ed8 rsi=0000000000000000 rdi=0000000000000000 rip=0000000000000000 rsp=fffff8800318bc88 rbp=fffff880010e7ed8 r8=0000000000000000 r9=fffff880010da501 r10=0000000000019905 r11=fffff88000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc 00000000`00000000 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a80be9 to fffff80002a81640 FAILED_INSTRUCTION_ADDRESS: +3364613036316532 00000000`00000000 ?? ??? STACK_TEXT: fffff880`0318b9a8 fffff800`02a80be9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx fffff880`0318b9b0 fffff800`02a7f860 : 00000000`0001fca2 fffffa80`03c9f900 fffffa80`05931888 fffff880`03163180 : nt!KiBugCheckDispatch+0x69 fffff880`0318baf0 00000000`00000000 : fffff800`02a8cb1c 00000000`13fa6554 00000000`13fa862b 00000000`13fa6554 : nt!KiPageFault+0x260 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`02a7f860 440f20c0 mov rax,cr8 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiPageFault+260 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260 BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260 Followup: MachineOwner ---------

Drivers:

Code: start end module name fffff880`04c82000 fffff880`04cc0000 1394ohci 1394ohci.sys Sat Nov 20 05:44:56 2010 (4CE7A6A8) fffff880`01038000 fffff880`0108f000 ACPI ACPI.sys Sat Nov 20 04:19:16 2010 (4CE79294) fffff880`0449f000 fffff880`04528000 afd afd.sys Sat Nov 20 04:23:27 2010 (4CE7938F) fffff880`04cd8000 fffff880`04cee000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`04ba9000 fffff880`04bf1000 alavozp9 alavozp9.SYS Sun Nov 28 05:38:44 2010 (4CF23134) fffff880`012bd000 fffff880`012c8000 amdxata amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA) fffff880`04cc0000 fffff880`04cc8000 ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C) fffff880`00fe1000 fffff880`00fea000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e00000 fffff880`00e2a000 ataport ataport.SYS Sat Nov 20 04:19:15 2010 (4CE79293) fffff960`00830000 fffff960`00891000 ATMFD ATMFD.DLL unavailable (00000000) fffff880`01beb000 fffff880`01bf2000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`04b06000 fffff880`04b17000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`07d21000 fffff880`07d3f000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`006b0000 fffff960`006d7000 cdd cdd.dll unavailable (00000000) fffff880`0179b000 fffff880`017c5000 cdrom cdrom.sys Sat Nov 20 04:19:20 2010 (4CE79298) fffff880`00cfb000 fffff880`00dbb000 CI CI.dll Sat Nov 20 08:12:36 2010 (4CE7C944) fffff880`01b9a000 fffff880`01bca000 CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B) fffff880`00c9d000 fffff880`00cfb000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01386000 fffff880`013f8000 cng cng.sys Sat Nov 20 05:08:45 2010 (4CE79E2D) fffff880`04cc8000 fffff880`04cd8000 CompositeBus CompositeBus.sys Sat Nov 20 05:33:17 2010 (4CE7A3ED) fffff880`061ab000 fffff880`061b9000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`04a65000 fffff880`04ae8000 csc csc.sys Sat Nov 20 04:27:12 2010 (4CE79470) fffff880`05d67000 fffff880`05d9c000 CT20XUT CT20XUT.SYS Wed May 05 09:01:28 2010 (4BE16C28) fffff880`05c9e000 fffff880`05d4c000 ctac32k ctac32k.sys Wed Jul 02 04:38:22 2008 (486B3E7E) fffff880`04cf3000 fffff880`04d98700 ctaud2k ctaud2k.sys Wed May 05 08:59:48 2010 (4BE16BC4) fffff880`0602d000 fffff880`0618a000 CTEXFIFX CTEXFIFX.SYS Wed May 05 09:01:21 2010 (4BE16C21) fffff880`05d4c000 fffff880`05d67000 CTHWIUT CTHWIUT.SYS Wed May 05 09:01:32 2010 (4BE16C2C) fffff880`04c43000 fffff880`04c74000 ctoss2k ctoss2k.sys Wed May 05 08:57:46 2010 (4BE16B4A) fffff880`04c74000 fffff880`04c7c000 ctprxy2k ctprxy2k.sys Wed May 05 08:59:51 2010 (4BE16BC7) fffff880`05bc4000 fffff880`05bfc000 ctsfm2k ctsfm2k.sys Wed May 05 08:57:33 2010 (4BE16B3D) fffff880`04ae8000 fffff880`04b06000 dfsc dfsc.sys Sat Nov 20 04:26:31 2010 (4CE79447) fffff880`04468000 fffff880`04477000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01b84000 fffff880`01b9a000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`04dd6000 fffff880`04df8000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`061b9000 fffff880`061c3000 dump_diskdump dump_diskdump.sys Sat Nov 20 05:33:56 2010 (4CE7A414) fffff880`06000000 fffff880`06013000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`061c3000 fffff880`061ee000 dump_nvstor dump_nvstor.sys Fri Mar 19 16:45:11 2010 (4BA3E257) fffff880`0619f000 fffff880`061ab000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`0fe64000 fffff880`0ff58000 dxgkrnl dxgkrnl.sys Sat Nov 20 04:50:50 2010 (4CE799FA) fffff880`0ff58000 fffff880`0ff9e000 dxgmms1 dxgmms1.sys Sat Nov 20 04:49:53 2010 (4CE799C1) fffff880`0510e000 fffff880`05158000 emupia2k emupia2k.sys Wed May 05 08:57:27 2010 (4BE16B37) fffff880`0817d000 fffff880`081b3000 fastfat fastfat.SYS Mon Jul 13 19:23:28 2009 (4A5BC1F0) fffff880`0ff9e000 fffff880`0ffab000 fdc fdc.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6) fffff880`01314000 fffff880`01328000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`050a9000 fffff880`050b4000 flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6) fffff880`012c8000 fffff880`01314000 fltmgr fltmgr.sys Sat Nov 20 04:19:24 2010 (4CE7929C) fffff880`015d5000 fffff880`015df000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01b4a000 fffff880`01b84000 fvevol fvevol.sys Sat Nov 20 04:24:06 2010 (4CE793B6) fffff880`01a47000 fffff880`01a91000 fwpkclnt fwpkclnt.sys Sat Nov 20 04:21:37 2010 (4CE79321) fffff880`05a43000 fffff880`05bc4000 ha20x2k ha20x2k.sys Wed May 05 08:59:10 2010 (4BE16B9E) fffff800`02feb000 fffff800`03034000 hal hal.dll Sat Nov 20 08:00:25 2010 (4CE7C669) fffff880`080bc000 fffff880`080d5000 HIDCLASS HIDCLASS.SYS Sat Nov 20 05:43:49 2010 (4CE7A665) fffff880`080d5000 fffff880`080dd080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`080ae000 fffff880`080bc000 hidusb hidusb.sys Sat Nov 20 05:43:49 2010 (4CE7A665) fffff880`07c58000 fffff880`07d21000 HTTP HTTP.sys Sat Nov 20 04:24:30 2010 (4CE793CE) fffff880`01b41000 fffff880`01b4a000 hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E) fffff880`04b3d000 fffff880`04b53000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00fea000 fffff880`00ff9000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`080de000 fffff880`080ec000 kbdhid kbdhid.sys Sat Nov 20 05:33:25 2010 (4CE7A3F5) fffff800`00baa000 fffff800`00bb4000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`04c00000 fffff880`04c43000 ks ks.sys Sat Nov 20 05:33:23 2010 (4CE7A3F3) fffff880`015a9000 fffff880`015c4000 ksecdd ksecdd.sys Sat Nov 20 04:21:15 2010 (4CE7930B) fffff880`01770000 fffff880`0179b000 ksecpkg ksecpkg.sys Sat Nov 20 05:10:34 2010 (4CE79E9A) fffff880`04c7c000 fffff880`04c81200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`05c75000 fffff880`05c8a000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`05c52000 fffff880`05c75000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`080f9000 fffff880`08103000 LVPr2M64 LVPr2M64.sys Fri May 07 21:38:16 2010 (4BE4C088) fffff880`05c00000 fffff880`05c51d00 lvrs64 lvrs64.sys Tue Nov 09 21:36:46 2010 (4CDA053E) fffff880`07600000 fffff880`079f6a80 lvuvc64 lvuvc64.sys Tue Nov 09 21:37:14 2010 (4CDA055A) fffff880`00c3a000 fffff880`00c89000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 08:03:51 2010 (4CE7C737) fffff880`06013000 fffff880`06021000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`05086000 fffff880`05095000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`080ec000 fffff880`080f9000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00fc7000 fffff880`00fe1000 mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299) fffff880`017c5000 fffff880`017f6000 MpFilter MpFilter.sys Tue Sep 14 20:19:28 2010 (4C901110) fffff880`08103000 fffff880`08113000 MpNWMon MpNWMon.sys Tue Sep 14 20:19:30 2010 (4C901112) fffff880`07d3f000 fffff880`07d57000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`07d57000 fffff880`07d84000 mrxsmb mrxsmb.sys Sat Nov 20 04:27:41 2010 (4CE7948D) fffff880`07d84000 fffff880`07dd1000 mrxsmb10 mrxsmb10.sys Sat Nov 20 04:26:53 2010 (4CE7945D) fffff880`07dd1000 fffff880`07df5000 mrxsmb20 mrxsmb20.sys Sat Nov 20 04:26:47 2010 (4CE79457) fffff880`015e8000 fffff880`015f3000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`0108f000 fffff880`01099000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01328000 fffff880`01386000 msrpc msrpc.sys Sat Nov 20 04:21:56 2010 (4CE79334) fffff880`0445d000 fffff880`04468000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01b2f000 fffff880`01b41000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`0161d000 fffff880`01710000 ndis ndis.sys Sat Nov 20 04:23:30 2010 (4CE79392) fffff880`0ffeb000 fffff880`0fff7000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`00c00000 fffff880`00c2f000 ndiswan ndiswan.sys Sat Nov 20 05:52:32 2010 (4CE7A870) fffff880`0618a000 fffff880`0619f000 NDProxy NDProxy.SYS Sat Nov 20 05:52:20 2010 (4CE7A864) fffff880`0459c000 fffff880`045ab000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`04528000 fffff880`0456d000 netbt netbt.sys Sat Nov 20 04:23:18 2010 (4CE79386) fffff880`01710000 fffff880`01770000 NETIO NETIO.SYS Sat Nov 20 04:23:13 2010 (4CE79381) fffff880`08113000 fffff880`08128000 NisDrvWFP NisDrvWFP.sys Tue Sep 14 20:20:25 2010 (4C901149) fffff880`01225000 fffff880`01236000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`04451000 fffff880`0445d000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02a01000 fffff800`02feb000 nt ntkrnlmp.exe Sat Nov 20 04:30:02 2010 (4CE7951A) fffff880`01406000 fffff880`015a9000 Ntfs Ntfs.sys Sat Nov 20 04:20:57 2010 (4CE792F9) fffff880`01be2000 fffff880`01beb000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`0fe62000 fffff880`0fe63180 nvBridge nvBridge.kmd Fri Jan 07 20:57:22 2011 (4D27C482) fffff880`0f207000 fffff880`0fe61d00 nvlddmkm nvlddmkm.sys Fri Jan 07 21:07:22 2011 (4D27C6DA) fffff880`04a00000 fffff880`04a63d80 nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12) fffff880`00dbb000 fffff880`00de6000 nvstor nvstor.sys Fri Mar 19 16:45:11 2010 (4BA3E257) fffff880`04576000 fffff880`0459c000 pacer pacer.sys Sat Nov 20 05:52:18 2010 (4CE7A862) fffff880`00f2a000 fffff880`00f3f000 partmgr partmgr.sys Sat Nov 20 04:20:00 2010 (4CE792C0) fffff880`00ef7000 fffff880`00f2a000 pci pci.sys Sat Nov 20 04:19:11 2010 (4CE7928F) fffff880`00fb0000 fffff880`00fb7000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00fb7000 fffff880`00fc7000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`015c4000 fffff880`015d5000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`05158000 fffff880`051fe000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`04d99000 fffff880`04dd6000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c89000 fffff880`00c9d000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`0ffc7000 fffff880`0ffeb000 rasl2tp rasl2tp.sys Sat Nov 20 05:52:34 2010 (4CE7A872) fffff880`04477000 fffff880`04492000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`045da000 fffff880`045fb000 raspptp raspptp.sys Sat Nov 20 05:52:31 2010 (4CE7A86F) fffff880`00de6000 fffff880`00e00000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`04400000 fffff880`04451000 rdbss rdbss.sys Sat Nov 20 04:27:51 2010 (4CE79497) fffff880`04bf1000 fffff880`04bfc000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`01610000 fffff880`01619000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`017f6000 fffff880`017ff000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`015df000 fffff880`015e8000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01af5000 fffff880`01b2f000 rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E) fffff880`05dd4000 fffff880`05dec000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`01009000 fffff880`01038000 SCSIPORT SCSIPORT.SYS Sat Nov 20 05:34:01 2010 (4CE7A419) fffff880`07df5000 fffff880`07e00000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`01aed000 fffff880`01af5000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`0ac96000 fffff880`0ad07000 spsys spsys.sys Mon May 11 13:20:58 2009 (4A085E7A) fffff880`01099000 fffff880`011fb000 sptd sptd.sys Tue Nov 23 06:47:37 2010 (4CEBA9D9) fffff880`08015000 fffff880`080ae000 srv srv.sys Sat Nov 20 04:28:05 2010 (4CE794A5) fffff880`05000000 fffff880`0506b000 srv2 srv2.sys Sat Nov 20 04:27:43 2010 (4CE7948F) fffff880`07c00000 fffff880`07c31000 srvnet srvnet.sys Sat Nov 20 04:27:20 2010 (4CE79478) fffff880`0125a000 fffff880`012bd000 storport storport.sys Sat Nov 20 05:35:02 2010 (4CE7A456) fffff880`05095000 fffff880`05096480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01843000 fffff880`01a47000 tcpip tcpip.sys Sat Nov 20 04:25:52 2010 (4CE79420) fffff880`07c31000 fffff880`07c43000 tcpipreg tcpipreg.sys Sat Nov 20 05:51:48 2010 (4CE7A844) fffff880`015f3000 fffff880`01600000 TDI TDI.SYS Sat Nov 20 04:22:06 2010 (4CE7933E) fffff880`01236000 fffff880`01258000 tdx tdx.sys Sat Nov 20 04:21:54 2010 (4CE79332) fffff880`045c6000 fffff880`045da000 termdd termdd.sys Sat Nov 20 06:03:40 2010 (4CE7AB0C) fffff960`005f0000 fffff960`005fa000 TSDDD TSDDD.dll unavailable (00000000) fffff880`04b17000 fffff880`04b3d000 tunnel tunnel.sys Sat Nov 20 05:51:50 2010 (4CE7A846) fffff880`08128000 fffff880`0817d000 udfs udfs.sys Sat Nov 20 04:26:11 2010 (4CE79433) fffff880`05097000 fffff880`050a9000 umbus umbus.sys Sat Nov 20 05:44:37 2010 (4CE7A695) fffff880`05db9000 fffff880`05dd3c80 usbaudio usbaudio.sys Sat Nov 20 05:43:52 2010 (4CE7A668) fffff880`05d9c000 fffff880`05db9000 usbccgp usbccgp.sys Sat Nov 20 05:44:03 2010 (4CE7A673) fffff880`06021000 fffff880`06022f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`0ffb6000 fffff880`0ffc7000 usbehci usbehci.sys Sat Nov 20 05:43:54 2010 (4CE7A66A) fffff880`050b4000 fffff880`0510e000 usbhub usbhub.sys Sat Nov 20 05:44:30 2010 (4CE7A68E) fffff880`0ffab000 fffff880`0ffb6000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04b53000 fffff880`04ba9000 USBPORT USBPORT.SYS Sat Nov 20 05:44:00 2010 (4CE7A670) fffff880`00eea000 fffff880`00ef7000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`01bf2000 fffff880`01c00000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`01200000 fffff880`01225000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`01a91000 fffff880`01aa1000 vmstorfl vmstorfl.sys Sat Nov 20 04:57:30 2010 (4CE79B8A) fffff880`00f3f000 fffff880`00f54000 volmgr volmgr.sys Sat Nov 20 04:19:28 2010 (4CE792A0) fffff880`00f54000 fffff880`00fb0000 volmgrx volmgrx.sys Sat Nov 20 04:20:43 2010 (4CE792EB) fffff880`01aa1000 fffff880`01aed000 volsnap volsnap.sys Sat Nov 20 04:20:08 2010 (4CE792C8) fffff880`045ab000 fffff880`045c6000 wanarp wanarp.sys Sat Nov 20 05:52:36 2010 (4CE7A874) fffff880`01600000 fffff880`01610000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00e37000 fffff880`00edb000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00edb000 fffff880`00eea000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`0456d000 fffff880`04576000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`000d0000 fffff960`003e1000 win32k win32k.sys unavailable (00000000) fffff880`01000000 fffff880`01009000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) Unloaded modules: fffff880`01bca000 fffff880`01bd8000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000E000 fffff880`01bd8000 fffff880`01be2000 dump_storpor Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000A000 fffff880`01800000 fffff880`0182b000 dump_nvstor. Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0002B000 fffff880`0182b000 fffff880`0183e000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00013000




So, after reviewing countless forum posts over the past year plus, I finally decided to post my own problem here with hopes someone smarter than I can determine why my Win7 box has been crashing randomly for some time. Saga below...

Built the box in Dec 2010. Worked like a champ for some time. Started random crashes probably about a year later or so, not sure exactly when. Crashes are sporadic and seemingly random. They didn't happen all that often so I only spent a bit of time trying to troubleshoot. After a while, they started to get a bit more frequent but still not bad. At one point I ran MemTest numerous times and while most times it didn't have any errors, sometimes it did. Last fall I bought a couple of sticks of new RAM (F3-12800CL9D-8GBRL) and it seemed to help for a bit. After the crashes continued, I started to suspect something with the video card...

About half the time it crashes I get a BSOD, the other half the screen just goes all garbled and usually freezes required a hard reboot. In December I turned off the auto overclocking on my ASUS mobo's (M4A89GTD PRO/USB3) integrated graphics card (Radeon HD 4290), and that really seemed to help. There were only a few crashes over the next couple of months. Then, all hell broke loose mid-March. All of a sudden it was crashing several times a day, all with the same apparent randomness. I've started another battery of MemTest and still clean except once.

Why do I suspect the integrated graphics card? The problem seems to happen more often when there is something more active going on like a game, video, etc. Also, at times it actually has locked up in the BIOS and a couple of times while doing the MemTest (but no errors were reported). The one time there were errors in MemTest it was odd since it wasn't just a couple...it appeared to trigger something and started reporting continual errors until after about 30 seconds it locked up too. I've been testing with FurMark and while it's made it through a couple of times without crashing, most of the time it does crash. I've tried different shared memory settings for the integrated graphics thinking maybe the Sideport memory on the integrated graphics might be bad, but that hasn't been able to isolate the problem either.

So, not sure what else to do before I start buying new components...I'd rather not have to buy a new graphics card, mobo and CPU since the box I have now seems to be more than enough for us. Other details about the machine are below. I've also thought of doing a clean Win7 install, but since the problem appears to happen when I'm not even in Windows, I'd rather not go through that fun unless I have to. Next step is a new graphics card unless someone finds the smoking gun for me!

CPU: AMD Athlon X4 640
Mobo: M4A89GTD PRO/USB3
RAM: 2x F3-12800CL9D-8GBRL (originally 2x F3-12800CL9D-4GBRL)
Primary HDD: OCZ Vertex 2 60 GB (SDD) (have run scandisk several times, no problems)
Seconary HDD: WD 500 GB and an eSATA WD 1 TB
Powersupply: 600W Coolmaster Silent Pro (was replaced once during this ordeal due to a PSU failure, problem happened before and after).

Thanks in advance for your help!

Rob Attached Files robwdavis.zip (3.04 MB, 16 views) Share Share this post on Digg Del.icio.us Technorati Twitter
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left; а JavaScript must be enabled 04-07-2013 #2 usasma Microsoft Community Contributor This member is a certified Microsoft Community Contributor at Windows 7 Forums. Click here for more information from Microsoft. Microsoft MVP - Windows Expert
- Consumer а
Join Date Mar 2010 Posts 1,333 Re: Long Term Chronic Seemling Random BSOD Problem Just FYI - a recent poster (early Nov 2011) states that they were advised by Asus to manually set their memory settings/timings/voltages because of issues with the M4 series of motherboards.
You can get the settings/timings/voltages from the website of your RAM manufacturer.

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cra...tml#post169956
27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems. You have 3 hard drives. What is the make/model/wattage and age of your Power Supply?

You have numerous different error codes (so many that I lost count) The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect. Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

GRMNGEN.SYS Thu Apr 30 12:45:26 2009 (49F9D5A6)
Garmin Generic WDM Support Driver
http://www.carrona.org/drivers/driver.php?id=GRMNGEN.SYS

grmnusb.sys Thu Apr 30 12:45:27 2009 (49F9D5A7)
Garmin USB GPS driver
http://www.carrona.org/drivers/driver.php?id=grmnusb.sys

AtiPcie.sys Tue May 5 11:00:22 2009 (4A005486)
ATI PCIE Driver for ATI PCIE chipset or [br] ATI PCI Express (3GIO) Filter[br]Found in my ATI video drivers (I have an Intel chipset)
http://www.carrona.org/drivers/driver.php?id=AtiPcie.sys

nusb3hub.sys Thu Apr 22 21:34:35 2010 (4BD0F92B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys

nusb3xhc.sys Thu Apr 22 21:34:36 2010 (4BD0F92C)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys

As you have time, please start running these free hardware diagnostics also: Hardware Diagnostics This'll give you a head start if the 3rd party drivers aren't the cause.

Analysis:
The following is for informational purposes only.
Code: **************************Sat Apr 6 19:26:29.953 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-50544-02.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 1:52:28.608 Probably caused by :hardware ( Unknown_Module_fffff880`044be570>+5ed1588 ) BugCheck A, {7fffffd3fb8, 2, 1, fffff8000387f852} BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) Arguments: Arg1: 000007fffffd3fb8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8000387f852, address which referenced memory BUGCHECK_STR: 0xA DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT FAILURE_BUCKET_ID: X64_IP_MISALIGNED ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 17:25:32.255 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-51605-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:07:29.816 Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 ) BugCheck 1A, {41790, fffffa8001241970, ffff, 0} BugCheck Info: MEMORY_MANAGEMENT (1a) Arguments: Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2 contains the address of the PFN for the corrupted page table page. On a 32 bit OS, parameter 2 contains a pointer to the number of used PTEs, and parameter 3 contains the number of used PTEs. Arg2: fffffa8001241970 Arg3: 000000000000ffff Arg4: 0000000000000000 BUGCHECK_STR: 0x1a_41790 PROCESS_NAME: dxdiag.exe FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 16:31:29.054 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-50559-02.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:13:56.241 Probably caused by :ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) BugCheck 1E, {0, 0, 0, 0} BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e) Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception BUGCHECK_STR: 0x1E DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 16:13:31.572 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-50606-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 4:59:16.133 *** WARNING: Unable to verify timestamp for mfehidk.sys *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys Probably caused by :mfehidk.sys ( mfehidk+16869 ) BugCheck 135, {ffffffffc0000005, fffff88007c7eac0, fffff88001301700, fffff8a00027e380} BugCheck Info: REGISTRY_FILTER_DRIVER_EXCEPTION (135) Arguments: Arg1: ffffffffc0000005, ExceptionCode Arg2: fffff88007c7eac0, Address of the context record for the exception that caused the bugcheck Arg3: fffff88001301700, The driver's callback routine address Arg4: fffff8a00027e380, Internal BUGCHECK_STR: 0x135 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: explorer.exe FAILURE_BUCKET_ID: X64_0x135_mfehidk+16869 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 11:13:08.845 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-50981-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:03:58.406 *** WARNING: Unable to verify timestamp for mfehidk.sys *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys Probably caused by :mfehidk.sys ( mfehidk+48204 ) BugCheck 24, {1904fb, fffff88003df8bf8, fffff88003df8450, fffff8800100d64d} BugCheck Info: NTFS_FILE_SYSTEM (24) Arguments: Arg1: 00000000001904fb Arg2: fffff88003df8bf8 Arg3: fffff88003df8450 Arg4: fffff8800100d64d PROCESS_NAME: services.exe BUGCHECK_STR: 0x24 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT FAILURE_BUCKET_ID: X64_0x24_mfehidk+48204 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 11:08:04.919 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-50559-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:04:41.496 Probably caused by :ntkrnlmp.exe ( nt!KipFatalFilter+1b ) BugCheck 1E, {ffffffffc0000005, fffff88003118fe0, 0, 0} BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e) Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88003118fe0, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception BUGCHECK_STR: 0x1E_c0000005_R PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x1E_c0000005_R_nt!KipFatalFilter+1b BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 11:02:35.768 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-50591-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:07:02.344 Probably caused by :ntkrnlmp.exe ( nt!ExReinitializeResourceLite+f2 ) BugCheck 24, {1904fb, fffff88008eb66e8, fffff88008eb5f40, fffff8000386fba2} BugCheck Info: NTFS_FILE_SYSTEM (24) Arguments: Arg1: 00000000001904fb Arg2: fffff88008eb66e8 Arg3: fffff88008eb5f40 Arg4: fffff8000386fba2 PROCESS_NAME: System BUGCHECK_STR: 0x24 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT FAILURE_BUCKET_ID: X64_0x24_nt!ExReinitializeResourceLite+f2 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 10:53:40.143 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-50544-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:43:35.719 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Probably caused by :ntkrnlmp.exe ( nt!AlpcpProcessSynchronousRequest+366 ) BugCheck 3B, {c0000005, fffff80003be1119, fffff8800a7abfe0, 0} BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b) Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80003be1119, Address of the instruction which caused the bugcheck Arg3: fffff8800a7abfe0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. BUGCHECK_STR: 0x3B DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT FAILURE_BUCKET_ID: X64_0x3B_nt!AlpcpProcessSynchronousRequest+366 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 09:58:20.702 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-50622-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:24:38.263 Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4518f ) BugCheck 50, {fffff88007496eb5, 8, fffff88007496eb5, 0} BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50) Arguments: Arg1: fffff88007496eb5, memory referenced. Arg2: 0000000000000008, value 0 = read operation, 1 = write operation. Arg3: fffff88007496eb5, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) BUGCHECK_STR: 0x50 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x50_BAD_IP_nt!_??_::FNODOBFM::_string_+4518f BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 09:32:47.896 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-51012-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:03:24.082 Probably caused by :hardware ( nt! ?? ::FNODOBFM::`string'+487ed ) BugCheck 1E, {ffffffffc0000005, fffff8000389d6d3, 1, c000005c} BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e) Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8000389d6d3, The address that the exception occurred at Arg3: 0000000000000001, Parameter 0 of the exception Arg4: 00000000c000005c, Parameter 1 of the exception BUGCHECK_STR: 0x1E_c0000005_R PROCESS_NAME: McSvHost.exe FAILURE_BUCKET_ID: X64_IP_MISALIGNED BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Apr 6 09:28:50.155 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40613-14008-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:12:52.716 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by :dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad ) BugCheck 119, {1, f0e4, e4, e4} BugCheck Info: VIDEO_SCHEDULER_INTERNAL_ERROR (119) Arguments: Arg1: 0000000000000001, The driver has reported an invalid fence ID. Arg2: 000000000000f0e4 Arg3: 00000000000000e4 Arg4: 00000000000000e4 BUGCHECK_STR: 0x119 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Fri Apr 5 20:52:10.432 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40513-50996-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:03:45.008 *** ERROR: Module load completed but symbols could not be loaded for partmgr.sys *** ERROR: Module load completed but symbols could not be loaded for volmgr.sys *** ERROR: Module load completed but symbols could not be loaded for volsnap.sys *** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.sys *** WARNING: Unable to verify timestamp for mfehidk.sys *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys Probably caused by :partmgr.sys ( partmgr+3512 ) BugCheck C2, {7, 109b, 30676863, fffffa8007990010} BugCheck Info: BAD_POOL_CALLER (c2) Arguments: Arg1: 0000000000000007, Attempt to free pool which was already freed Arg2: 000000000000109b, (reserved) Arg3: 0000000030676863, Memory contents of the pool block Arg4: fffffa8007990010, Address of the block of pool being deallocated BUGCHECK_STR: 0xc2_7 PROCESS_NAME: WUDFHost.exe FAILURE_BUCKET_ID: X64_0xc2_7_partmgr+3512 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Fri Apr 5 20:47:49.695 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40513-51199-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:06:03.256 Probably caused by :CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce ) BugCheck D1, {6a00, 2, 8, 6a00} BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Arguments: Arg1: 0000000000006a00, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000000000006a00, address which referenced memory PROCESS_NAME: System BUGCHECK_STR: 0xD1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_CLASSPNP!TransferPktComplete+1ce BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Fri Apr 5 19:26:13.785 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40513-51979-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:08:27.346 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by :dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad ) BugCheck 119, {1, ef00, 7d, 7d} BugCheck Info: VIDEO_SCHEDULER_INTERNAL_ERROR (119) Arguments: Arg1: 0000000000000001, The driver has reported an invalid fence ID. Arg2: 000000000000ef00 Arg3: 000000000000007d Arg4: 000000000000007d BUGCHECK_STR: 0x119 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Fri Apr 5 19:00:29.108 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40513-51121-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:01:12.669 Probably caused by :ntkrnlmp.exe ( nt!KiDeliverApc+187 ) BugCheck A, {0, 2, 1, fffff800038cf617} BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800038cf617, address which referenced memory BUGCHECK_STR: 0xA DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0xA_nt!KiDeliverApc+187 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Thu Apr 4 17:53:14.830 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40413-59639-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:02:37.001 Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+27911 ) BugCheck 34, {49d, ffffffffc0000420, 0, 0} BugCheck Info: CACHE_MANAGER (34) Arguments: Arg1: 000000000000049d Arg2: ffffffffc0000420 Arg3: 0000000000000000 Arg4: 0000000000000000 BUGCHECK_STR: 0x34 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x34_nt!_??_::FNODOBFM::_string_+27911 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Mon Apr 1 16:03:22.230 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40113-52728-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 6:27:14.401 *** WARNING: Unable to verify timestamp for ???????? Probably caused by :ntkrnlmp.exe ( nt!PoIdle+52a ) BugCheck 4E, {99, 1d4ab4, 0, 1d4dc4} BugCheck Info: PFN_LIST_CORRUPT (4e) Arguments: Arg1: 0000000000000099, A PTE or PFN is corrupt Arg2: 00000000001d4ab4, page frame number Arg3: 0000000000000000, current page state Arg4: 00000000001d4dc4, 0 BUGCHECK_STR: 0x4E_99 PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x4E_99_nt!PoIdle+52a ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sun Mar 31 21:04:20.090 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps33113-54615-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 1:45:20.588 Probably caused by :win32k.sys ( win32k!EngRestoreFloatingPointState+2a82 ) BugCheck 50, {fffff900c3b46018, 1, fffff9600012a382, 0} BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50) Arguments: Arg1: fffff900c3b46018, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff9600012a382, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) BUGCHECK_STR: 0x50 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: ViewNX2.exe FAILURE_BUCKET_ID: X64_0x50_win32k!EngRestoreFloatingPointState+2a82 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Mon Apr 1 09:35:34.027 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40113-53414-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:01:05.198 Probably caused by :Pool_Corruption ( nt!ExDeferredFreePool+a53 ) BugCheck 19, {3, fffffa80066902b0, fffffa80066908c0, fffffa80066902b0} BugCheck Info: BAD_POOL_HEADER (19) Arguments: Arg1: 0000000000000003, the pool freelist is corrupt. Arg2: fffffa80066902b0, the pool entry being checked. Arg3: fffffa80066908c0, the read back flink freelist value (should be the same as 2). Arg4: fffffa80066902b0, the read back blink freelist value (should be the same as 2). BUGCHECK_STR: 0x19_3 PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a53 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Mon Apr 1 09:30:54.711 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps40113-53601-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 12:23:53.881 Probably caused by :USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f ) BugCheck A, {fffffa880b947000, 2, 0, fffff80003deb3da} BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) Arguments: Arg1: fffffa880b947000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80003deb3da, address which referenced memory BUGCHECK_STR: 0xA DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: MSMONEY.EXE FAILURE_BUCKET_ID: X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Wed Mar 27 22:04:57.939 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32713-53991-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:01:45.499 Probably caused by :storport.sys ( storport!StorPortGetScatterGatherList+1fd ) BugCheck 1E, {0, 0, 0, 0} BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e) Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception BUGCHECK_STR: 0x1E DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x1E_storport!StorPortGetScatterGatherList+1fd BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Wed Mar 27 22:02:27.314 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32713-53024-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 1:50:25.875 Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48de1 ) BugCheck 18, {0, fffffa8009b451e0, 2, ffffffffffffffff} BugCheck Info: REFERENCE_BY_POINTER (18) Arguments: Arg1: 0000000000000000, Object type of the object whose reference count is being lowered Arg2: fffffa8009b451e0, Object whose reference count is being lowered Arg3: 0000000000000002, Reserved Arg4: ffffffffffffffff, Reserved The reference count of an object is illegal for the current state of the object. Each time a driver uses a pointer to an object the driver calls a kernel routine to increment the reference count of the object. When the driver is done with the pointer the driver calls another kernel routine to decrement the reference count. Drivers must match calls to the increment and decrement routines. This bugcheck can occur because an object's reference count goes to zero while there are still open handles to the object, in which case the fourth parameter indicates the number of opened handles. It may also occur when the object?s reference count drops below zero whether or not there are open handles to the object, and in that case the fourth parameter contains the actual value of the pointer references count. BUGCHECK_STR: 0x18 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: iexplore.exe FAILURE_BUCKET_ID: X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+48de1 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Tue Mar 26 22:07:01.610 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32613-54007-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 5:54:04.202 Probably caused by :ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de ) BugCheck 3B, {c0000005, fffff80003b5430e, fffff8800b836720, 0} BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b) Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80003b5430e, Address of the instruction which caused the bugcheck Arg3: fffff8800b836720, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. BUGCHECK_STR: 0x3B DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: OUTLOOK.EXE FAILURE_BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1de BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Tue Mar 26 14:51:24.978 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32613-53071-01.dmp] *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 14:09:27.165 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) BugCheck 1E, {0, 0, 0, 0} BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e) Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception BUGCHECK_STR: 0x1E DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Mon Mar 25 23:07:21.773 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32513-92586-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:03:27.334 *** WARNING: Unable to verify timestamp for amd_xata.sys *** ERROR: Module load completed but symbols could not be loaded for amd_xata.sys Probably caused by :hardware ( amd_xata+8c16 ) BugCheck D5, {fffff9801a680fb0, 1, fffff88001196c16, 0} BugCheck Info: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5) Arguments: Arg1: fffff9801a680fb0, memory referenced Arg2: 0000000000000001, value 0 = read operation, 1 = write operation Arg3: fffff88001196c16, if non-zero, the address which referenced memory. Arg4: 0000000000000000, (reserved) BUGCHECK_STR: 0xD5 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System FAILURE_BUCKET_ID: X64_IP_MISALIGNED_amd_xata.sys BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Mon Mar 25 21:23:38.418 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32513-53913-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:01:49.979 Probably caused by :ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+537 ) BugCheck C5, {8, 2, 1, fffff800039fc147} BugCheck Info: DRIVER_CORRUPTED_EXPOOL (c5) Arguments: Arg1: 0000000000000008, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff800039fc147, address which referenced memory BUGCHECK_STR: 0xC5_2 PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0xC5_2_nt!ExAllocatePoolWithTag+537 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Mar 23 23:58:21.531 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32313-52962-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:00:59.092 *** WARNING: Unable to verify timestamp for amd_xata.sys *** ERROR: Module load completed but symbols could not be loaded for amd_xata.sys Probably caused by :amd_xata.sys ( amd_xata+1d06 ) BugCheck D1, {760, 2, 0, fffff880010e8c1d} BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Arguments: Arg1: 0000000000000760, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880010e8c1d, address which referenced memory BUGCHECK_STR: 0xD1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: explorer.exe FAILURE_BUCKET_ID: X64_0xD1_amd_xata+1d06 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Mar 23 23:56:12.449 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32313-52899-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:08:22.010 *** ERROR: Module load completed but symbols could not be loaded for cdd.dll Probably caused by :cdd.dll ( cdd+599b ) BugCheck 1000007E, {ffffffffc0000094, fffff9600078599b, fffff880069c3778, fffff880069c2fd0} BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) Arguments: Arg1: ffffffffc0000094, The exception code that was not handled Arg2: fffff9600078599b, The address that the exception occurred at Arg3: fffff880069c3778, Exception Record Address Arg4: fffff880069c2fd0, Context Record Address BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x7E_cdd+599b BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Sat Mar 23 18:59:32.947 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32313-51558-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 1:57:20.133 Probably caused by :ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) BugCheck 7F, {8, 80050031, 6f8, fffff80003886f24} BugCheck Info: UNEXPECTED_KERNEL_MODE_TRAP (7f) Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff80003886f24 BUGCHECK_STR: 0x7f_8 PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Fri Mar 22 22:42:58.624 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32213-53586-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:02:53.185 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by :dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad ) BugCheck 119, {1, c301, 1, 1} BugCheck Info: VIDEO_SCHEDULER_INTERNAL_ERROR (119) Arguments: Arg1: 0000000000000001, The driver has reported an invalid fence ID. Arg2: 000000000000c301 Arg3: 0000000000000001 Arg4: 0000000000000001 BUGCHECK_STR: 0x119 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: CCC.exe FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Fri Mar 22 15:03:38.544 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32213-52837-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 3:57:42.105 Probably caused by :SCSIPORT.SYS ( SCSIPORT!DllInitialize+3eed ) BugCheck A, {8, 2, 1, fffff80003817bbe} BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) Arguments: Arg1: 0000000000000008, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80003817bbe, address which referenced memory BUGCHECK_STR: 0xA DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0xA_SCSIPORT!DllInitialize+3eed BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Thu Mar 21 22:45:33.802 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32113-53399-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:02:13.362 Probably caused by :Pool_Corruption ( nt!ExDeferredFreePool+100 ) BugCheck 50, {ffffffffffffffff, 0, fffff800039bb9bc, 0} BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50) Arguments: Arg1: ffffffffffffffff, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff800039bb9bc, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) BUGCHECK_STR: 0x50 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x50_nt!ExDeferredFreePool+100 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Thu Mar 21 22:41:45.790 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32113-52915-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 7:55:40.351 Probably caused by :ntkrnlmp.exe ( nt!KeReleaseSemaphore+137 ) BugCheck A, {fffff880009fdb08, 2, 1, fffff800038a0327} BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) Arguments: Arg1: fffff880009fdb08, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800038a0327, address which referenced memory BUGCHECK_STR: 0xA DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: mfefire.exe FAILURE_BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+137 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Wed Mar 20 21:49:00.797 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32013-53898-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 10:05:03.358 Probably caused by :tcpip.sys ( tcpip!IppInspectLocalDatagramsOut+88 ) BugCheck D1, {13, 2, 0, fffff88001889b68} BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Arguments: Arg1: 0000000000000013, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88001889b68, address which referenced memory BUGCHECK_STR: 0xD1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0xD1_tcpip!IppInspectLocalDatagramsOut+88 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Wed Mar 20 11:43:04.159 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps32013-52899-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:11:47.720 *** ERROR: Module load completed but symbols could not be loaded for usbohci.sys Probably caused by :usbohci.sys ( usbohci+2a45 ) BugCheck FE, {5, fffffa8007e971a0, 10024397, fffffa80077c4258} BugCheck Info: BUGCODE_USB_DRIVER (fe) Arguments: Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is using a physical memory address that was not allocated by the USBport driver. Arg2: fffffa8007e971a0, Device extension pointer of the host controller Arg3: 0000000010024397, PCI Vendor,Product id for the controller Arg4: fffffa80077c4258, Pointer to Endpoint data structure BUGCHECK_STR: 0xFE DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci+2a45 BIOS Version 3029 BIOS Release Date 07/05/2012 Manufacturer System manufacturer Product Name System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` **************************Tue Mar 19 19:59:58.266 2013 (UTC - 4:00)************************** Loading Dump File [C:UsersOwnerSysnativeBSODApps31913-52884-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime:0 days 0:04:45.842 Probably caused by :hardware ( nt!KiInterruptDispatch+22 ) BugCheck A, {ffffda802fc8f485, 2, 1, fffff80003876952} BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) Arguments: Arg1: ffffda802fc8f485, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800038




Hi guys, I'm putting this in the hardware forum but it may be something else that's the problem so I guess I'll just see what jumps out at me first.
The problem I'm having at present is a duplicate of one I suffered in February which caused me so much grief.
I didn't find an acceptable answer then but I did manage to get things moving by buying and installing a new hard drive.
So: here we go.
The computer, a desktop one with Win 7 installed, has 3 hard drives. Had 3 drives, may be a better description but more on that later.

For no apparent reason when I started it up one morning around a week ago it took forever to load up. I mean in excess of 3 hours. From that point everything that I tried to do such as open a file or a programme (I'm English) took substantial times to open, in fact trying to move the cursor from one side of the screen to another took 90 minutes and was completed in moves of around half an inch at a time before freezing again.
I have an up to date antivirus (Kaspersky) as well as malwarebytes. I haven't installed anything recently, or even removed anything that could have left stuff in the registry.
I have run a Ram check and nothing shows as a problem there. I have booted directly from a Kaspersky startup disc to check for boot virus activity but this is all clean. I did the same thing with AVG startup disc to double check.
I have tried to do a Restore, a Last Known Good Configuration, and also a Repair from a Windows disc to one of the hard drives but this doesn't cure anything.
Now, for those who are already ahead of me, this same thing happens on each of the drives I try to boot from so it appears to be non hard drive related.
Actually, getting back to the 3 hard drives, on one reboot the one I used as my normal primary went missing from the system and the computer went through a complete file check removing apparent dead links that related to the missing drive from the other drives.
I have now installed a new windows 7 onto one of the drives. I didn't mean to, I just loaded the Win7 disc to do another system check from a DOS prompt but as it took so long to load the disc I fell asleep and it installed the new Windows by default.
So, the new system is still the same. Naturally it hasn't had any other devices set up on this drive so no conflict of drivers is likely. Nevertheless it's still no better.
I'm thinking it has more to do with hardware for this reason. As I said, the RAM checks out OK.
I guess a dodgy processor would just not work at all. Maybe I'm wrong but I'm sure you'll let me know. What would be the result of a CMOS battery being almost done for? Could that be the problem, or not?

I've gone to the expense of buying a motherboard bundle today with processor, ram etc and am likely to just install them but before I do I thought I'd throw this to the forum to see if it hits home with anyone. I'd still rather get this system working and perhaps, just maybe, get my hard drive back from the land of the dead, especially since this was the new one I fitted in February and has most of my useful stuff on it.
Any ideas guys n'gals

Added when remembered of importance.
Thinking back, when I had this same problem in February it wasn't so much to do with a slow computer, I just lost without any reason my primary hard drive. I could still access the other drives and managed to salvage some stuff from them that related to files I made as backups.
I still got the dreaded startup CHKDSK which threw out loads of stuff from God knows where. It took a whole night to complete on the 1st occasion but that wasn't the end of it.
It did the same thing each time I restarted the computer and seemed to find thousands more dead links/files etc each time.
I did a fsc scannow and other stuff at the time, as well as loads of other recommended things that I read about on various forums, to see if that threw any light on the situation but it didn't.
At least I got pretty normal access to the remaining drives although the dead hard drive at that time never recovered to my knowledge.
I fitted the new one on the same SATA connection so I wonder..............




Hi all, I recently bought a refurbished laptop and after fixing most of the problems I've encountered, this one doesn't seem to want to go away.

For a quick run down of specs, I'm running Win7 Home premium 64-bit on an Advent Roma 4001, Intel Dual Core T4400, 4GB RAM and 500GB HD.

During the "Please wait" and "Welcome" messages it can take up to 2 minutes just to log on, but the main problem occurs after logging in. The CPU usage, apart from System Idle Process (of course) is pretty much zero, and the RAM usage is down at about 30MB. Everything seems responsive, however, when I attempt to open a program or process I'm getting incredible lag. If I'm quick enough, I can open up a window or two or a program before the lag strikes. The strange thing is it doesn't actually appear to be unresponsive (apart from when it lags with my internet browser on-screen and the loading animation freezes). The programs all load given time, usually between 2-5 minutes, and for all they run slowly for an amount of time, still run. I don't notice any processes or services that are hogging the memory or being specifically tied to causing the lag after executing them. The slowness is recurrent through every execution I make - through opening windows explorer to my internet browser, a program or just opening up the start menu - everything lags for the same amount of time. Something then just seems to "click" after a while, and everything runs smooth as pie; the programs I've tried to open up all flick on as if they were queued and waiting for something to clear.

I've tried chkdsk, messing around with msconfig, including performing a clean boot by turning off all non-windows process and startup icons within msconfig (and I have kept those settings for every boot, no luck), made sure all drivers are updated and functioning, seeing if the problem occurs in safe mode (it doesn't), checked event viewer for any critical errors (there are none, but a hell of a lot of standard errors, mostly, 7 Disk) no viruses or malware have been found after searches, ran sfc /scannow, checked the memory with a repair disk... I've tried a lot. From other problems with the system I've had to reinstall the OS 3 times and this has occurred on each install, so I'm not going through that again. It doesn't happen for around the first day after an OS install and crops up slowly, which tells me there's something that can be fixed, I just don't know what.

It may be worth noting that I can't seem to do a System Restore, since after running the restore I get a message pop-up after restart that it couldn't locate C:/Windows/assemblys/NativeImages etc... I have tried not to disable services in msconfig since it would delete my restore points, but I'm tempted - the problem may be there.

I haven't tried Driver Verifier (god forbid) and I'm really hoping it's not a hardware issue (since the problem is cured after a few patient minutes, I wouldn't think it was). Does anyone have any suggestions?

Thanks, Anton.

EDIT: The problem was the services. I was reluctant to tamper with them since it means you lose all your system restore points, but the problem was there. After disabling everything by running 'Diagnostic mode' in msconfig, the problem was gone. I'm still not sure what the service was, but after enabling my critical processes only, voila!


Page 2 of 2.
Results 21...33 of 33