chkdsk on reboot windows 7 Results

Page 1 of 3.
Results 1...20 of 46

Sponsored Links:

Occasionally my Windows 7 64 bit system crashes. When it happens the screen goes crazy (filled with black and white static) for several seconds, then it reboots. I haven't noticed any discernable pattern as to triggering events. Any help in troubleshooting this would be greatly appreciated.

I have attached the minidump for the most recent crash.

System specs are as follows:

CPU: Intel core i5 750 2.6 GHz (not overclocked)
Motherboard: Gigabyte P55-UD3
Graphics: Sapphire HD5770 1GB
Graphics Driver: 8.671-091026a-090883E-ATI
Catalyst Version: 9.11
Memory: Corsair CMX4GX3M2A1600C9 4GB

Thanks in advance ... Attached Files (25.8 KB, 79 views) Share Share this post on Digg 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-16-2010 #2 busydog Senior Member Enjoys Windows 7 Forums
Join Date Feb 2009 Posts 528 The two most likely causes of a random crash are memory and bad hard drive sectors.

Run a DOS-boot memory scan to check for bad memory (Google for a program to create a bootable ISO) and use Tools under your C-Drive (from My Computer) to run a chkdsk with repair of bad sectors.

Originally Posted by stevecnz Occasionally my Windows 7 64 bit system crashes. When it happens the screen goes crazy (filled with black and white static) for several seconds, then it reboots. I haven't noticed any discernable pattern as to triggering events. Any help in troubleshooting this would be greatly appreciated.

I have attached the minidump for the most recent crash.

System specs are as follows:

CPU: Intel core i5 750 2.6 GHz (not overclocked)
Motherboard: Gigabyte P55-UD3
Graphics: Sapphire HD5770 1GB
Graphics Driver: 8.671-091026a-090883E-ATI
Catalyst Version: 9.11
Memory: Corsair CMX4GX3M2A1600C9 4GB

Thanks in advance ...

ok, i've tried EVERYTHING, but my copy of windows 7 is still refusing to boot in any mode at all.

first of all, it's a 64x edition of the 7600 build of windows 7, i have successfully booted into it ONCE, and that was during installation, after it rebooted me for configuration i promptly was not ever able to boot into it again sucessfully.

i've tried removing all USB devices, disabling USB and LAN in the BIOS, no luck.

I've tried booting with "startup repair" option and it dies on me, i've tried safe mode too, no luck.

I booted with the install disk under "repair system startup" and the error log it outputted i'll type at the end*

the ONLY thing i haven't tried is booting from the win7 dvd, and when i use it there seems to be no option to boot the actual OS from it, only "install" and "repair"

the only other thing i can mention as relevant is that i have 2 HDs, with WinXP on the first drive (set to boot first) and win7 installed on the second (set to boot after) and that even during chkdsk win7 refers to itself as being on D: (even though operating system always regard the location of the OS as C: )

*windows repair error log

my specs are
500gb hd (winxp) and 1tb hd (win7)
intel core 2 duo 2.66 (OC to 3.01)
8gb DDR2
radeon 4870x2


I've been running my Windows 7 x64 machine for about 3 weeks without problem. All of my programs are installed on the SSD and the HDD is for data files. Simple. Easy.

I run dual display with no problem, 1920x1080 on the 24" LED (DVI), and extended to a 19" LCD (VGA).

My dad was kind enough to buy me a 32" 1080p Insignia TV for christmas. I bought a cheap HDMI cable online, and when it came in the mail i decided I would set my computer up to have 3 monitors. (I didn't know that my graphics card only supports 2 at a time, I know this now.)

So I plugged in the HDMI Cable to the TV and to the Computer. The 24" LED screen (my main one) Twitches for a moment then returns to normal, the TV comes on, and the 19" LCD goes blank. All is good except Aero magically shut off. After fiddling with the display settings and realizing i can only have two monitors at a time. I decide on the 24" and the 32" for now, but leave all three plugged in. I restart the computer in hopes of returning Aero. THe computer takes a VERY long time to start up and when it does, i'm presented with a dialog telling me that a page file has been created for me.
My page file SHOULD have been on my HDD (to keep room on my SSD, with 8GB of RAM i didnt think page file was THAT important).

I click the dialog and the page file settings open up. i go to check and make sure they are correct, but when i select the HDD from the listbox, everything stops working right. Page file dialogs go not responding. I open task manager and all looks good in processes. Start bar won't open. It looks like the computer is thrashing, but it never gets around to catching up with itself, so i shut it off and try again with the same results. Then i unplug everything but the DVI monitor, the mouse and the keyboard, and try again... same results. Tried safe mode... same results. So i shut it off and let it be for a day (i was pretty frustrated)

I come back today, turn it on and it hangs forever on the 'Starting Windows' boot screen. I shut it off and figure.. I didnt have that much on there, I might as well wipe the drive and start from scratch, thats the easiest solution, so i pop in the Windows 7 x64 DVD, reboot the machine, all looks good, and i go for install, and it Hangs forever on the 'Setup is starting...' screen with a spinning wheel cursor.

One more time i restarted the computer without the disc booted 'normally' and it hung on the 'Starting Windows' screen for a little while, then entered CHKDSK. I let that run, and after running for a bit, for 30 minutes, it sat saying 'CHKDSK is verifying Usn Journal...'

I have no idea what that means so here I am.

Thanks for reading my long story but i wanted to give as much detail as possible.
I appreciate any help that can be afforded, thanks,


PC Specs:
System Manufacturer/Model Number
Windows 7 Ultimate x64
AMD Phenom II x4 925 (2.8G/8M)
Gigabyte GA-770T - USB3
4X [CORE i7-DDR3] 2GB DDR3-1600 (8GB Total)
Graphics Card
PALIT GTS450 1GB (nVidia)
Sound Card
on board sound
Monitor(s) Displays
ViewSonic 1080p LED 24" DVI
Insignia 32" LCD HDMI
ThinkVision 19" LCD VGA
Microsoft - Wireless USB
120MM Liquid Cooler
Hard Drives
40GB INtel x25-V 2.5" SATA MLC-SSD
Internet Speed
Verizon FiOS - Basic

Brand new AMD XII6 machine with barely anything installed. Greatly appreciated! Attached Files Minidump (126.6 KB, 110 views) Share Share this post on Digg 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 10-02-2010 #2 TorrentG Premier Member Enjoys Windows 7 Forums
Join Date May 2010 Posts 3,913 Re: Windows 7 64bit BSOD after wake up from sleep Hey there.

Install the latest On/Off Charge utility from Gigabyte's website to update this driver that I personally know to cause problems:

AppleCharger AppleCharger.sys Mon Apr 26 23:54:05 2010

Update this NEC 3.0 USB driver from Gigabyte's site for your motherboard:

nusb3hub nusb3hub.sys Fri Nov 20 05:15:57 2009

Uninstall all other utilities from Gigabyte to rid this driver or manually delete it. It's at C:WindowsSysrtem32drivers:

gdrv gdrv.sys Thu Mar 12 23:22:29 2009


Run this command from an elevated command prompt:

chkdsk /r


If crashes persist, uninstall Zone Alarm then boot to safe mode and uninstall Avast with the tool found here:

AV Uninstallers

Reboot and install MSE to replace it.

Something totally wierd and shocking happened with my machine running on Windows 7 today (25-06-10).

This is what happened, everything was working fine till the evening. I was back home from a hard day, started my machine and i saw a message that windows has updates that needs to be downloaded. I check the required updates, there were couple of .net framework and few windows kb series. i assumed them to be normal critical updates and as usual i updated my windows 7.

After successful update windows rebooted and something weird happened. i have 4 drives, 1 primary C: and 3 logical (D,E,F). All of a sudden drives D,E,F were unaccessible. It gave Data Error: Cyclic redundancy . And when i tried to right-click and open it, it asked me to format the drive. i thought it could have been something with the update. So i restored backed to my restore point created before the update. After restore the drives were still unaccessible, except the C: i was able to access the C:

I started disk management to see the state of the drives. Surprisingly all the 3 drives showed RAW healthy state. I was shocked as i had all my critical data in those drives. i tried running chkdsk from command prompt on these drives, but it gave the same error.

I then tried putting in the startup disk to boot from cd and check if my data was still there, i rebooted by booting from the startup disk. The screen freezed on a black screen. i removed the cd and rebooted my machine. This time it gave me an options stating start windows normally or repair. I tried to start windows normally, but it failed and just rebooted again. This continued several times. I then went on the option to repair. The repair process just stucked on attempting repair. I rebooted and tried to install windows again. But it said windows cannot be installed on the drive and showed me an unsed 239 GB drive which is my HDD (250GB). Where did my logical drives and the data in it go

i tried the following options from recovery disk i.e running the following commands from the prompt.:

but all the commands gave a same error "A device attached to the system is not functioning"

i just dont know what to do now ?? All my 12 years career data is in that drive !!

To add to the pain, my external backup drive has been sent to the vendor for RMA, since it had accidentally fallen from my hand and drive was thus unaccessible.

Please help me start my system and retrieve my data

Everything was going so well until now...

I installed Windows 7 SP1 64-bit on a Toshiba laptop which used to have Vista 32-bit on it.

Yesterday I put in all the Toshiba drivers and ran chkdsk and am pretty sure it was ok.

I ran chkdsk tonight and got a message that was so quick I can barely read it, but on reboot at the end it says "A disk checking has been scheduled. Disk checking has been cancelled" which comes and goes very quickly.

In BootExecute in the registry it seems OK and shows it as "autocheck autochk*".

Any ideas?

You reboot your PC and have it boot to the Windows 7 install DVD.

Once the DVD is loaded, you can choose install or repair. In many cases, repair works.

If you are an enterprise customer, you would be provided a copy of DART (Microsoft Diagnostics and Recovery Toolset). It looks just like a recovery disk (it does not install an OS), but adds an additional option which opens another window providing you with about another dozen tools, which can come in handy. Search Microsoft's site and I believe it is now publicly available, hovering around v73.

Neither of the above resolves my situation -- I cannot get to the Windows 7 desktop to run an in-place upgrade (now referred to as a repair installation).
Anyway, if you choose install, you are prompted with Upgrade or Custom, where the former would retain all of your programs & their settings, only requiring you to redo any tweaks you might have made to the OS, and the latter will wipe out all those settings, requiring that you reinstall all your programs from scratch.

With Windows 7 installed, if you choose Upgrade, you will be presented with text indicating that the PC started by booting the DVD and in order to run an upgrade (in my case, it would be an in-place upgrade), it has to be done from the Windows desktop (not verbatim).

If you cannot get to the desktop you cannot directly do an in-place upgrade (now referred to as a repair installation), as was provided for in previous Windows incarnations (I have "worked with" Microsoft since DOS 1.0).

Almost every mention of repair installation I see repeats, and is based upon, Microsoft's mantra that you cannot do an in-place upgrade if you booted first to the DVD -- ask any Microsoft tech, and you will hear that almost word for word from each of them.

If Microsoft states that xyz are your only supported solutions and all three do not work, you can either accept that you are screwed, or delve deeper into what is possible, but not Microsoft supported.

It is the latter solution that I am looking for. I have no interest in whether Microsoft supports the solution; my interest is in whether it resolves my problem.

I was using Paragon Partition Manager 11 to defrag the MFT and then compress the MFT. I saved the last of my drives (C & D) for last (making sure all the others were fine first), and that required a reboot, where Paragon's software did its thing, totally mangling my boot-up.

I am running Windows 7 Ultimate SP1 64-bit, running at 4.140Mhz, 12G RAM, 5 internal HDDs and 7 external HDDs and all are fine ("chkdsk /b", along with the latest TestDisk, via various LiveCDs were used to determine that). Disconnecting (not just disabling) all drives except Drive-C had no positive effect.

A writable Windows 7 SP1 DVD (downloaded and created from the Partner Portal's Action Pack) is being used.
I have already had this to the Microsoft Professional Tech group who then escalated it to a Sr Engineer, after I documented all the steps I took on my own (both Windows and Linux-based). We are actively working on it, but I would love to have the solution before he does...

So, thinking outside the box, how can you make the DVD believe that it did not start the PC?

Hi, after I play Battlefield3 for 40/50 minutes i get a 0x124 BSOD. I searched a lot through the internet but none of the solutions I found worked for me, so I hope you can help me.
I read the guide on how to post a help thread and I hope that in the attachment you'll find everything you need (SF Diagnostic files, CPUz screens, rammon report).

Thanks in advance. Attached Files Seven (1.25 MB, 36 views) Share Share this post on Digg 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 12-05-2011 #2 Elmer Tier 2 Moderator Resident eejit
Join Date Mar 2010 Posts 1,946 Re: Battlefield3 Hi Feariss and Welcome to The Forum.
Apologies for the delay in a response, you seem to have slipped through the safety net (what safety net?? ).

Usual causes: Hardware, Incompatibility, May be driver corruption.

Your latest dump file lists hardware as the probable cause.
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes. Random stop codes can often indicate hardware issues.

As a Priority:

The dtsoftbus driver has been known to cause problems on some Windows 7 systems. This belongs to Daemon Tools Light. I suggest uninstalling until your blue screens are resolved.

You're getting a stop0x124, which means blame the hardware.

Stop 0x124 Checks
Ensure that none of the hardware is being over-clocked. Ensure that the machine is adequately cooled. Chase out those dust bunnies! Make sure all hardware related drivers are up to date. Possibly update the motherboard BIOS according to the manufacturer's instructions. Always keep The Windows system itself up to date.
See this thread for additional pointers: Stop 0x124 - what to try.

Update your bios to the latest available. You'll have to use the Vista x64 OS as an option as Windows 7 isn't listed. ASUSTeK (double check I've the right Mobo!!).

You have two different sets of RAM installed, it may be worth running with only 2gb installed just to check stability. I'd go with the Kingston RAM first, making sure they are installed in the recommended slots for your Mobo. (Note this is only to see if your machine becomes more stable, not to check if you have faulty ram).

Some hardware tests you should be prepared to run:Run Chkdsk
Run the correct Hard Drive Diagnostics Tool for your HDD.
Memtest86+ iso download.
Guide to using Memtest86+
CPU - Stress Test with Prime95. Run the "Blend" and "Small FFTs" tests (but see below link).
Video Card - Stress Test with Furmark.

As you are having problems when gaming I would reset the graphics drivers.

Download and install Driver Sweeper.Uninstall your current Graphics setup through Programs and FeaturesBoot to (preferably) Safe Mode and run Driver Sweeper to clean up the remnants of your current Graphics set up.Reboot to Normal Mode.Install your new Graphics set up.AMD Graphics Drivers

Then I would stress test the Graphics Card as listed above under Hardware tests.

Bugcheck Analysis: Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa800444b6d8, 0, 0} Probably caused by : hardware Followup: MachineOwner Your drivers list is very limited, usually happens when the bsod's are saying it's a hardware related fault.
Drivers: Code: fffff880`00f8e000 fffff880`00fe5000 ACPI ACPI.sys Sat Nov 20 09:19:16 2010 (4CE79294) fffff880`00ded000 fffff880`00df8000 amdxata amdxata.sys Fri Mar 19 16:18:18 2010 (4BA3A3CA) fffff880`00c86000 fffff880`00c8f000 atapi atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`00dc3000 fffff880`00ded000 ataport ataport.SYS Sat Nov 20 09:19:15 2010 (4CE79293) fffff880`00e1b000 fffff880`00edb000 CI CI.dll Sat Nov 20 13:12:36 2010 (4CE7C944) fffff880`01988000 fffff880`019b8000 CLASSPNP CLASSPNP.SYS Sat Nov 20 09:19:23 2010 (4CE7929B) fffff880`00d08000 fffff880`00d66000 CLFS CLFS.SYS Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`01000000 fffff880`01072000 cng cng.sys Sat Nov 20 10:08:45 2010 (4CE79E2D) fffff880`019b8000 fffff880`019c6000 crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD) fffff880`01972000 fffff880`01988000 disk disk.sys Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`019d2000 fffff880`019db000 dump_atapi dump_atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`019c6000 fffff880`019d2000 dump_ataport dump_ataport.sys Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`019db000 fffff880`019ee000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F) fffff880`01140000 fffff880`01154000 fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481) fffff880`010f4000 fffff880`01140000 fltmgr fltmgr.sys Sat Nov 20 09:19:24 2010 (4CE7929C) fffff880`0122c000 fffff880`01236000 Fs_Rec Fs_Rec.sys Tue Jul 14 00:19:45 2009 (4A5BC111) fffff880`01938000 fffff880`01972000 fvevol fvevol.sys Sat Nov 20 09:24:06 2010 (4CE793B6) fffff880`0182b000 fffff880`01875000 fwpkclnt fwpkclnt.sys Sat Nov 20 09:21:37 2010 (4CE79321) fffff800`02e13000 fffff800`02e5c000 hal hal.dll Sat Nov 20 13:00:25 2010 (4CE7C669) fffff880`0192f000 fffff880`01938000 hwpolicy hwpolicy.sys Sat Nov 20 09:18:54 2010 (4CE7927E) fffff880`00e0d000 fffff880`00e15000 intelide intelide.sys Tue Jul 14 00:19:48 2009 (4A5BC114) fffff800`00bb7000 fffff800`00bc1000 kdcom kdcom.dll Sat Feb 05 16:52:49 2011 (4D4D8061) fffff880`01200000 fffff880`0121b000 ksecdd ksecdd.sys Sat Nov 20 09:21:15 2010 (4CE7930B) fffff880`01400000 fffff880`0142b000 ksecpkg ksecpkg.sys Sat Nov 20 10:10:34 2010 (4CE79E9A) fffff880`00ca5000 fffff880`00cf4000 mcupdate mcupdate.dll Sat Nov 20 13:03:51 2010 (4CE7C737) fffff880`00c6c000 fffff880`00c86000 mountmgr mountmgr.sys Sat Nov 20 09:19:21 2010 (4CE79299) fffff880`00fee000 fffff880`00ff8000 msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE) fffff880`01154000 fffff880`011b2000 msrpc msrpc.sys Sat Nov 20 09:21:56 2010 (4CE79334) fffff880`0191d000 fffff880`0192f000 mup mup.sys Tue Jul 14 00:23:45 2009 (4A5BC201) fffff880`014a5000 fffff880`01598000 ndis ndis.sys Sat Nov 20 09:23:30 2010 (4CE79392) fffff880`01598000 fffff880`015f8000 NETIO NETIO.SYS Sat Nov 20 09:23:13 2010 (4CE79381) fffff800`02e5c000 fffff800`03445000 nt ntkrnlmp.exe Thu Jun 23 03:53:23 2011 (4E02AAA3) fffff880`01246000 fffff880`013e9000 Ntfs Ntfs.sys Fri Mar 11 03:39:39 2011 (4D79997B) fffff880`00d99000 fffff880`00dae000 partmgr partmgr.sys Sat Nov 20 09:20:00 2010 (4CE792C0) fffff880`00d66000 fffff880`00d99000 pci pci.sys Sat Nov 20 09:19:11 2010 (4CE7928F) fffff880`00c5c000 fffff880`00c6c000 PCIIDEX PCIIDEX.SYS Tue Jul 14 00:19:48 2009 (4A5BC114) fffff880`0121b000 fffff880`0122c000 pcw pcw.sys Tue Jul 14 00:19:27 2009 (4A5BC0FF) fffff880`00cf4000 fffff880`00d08000 PSHED PSHED.dll Tue Jul 14 02:32:23 2009 (4A5BE027) fffff880`018e3000 fffff880`0191d000 rdyboost rdyboost.sys Sat Nov 20 09:43:10 2010 (4CE7982E) fffff880`018d9000 fffff880`018e3000 speedfan speedfan.sys Fri Mar 18 16:08:46 2011 (4D83838E) fffff880`018d1000 fffff880`018d9000 spldr spldr.sys Mon May 11 17:56:27 2009 (4A0858BB) fffff880`01627000 fffff880`0182b000 tcpip tcpip.sys Thu Sep 29 04:43:04 2011 (4E83E948) fffff880`00e00000 fffff880`00e0d000 vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB) fffff880`01875000 fffff880`01885000 vmstorfl vmstorfl.sys Sat Nov 20 09:57:30 2010 (4CE79B8A) fffff880`00dae000 fffff880`00dc3000 volmgr volmgr.sys Sat Nov 20 09:19:28 2010 (4CE792A0) fffff880`00c00000 fffff880`00c5c000 volmgrx volmgrx.sys Sat Nov 20 09:20:43 2010 (4CE792EB) fffff880`01885000 fffff880`018d1000 volsnap volsnap.sys Sat Nov 20 09:20:08 2010 (4CE792C8) fffff880`00edb000 fffff880`00f7f000 Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F) fffff880`00f7f000 fffff880`00f8e000 WDFLDR WDFLDR.SYS Tue Jul 14 00:19:54 2009 (4A5BC11A) fffff880`00fe5000 fffff880`00fee000 WMILIB WMILIB.SYS Tue Jul 14 00:19:51 2009 (4A5BC117) Mini Kernel Dump does not contain unloaded driver list Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.


Hi guys,
I come back to you after some time away in a happy place where tech support is never needed, once again humbly requesting your expertise.

When my laptop hinge busted, I salvaged the HDD and decided to mount it in my next desktop build and use it until I bought another HDD to sell it with. This drive was partitioned with a dual boot of Win7pro64 and Backtrack 5r1 64, both were pretty well maintained, no foreseeable issues with swapping the drive, right?

Well, we seem to be having some technical difficulty, on both fronts. As this is sevenforums, Ill restrict this to my Windows 7 issues, but for any bilingual folks out there that are interested, I'm posting the other half of the dilemma on linuxquestions, sparing them the windows part of it lol. Ill add a link to it once its up.

Okay so here is the hardware setup I am working with.

Asus M5A97 mobo, amd970/sb950 chipset, is rated to support all components
AMD FX-8120 CPU Black Edition
16 GB G-Skill Sniper pc3-12800 ram
XFX nVidia GeForce 6800GT 256MB GDDR3 (I can hear your snickering )
Raidmax 630w PSU
Samsung Supermulti Optical
WD Scorpio Black Laptop SATA HDD

Everything listed is brand new, purchased online, save for the HDD of course. The video card was purchased used at the local computer shop, last-minute.

So just let me explain the nvidia card real fast I planned this build assuming my old HD3870 would work just fine, but it went out on me almost right away. I had it hookup up to a coby tv with a 1366x768 resolution, which is what the nvidia card is powering now as well, via DVI-I output to a DVI to HDMI adapter, then through an HDMI-HDMI cable to the tv, same as the HD3870 was (in case any of that proves relevant). My original intention was to leave this setup open for crossfire if I found another 3800 series. I should note that while the HD 3870 was working, I had booted it up alright and gotten to the boot animation for Windows 7 once. It then proceeded to reboot, after which my video card was toast and I could not get a successful POST. Now that the card is changed, here is what I am experiencing.

When I boot up, I get a POST beep, I go into the BIOS, everything is looking tip top. I select the HDD, everythings still going fine. Since I am running a dual-boot configuration, GRUB is my boot manager. I select the Windows 7 Boot Loader, and I have the option to run startup repair or try to boot normally. I tried the startup repair a few times. The first time it said attempting repairs, then said it would reboot and either boot successfully or continue startup repair. It does not boot up fine, in fact, I get a BSOD. I try the startup repair again, only for it to tell me the problem couldnt be fixed automatically. Well it gives me two options, to either view advanced details in a log file of some sort, or to log in to a user account to run some diagnostic utilities.

The log shows no errors of any kind - I went through each instance of startup repair and they were all negative for each category. There was one "root cause" listed for each attemp which said that 'a recent hardware change' may have caused this to happen. I was told by my college professor who holds an advanced certification for Windows 7 that you could swap a Windows HDD to another computer, and all that would happen is most hardware would default to Windows generic drivers, and you would have some short window of time to reactivate Windows within, due to some sort of built in anti-piracy feature throwing up red flags at the substantial hardware change. Have I been ill-informed, or do I have bigger problems than that?

I logged into my administrative account and the options provided are as follows: Startup Repair, System Restore, System Image Recovery, Windows Memory Diagnostic, and the Command Prompt.
Startup Repair just fails and loops me back, System Restore can't find any restore points (very odd), and System Image Recovery is unusable for me since I never made a backup image. I ran the memory diagnostic as well as chkdsk /f, as advised, and neither found any errors. Selecting the Commant Prompt option, my working directiory is x:windowssystem32. I can switch over to c:, and I can access all of my files, personal, applications, and system alike, which appear to be intact (much of this I have verified via examination from my Backtrack/Linux partition).

Well, I've taken the Windows 7 course, and I don't want to screw around with finding the perpetrator behind my misfortune if I don't have to - I'll just do a side by side install, throw everything on c: into the "Windows.Old" folder, and get the ball rolling on re-crafting my setup, followed by some housecleaning. I have my original product key, all I have to do is pop in that install disc, right? Save the day? I could not have been more wrong.

I actually get a blue screen error while booting from the install disc. This is burnt with an iso obtained from MSDNAA, a legitimate copy of Windows 7 Professional 64 bit, the SP1 Debug Rollup. It's what I used to install the Windows 7 that is currently failing that I'd used for well over a year, and the Windows 7 on another machine I'd built. The serial is registered to me and it was all free through my college. When I did my second install, upon activation I asked if I would need to request a new serial since this one had been used, and was told NO, that my serial is MSDNAA specific, usable as many times as I'd like for academic purposes. You cannot even retrieve these from the system using means that would otherwise produce the correct key - it will come back as five sets of five B's. These are the only two times it has been used and this most definitely does not count as a third since it is the same OS, HDD, owner, serial, and disc even.

Circling back to the BSOD, the interesting thing to me is that the exact same blue screen error comes up while booting my Windwos partition as while attempting to boot from CD to reinstall. Is that significant? I know the terminology sort of clumps them all into the same category, but surely there is a correlation, no? I thought perhaps I was going crazy, and Windows had set some bit switch on the HDD that says "Help, I'm supposed to be in a laptop!" but this does not explain the CD.

I have tried to boot into safe mode, have tried Automatic System Recovery (which im given to understand is the same as Startup Repair), but no cigar. ASR behaves as startup repair did and safe mode = bsod. I have attached a picture of the error screen for reference. I have a copy of Ultimate Boot CD for Windows on my USB drive, but there is a plethora of utils and I dont know how to use most of them. If there is a specific tool that could remedy the issue or shed some light on the situation, I can certainly collect info and report back.


Thanks in advance, all you guys!

Here's what I got: PLEASE HELP!!!!

AMD Phenom II x4 3.20 GHz
2 x 2GB Corsair Ram DDR3
Biostar TA880GB+
Corsair 400w power supply
1TB Samsung Spinpoint F3 HD103SJ
Acer H2038 Monitor
Microsoft Wireless 5000 keyboard and mouse
Windows 7 Ultimate

I put the PC together my self a couple months ago..since then I've been getting random, almost always different BSOD's when starting up my PC. It seems to happen more often on cold starts after hours of not turning on the pc. I am also gettin BSOD's while using windows if I am able to load it.

-I've done a clean install of windows 7 ultimate several times.
-I've run memtest through 7 passes and haven't found errors on either stick..I also tried using each memory stick individually and still came up with BSOD's
-I tried sfc /scannow several times as well as chkdsk
-I tried startup repair...sometimes it works, sometimes it doesn't work.
-System restore usally lets me boot up after restart, but later I will get BSOD again. Sometimes I get the "referenced memory could not be read" error during system restore process and I have to reboot.
-I updated my bios after about 2 weeks of getting errors and also tried updating everything else of the motherboard manufac. site.
-I tried all windows updates for my hardware
-I ran the samsung hard drive diagnostic and didn't get any errors.
-I get BSOD's even without installing any software on clean installs
-I tried reseating everything on my MOBO
-I don't have an extra PC to swap out hardware with..

I don't know if I can give anymore useful info, but I have attached my dumpfiles and hopefully someone can please help me!!! I finally built this PC and haven't been able to enjoy it yet...PLEASE HELP.... SOMEONE!! Attached Files (76.4 KB, 66 views) Share Share this post on Digg 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 09-22-2010 #2 TorrentG Premier Member Enjoys Windows 7 Forums
Join Date May 2010 Posts 3,913 Re: BSOD extravaganza on new build HELP!!! Update your wireless driver from the manufacturer's site:

netr28u netr28u.sys Wed Feb 25 21:42:42 2009


Navigate to C:WindowsSystem32drivers and delete this:

BIOS BIOS.sys Wed Mar 16 02:23:52 2005

Reboot and run Ccleaner to clean the registry.


The above will fix it. Enjoy.

My Desktop crashed the other day and have been trying to fix. I can get the machine to boot in safe mode but can not get to boot in standard mode with out it getting to log in screen then after logging in crashing with Blue screen. There were a number of windows updates that were installed just a little while before the crach as well.

I've run chkdsk/r, memory test (memtest86 bootable CD) and reported to Microsoft (of course there is no solution available) and of course the system restore can't locate the restore point.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: F21F29CB
BCP2: 00000000
BCP3: 82EC3789
BCP4: 00000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
Attached Files 102010-17222-01.dmp (156.1 KB, 72 views) Share Share this post on Digg Technorati Twitter
Operating System Windows 7
Computer Type Pentium ACPIx86-based PC
CPU Type and Speed Intel DuoCore
System Memory Type 4 GB
Video Card Type and Speed NVidia 7300
Computer Monitor View Sonic
Hard Drive Western Digital 2500 ATA
Optical Drives Optiarc DVD RW AD-7190A ATA
Network Adapter RealTeck PCIe GBe Family Controller
Anti-virus Software Norton 360
Computer Skill Level Average Ability
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 10-21-2010 #2 TorrentG Premier Member Enjoys Windows 7 Forums
Join Date May 2010 Posts 3,913 Re: System Crash now Blue Screen of death on Bootup Hello, welcome.

1) Uninstall the notorious Norton/Symantec in safe mode + networking using the tool found here:

AV Uninstallers

Reboot and install MSE to replace it.

2) Update your video card driver from

nvlddmkm nvlddmkm.sys Thu May 14 16:32:27 2009

3) Naivgate to C:WindowsSystem32drivers and delete the very old BANTExt.sys and PxHelp20.sys.

BANTExt BANTExt.sys Wed May 27 22:43:29 1998
PxHelp20 PxHelp20.sys Wed Jun 20 18:26:00 2007

4) Reboot and enjoy.

Hi there,

This is a relatively new BSOD issue, but has occurred several times. It most reliably occurs during Windows Update, but has also occurred just during ordinary browsing. Explorer has also stopped unexpectedly several times. Windows is reporting all drivers as up-to-date, the hard disk checker that runs following a crash is not reporting any disk errors, and no new software was installed just prior to the start of the problem. I've attached the most recent dump file. Thanks in advance for any advice you may have!

Josh Attached Files 091510-30732-01.dmp (268.3 KB, 87 views) Share Share this post on Digg 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 09-15-2010 #2 TorrentG Premier Member Enjoys Windows 7 Forums
Join Date May 2010 Posts 3,913 Re: BSOD during Win Update, or just whenever, on Gateway NV53 w/ Win 7 Hey there.

Yeah, this is definitely dealing with the hard drive. One moment about that.

Uninstall Daemon Tools in the normal method. Then use the installer/uninstaller found here to carefully remove the notorious sptd.sys from the system:

DuplexSecure - Downloads

Reboot and install PowerISO for disc emulation as it will never crash Windows and the emulation part of the software is free forever:

PowerISO - Create, Edit, Compress, Encrypt, Split, Mount, Extract ISO file, ISO/BIN converter, Virtual Drive


Update your video card driver:

atikmdag atikmdag.sys Thu Jul 02 13:45:07 2009

Drivers & Support | GAME.AMD.COM


Update your Broadcom ethernet (network) driver:

k57nd60a k57nd60a.sys Sat Jun 20 07:34:49 2009

To do so, visit your motherboard manufacturer's website to download/install.


Navigate to C:WindowsSystem32drivers and delete the following drivers which are too old for Windows 7:




Finally, open an elevated command prompt. Run the following command then press enter and follow the on-screen directions:

chkdsk /r

I have just built a new computer. And am getting BSODs. Here's my notes on them:

Errors Codes are as follows:

(I didn't write the codes down the first 2 times)

3rd BSOD (3/22/11):
*** STOP: 0x0000007F (0x0000000000000008, 0x0000000080050031, 0x00000000000006F8, 0xFFFFF80003888F72)

4th BSOD (3/25/11):
*** STOP: 0x0000007F (0x0000000000000008, 0x0000000080050031, 0x00000000000006F8, 0xFFFFF80003888F72)
*** dxgmms1.sys - address FFFFF880061B2360 base at FFFFF880061A2000, DateStamp 4ce799c1

5th BSOD (4/11/11):
*** STOP: 0x0000003B (0X00000000C0000005, 0xFFFFF96000093BFA, 0xFFFFF88008B0C210, 0x0000000000000000)
*** win32k.sys - Address FFFFF96000093BFA base at FFFFF96000010000, DateStamp 4d2415ea

6th BSOD (4/13/11):
An Attempt was made to write to read-only memory.
***STOP: 0x000000BE (0xFFFFF960002E22D8, 0x80900003ED6AC021, 0xFFFFF88002A64960, 0x000000000000000B)
*** win32k.sys - Address FFFFF96000103977 base at FFFFF96000040000, DateStamp 4d2415ea

7th BSOD (4/17/11):
***STOP: 0x0000000A (0xFFFFF6F44001A710, 0x0000000000000002, 0x0000000000000001, 0xFFFFF800038D58E9)
-this was the first time it did this (might be cause i enabled pagefile.sys before this crash?):
Collecting data for crash dump...
Initializing disk for crash dump...
Beginning dump of physical dump.
Dumping physical memory to disk: (1-100 count ticker ran)
Physical memory dump complete.

My system is as follows:

-CPU: AMD Phenom II X6 1090T Black Edition Thuban 3.2GHz Socket AM3 w/ ZALMAN 9500A-LED 92mm 2 Ball CPU Cooler
-RAM: 2X G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model F3-10666CL9D-8GBRL (16GB total)
-SSD: Crucial RealSSD C300 CTFDDAC064MAG-1G1 2.5" 64GB SATA III MLC Internal Solid State Drive (mainly have OS on here, and heavy programs like my DAW's)
-2x HDD: Western Digital Caviar Green WD20EARS 2TB SATA 3.0Gb/s Hard Drives (4gb total. In RAID 1 Mirror, 2 partitions: P: 195gb for programs and the rest S: 1.62gb for stoarage)
-VID CARD: ASUS EAH6870 DC/2DI2S/1GD5 Radeon HD 6870 1GB 256-bit GDDR5 PCI Express 2.1 x16 HDCP Ready CrossFireX Support Video Card with Eyefinity
-POWER SUPPLY: CORSAIR Enthusiast Series CMPSU-650TX 650W ATX12V / EPS12V SLI Ready CrossFire Ready 80 PLUS Certified Active PFC Compatible with Core i7 Power Supply
-DVD R/RW: Philips Internal Drive SPD2415BD DVD 20x ReWriter SPD2415BD/17 IDE
-OS: Windows 7 Ultimate 64 bit (MSDN version) on SSD
-FIREWIRE AUDIO PERIPHERAL: Presonas Firestudio Project Firewire recording interface
-DISPLAY: 2 monitors set up as follows: Samsung 226bw (s version) via DVI cable plugged into top DVI port of my video card. And a Gateway 700G 17 inch monitor Via DVI/HDMI adapter on bottom port of my video card via HDMI to DVI cable (i didnt have another DVI cable lying around).
-AUDIO RECEIVER: Optical Denon AVR-1801 DTS precision audio recivier (with 5.1 speaker setup)
-CASE: Antec Nine Hundred Black Steel ATX Mid Tower Computer Case
-MOUSE: Logitec MX518 usb wired
-KEYBOARD: emachines ps/2 wired

What I can say what i was doing when i got the blue screens:

-first two times all i know is i was in ventrilo (voice communication program) using a usb mic and one of those times i was playing Team Fortress 2
-3rd and 4th times i was recording with my Presonas Firestudio Project interface.
-5th crash i was away. i do'nt think i had anything major running and the screens were off and i was out of the room.
-6th crash i was playing DOD:S for about 30 mins Fire Studio project was off.
-7th crash playing TF2 for 5 mins at most. Fire Studio project was on and default audio device.

My system hiccups sometimes when it shouldn't with these specs. Such as when typing in a web browser sometimes ill be typing and the cursor will freeze for a second then all that I typed while it was frozen will all pop out at once. or when playing games like TF2 there will be lots of sound loops (repeats a split second sound clip 3 to 5 times then proceeds) and video hiccups. these might be because my internet is bad also?

So far i have done the following to try to fix this error:

-Disk Defrag on all drives
-Maleware (0 threats)
-IoBit secutry 360 (0 threats)
-AVG free (1 threat removed)
-CCleaner (both registry and disk clean)
-Driver Max and updated every Driver
-Windows Memory Diagnostics Tool with 0 problems.
-Prime95 (359 Torture Tests in 8 hours, 14 minutes with 0 errors and 0 warnings)

-Monitored all temps via CPUID's HW monitor. all temps look really nice and low even during stress tests.
CPU: 52 C (all cores during prime95 | ~40 C max during games and other normal high usage)
GPU: 81 C (during furmark, no more than 57 C during games)
HDDs: 25-26 C always
TMPIN0 34 C (after prime95 stress test)
TMPIN1 56 C (after prime95 stress test)
TMPIN2 57 C (after prime95 stress test)
Voltage 0 1.22 Volts [0x4C] (CPU VCORE)
Voltage 1 1.47 Volts [0x5C] (VIN1)
Voltage 2 3.36 Volts [0xD2] (+3.3V)
Voltage 3 5.03 Volts [0xBB] (+5V)
Voltage 4 12.42 Volts [0xC2] (+12V)
Voltage 5 -8.96 Volts [0x8C] (-12V)
Voltage 7 3.60 Volts [0x86] (+5V VCCH)
Voltage 8 3.25 Volts [0xCB] (VBAT)
Processor Watts: 62.40 W - 141.6 W
Vid Card Votls: VINO 1.2V

-AS SSD to see my drivers. got this:
AS SSD Benchmark 1.6.4067.34354
Name: C300-CTFDDAC064M SCSI Disk Device
Firmware: 0006
Controller: ahcix64s
Offset: 103424 K - OK
Size: 59.62 GB
Date: 3/26/2011 11:56:01 AM
AS SSD Benchmark 1.6.4067.34354
Name: AMD 1X2 Mirror/RAID1 SCSI Disk Device
Firmware: 1.10
Controller: ahcix64s
Offset: 132096 K - OK
Size: 1862.64 GB
Date: 3/26/2011 11:55:34 AM
AS SSD Benchmark 1.6.4067.34354
Name: AMD 1X2 Mirror/RAID1 SCSI Disk Device
Firmware: 1.10
Controller: ahcix64s
Offset: 204932096 K - OK
Size: 1862.64 GB
Date: 3/26/2011 11:55:03 AM
(C is my SSD with windows 7 on it and P and S are 2 partitions i set up on my RAID 1 Sata drives for Programs and Storage)

-Ran Windows Action Center and got this:
Driver software installation
Problem: Could not install driver software
Files that help describe the problem:
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

-I have ran a check Disk on all 3 partitions just after crash 4
C: (my SSD) 0 problems, 0 bad sectors.
S: (1.62TB Partition on my RAID 1 drives for storage) 0 problems, 0 bad sectors
P: (200gb partition on my RAID 1 drives for programs)
The type of the file system is NTFS.
Volume label is Programs.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
7680 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
9000 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
7680 file SDs/SIDs processed.
Security descriptor verification completed.
661 data files processed.
CHKDSK is verifying Usn Journal...
9177824 USN bytes processed.
Usn Journal verification completed.
The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

204799999 KB total disk space.
26162916 KB in 6907 files.
3300 KB in 662 indexes.
0 KB in bad sectors.
89295 KB in use by the system.
65536 KB occupied by the log file.
178544488 KB available on disk.

4096 bytes in each allocation unit.
51199999 total allocation units on disk.
44636122 allocation units available on disk.

I ran it with /F and it fixed the problem. but still got BSOD after this (5th crash)
I have run CHKDSK with /R again just in case and found no errors no bad sectors on all partitions.

-Calculated my power supply using Antec's power supply calculator:
System Type: Single Processor
Motherboard: High End - Desktop
CPU: AMD Phenom II X6 1090T 3200 MHz Thuban
CPU Utilization (TDP): 90% TDP
RAM: 4 Sticks DDR3 SDRAM
Video Card: AMD Radeon HD 6870
Video Type: Single Card
Green SATA: 2 HDDs
Flash SSD: 1 Drive
DVD-RW/DVD+RW Drive: 1 Drive
USB: 3 Devices
IEEE-1394 FireWire: 1 Device
Regular: 1 Fan 120mm; 1 Fan 250mm;
LED: 1 Fan 92mm; 3 Fans 120mm;
Keyboard and mouse: Yes
System Load: 90 %
Recommended Minimum
PSU Wattage: 429 Watts

Neweggs power supply calculator: 527 Watts recommend

I'm 123-221 watts over recommend supply. shouldn't be a problem there.

-Did some GPU stress tests using FurMark:
First i did a Burn-In test for 30 minutes @ full screen Resolution: 1680x1050 (FS) - AA:2 samples:
max temp 81, avg fps 25, max fan speed 47%

then some Benchmarks at 1 min each one right after the other with little time in between to cool off:
-BM 1 SCORE:1488 points (24 FPS, 60000 ms) FPS: min:22, max:31, avg:24 - OPTIONS: DynBkg
-BM 2 SCORE:943 points (15 FPS, 60000 ms) FPS: min:13, max:19, avg:15 - OPTIONS: DynCam
-BM 3 SCORE:1318 points (21 FPS, 60000 ms) FPS: min:22, max:23, avg:21 - OPTIONS: none (burn in)
-BM 4 SCORE:646 points (10 FPS, 60000 ms) FPS: min:11, max:12, avg:10 - OPTIONS: XB
-BM 5 SCORE:2179 points (36 FPS, 60000 ms) FPS: min:34, max:40, avg:36 - OPTIONS: FX

no crashes. temps look good.

Thoughts of possible suspects:
-Driver issues? (sound cards?)
-Bad Windows install? Maybe bad windows install discs? Discs were bought off eBay and looked questionable. I will get new ones from M$ and reformat soon.
-When I first installed windows Pagefile.sys and hibernate.sys were huge (~13gb each) so i disabled hibernate and disabled Pagefile.sys. -I enabled my PageFile.sys after 6th crash to see if that helped but crashed again but i got a crash dump 7th time.
-Monitor issues? maybe the cabling on the second monitor is messing with something (DVI to HDMI converter on vid card with a HDMI to DVI cable to monitor). I just didn't have another DVI lying around). 2 different resolutions, sizes and aspect ratios? Attached Thumbnails Attached Files (24.5 KB, 64 views) (1.03 MB, 67 views) rammon.txt (11.3 KB, 140 views) Share Share this post on Digg 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-18-2011 #2 cybercore Premier Member Enjoys Windows 7 Forums
Join Date Jul 2009 Posts 7,900 Re: BSOD's on new home build w/ full description
BugCheck A, {fffff6f44001a710, 2, 1, fffff800038d58e9}
Process: hl2.exe
Stack nt ... nt
Probably caused by : memory_corruption ( nt!MiUnmapPageInHyperSpaceWorker+49 )

RAM is the problem.

1. Load bios defaults, save and reboot. Make sure AMD Cool and Quiet is on. Also, should be no overclocking.
2. Uninstall AVG (replace with MSE for now) and uninstall Daemon Tools.
3. If still crashes, decrease the total amount of RAM by removing sticks.

PSU Wattage: 429 Watts Consider a more powerful unit.


Code: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:DMP41711-20623-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:websymbols* Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`0381f000 PsLoadedModuleList = 0xfffff800`03a64e90 Debug session time: Sun Apr 17 19:24:49.621 2011 (UTC - 4:00) System Uptime: 0 days 5:49:38.385 Loading Kernel Symbols ............................................................... ................................................................ .......................................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff6f44001a710, 2, 1, fffff800038d58e9} Probably caused by : memory_corruption ( nt!MiUnmapPageInHyperSpaceWorker+49 ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffff6f44001a710, 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: fffff800038d58e9, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003ad00e8 fffff6f44001a710 CURRENT_IRQL: 2 FAULTING_IP: nt!MiUnmapPageInHyperSpaceWorker+49 fffff800`038d58e9 48832100 and qword ptr [rcx],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: hl2.exe TRAP_FRAME: fffff8800ab948b0 -- (.trap 0xfffff8800ab948b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000000e rbx=0000000000000000 rcx=fffff6f44001a710 rdx=0000098000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800038d58e9 rsp=fffff8800ab94a40 rbp=fffff680002a5358 r8=0000000000000001 r9=0000000000000001 r10=0000000000000000 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!MiUnmapPageInHyperSpaceWorker+0x49: fffff800`038d58e9 48832100 and qword ptr [rcx],0 ds:fffff6f4`4001a710=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000389ebe9 to fffff8000389f640 STACK_TEXT: fffff880`0ab94768 fffff800`0389ebe9 : 00000000`0000000a fffff6f4`4001a710 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0ab94770 fffff800`0389d860 : 00000000`00000000 00000000`0e077990 00000000`0000014c fffff880`034d4000 : nt!KiBugCheckDispatch+0x69 fffff880`0ab948b0 fffff800`038d58e9 : 00000000`00001000 00000000`00000000 00000000`00000000 00000000`00000008 : nt!KiPageFault+0x260 fffff880`0ab94a40 fffff800`038f8a3d : fffff880`034e2000 fffff680`002a5358 00000000`00000001 00000000`00000000 : nt!MiUnmapPageInHyperSpaceWorker+0x49 fffff880`0ab94a80 fffff800`038ad09d : fffffa80`04fcae80 fffff880`0ab94b40 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xae5f fffff880`0ab94ac0 fffff800`0389d76e : 00000000`00000001 00000000`54a6b000 fffffa80`0cb76001 00000000`2b8be740 : nt!MmAccessFault+0xa7d fffff880`0ab94c20 00000000`68ea38ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`1241fd34 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x68ea38ea STACK_COMMAND: kb FOLLOWUP_IP: nt!MiUnmapPageInHyperSpaceWorker+49 fffff800`038d58e9 48832100 and qword ptr [rcx],0 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiUnmapPageInHyperSpaceWorker+49 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiUnmapPageInHyperSpaceWorker+49 BUCKET_ID: X64_0xA_nt!MiUnmapPageInHyperSpaceWorker+49 Followup: MachineOwner ---------


Code: start end module name fffff880`04910000 fffff880`0494e000 1394ohci 1394ohci.sys Sat Nov 20 05:44:56 2010 (4CE7A6A8) fffff880`01000000 fffff880`01057000 ACPI ACPI.sys Sat Nov 20 04:19:16 2010 (4CE79294) fffff880`03000000 fffff880`03089000 afd afd.sys Sat Nov 20 04:23:27 2010 (4CE7938F) fffff880`049a4000 fffff880`049ba000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`01400000 fffff880`0145a000 ahcix64s ahcix64s.sys Thu Sep 23 05:49:41 2010 (4C9B22B5) fffff880`049ea000 fffff880`049fe000 amdiox64 amdiox64.sys Thu Feb 18 10:17:53 2010 (4B7D5A21) fffff880`0419a000 fffff880`041af000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00df1000 fffff880`00dfc000 amdxata amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA) fffff880`09a71000 fffff880`09a7c000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`01075000 fffff880`0107e000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00dc7000 fffff880`00df1000 ataport ataport.SYS Sat Nov 20 04:19:15 2010 (4CE79293) fffff880`06517000 fffff880`06537000 AtihdW76 AtihdW76.sys Wed Nov 17 07:02:04 2010 (4CE3C43C) fffff880`04ca4000 fffff880`055d9000 atikmdag atikmdag.sys Tue Mar 22 22:12:23 2011 (4D895707) fffff880`04000000 fffff880`0404f000 atikmpag atikmpag.sys Tue Mar 22 21:44:22 2011 (4D895076) fffff880`01894000 fffff880`0189c000 AtiPcie AtiPcie.sys Tue May 05 11:00:22 2009 (4A005486) fffff880`01d52000 fffff880`01d86000 AVGIDSDriver AVGIDSDriver.Sys Tue Aug 03 18:24:45 2010 (4C58972D) fffff880`0188a000 fffff880`01894000 AVGIDSEH AVGIDSEH.Sys Mon Sep 13 18:46:38 2010 (4C8EA9CE) fffff880`07e71000 fffff880`07e7d000 AVGIDSFilter AVGIDSFilter.Sys Tue Aug 03 18:23:21 2010 (4C5896D9) fffff880`04124000 fffff880`04174000 avgldx64 avgldx64.sys Tue Dec 07 21:01:55 2010 (4CFEE713) fffff880`01db2000 fffff880`01dc1000 avgmfx64 avgmfx64.sys Mon Sep 06 20:49:14 2010 (4C858C0A) fffff880`01880000 fffff880`0188a000 avgrkx64 avgrkx64.sys Mon Sep 06 20:49:37 2010 (4C858C21) fffff880`030db000 fffff880`0313c000 avgtdia avgtdia.sys Fri Nov 12 06:08:42 2010 (4CDD203A) fffff880`01dca000 fffff880`01dd1000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`04113000 fffff880`04124000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`07f84000 fffff880`07fa2000 bowser bowser.sys Tue Feb 22 23:55:04 2011 (4D649328) fffff960`00670000 fffff960`00697000 cdd cdd.dll Sat Nov 20 07:55:34 2010 (4CE7C546) fffff880`01d88000 fffff880`01db2000 cdrom cdrom.sys Sat Nov 20 04:19:20 2010 (4CE79298) fffff880`00d07000 fffff880`00dc7000 CI CI.dll Sat Nov 20 08:12:36 2010 (4CE7C944) fffff880`01850000 fffff880`01880000 CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B) fffff880`00ca9000 fffff880`00d07000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01520000 fffff880`01592000 cng cng.sys Sat Nov 20 05:08:45 2010 (4CE79E2D) fffff880`04994000 fffff880`049a4000 CompositeBus CompositeBus.sys Sat Nov 20 05:33:17 2010 (4CE7A3ED) fffff880`07e7d000 fffff880`07e86000 cpuz135_x64 cpuz135_x64.sys Wed Jan 19 11:42:06 2011 (4D37145E) fffff880`0711f000 fffff880`0712d000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`04072000 fffff880`040f5000 csc csc.sys Sat Nov 20 04:27:12 2010 (4CE79470) fffff880`040f5000 fffff880`04113000 dfsc dfsc.sys Sat Nov 20 04:26:31 2010 (4CE79447) fffff880`01ddf000 fffff880`01dee000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`0183a000 fffff880`01850000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`06574000 fffff880`06596000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`07139000 fffff880`07142000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`0712d000 fffff880`07139000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`07142000 fffff880`07155000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`07113000 fffff880`0711f000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`04269000 fffff880`0435d000 dxgkrnl dxgkrnl.sys Sat Nov 20 04:50:50 2010 (4CE799FA) fffff880`0435d000 fffff880`043a3000 dxgmms1 dxgmms1.sys Sat Nov 20 04:49:53 2010 (4CE799C1) fffff880`00c4c000 fffff880`00c60000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`00c00000 fffff880`00c4c000 fltmgr fltmgr.sys Sat Nov 20 04:19:24 2010 (4CE7929C) fffff880`015a3000 fffff880`015ad000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01800000 fffff880`0183a000 fvevol fvevol.sys Sat Nov 20 04:24:06 2010 (4CE793B6) fffff880`01ad0000 fffff880`01b1a000 fwpkclnt fwpkclnt.sys Sat Nov 20 04:21:37 2010 (4CE79321) fffff880`0494e000 fffff880`0495b000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0) fffff800`03e09000 fffff800`03e52000 hal hal.dll Sat Nov 20 08:00:25 2010 (4CE7C669) fffff880`043a3000 fffff880`043c7000 HDAudBus HDAudBus.sys Sat Nov 20 05:43:42 2010 (4CE7A65E) fffff880`070d8000 fffff880`070f1000 HIDCLASS HIDCLASS.SYS Sat Nov 20 05:43:49 2010 (4CE7A665) fffff880`070f1000 fffff880`070f9080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`070ca000 fffff880`070d8000 hidusb hidusb.sys Sat Nov 20 05:43:49 2010 (4CE7A665) fffff880`07ebb000 fffff880`07f84000 HTTP HTTP.sys Sat Nov 20 04:24:30 2010 (4CE793CE) fffff880`01be7000 fffff880`01bf0000 hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E) fffff880`04967000 fffff880`04985000 i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00e5c000 fffff880`00e7d000 jraid jraid.sys Wed Nov 24 22:27:17 2010 (4CEDD795) fffff880`04985000 fffff880`04994000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff800`00bac000 fffff800`00bb6000 kdcom kdcom.dll Sat Feb 05 11:52:49 2011 (4D4D8061) fffff880`04218000 fffff880`0425b000 ks ks.sys Sat Nov 20 05:33:23 2010 (4CE7A3F3) fffff880`01505000 fffff880`01520000 ksecdd ksecdd.sys Sat Nov 20 04:21:15 2010 (4CE7930B) fffff880`017a7000 fffff880`017d2000 ksecpkg ksecpkg.sys Sat Nov 20 05:10:34 2010 (4CE79E9A) fffff880`06596000 fffff880`0659b200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`071a7000 fffff880`071bc000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`07163000 fffff880`07186000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c88000 fffff880`00c95000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`07155000 fffff880`07163000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`04890000 fffff880`0489f000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`070fa000 fffff880`07107000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00e7d000 fffff880`00e97000 mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299) fffff880`07fa2000 fffff880`07fba000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`07fba000 fffff880`07fe7000 mrxsmb mrxsmb.sys Tue Feb 22 23:56:22 2011 (4D649376) fffff880`07e00000 fffff880`07e4d000 mrxsmb10 mrxsmb10.sys Tue Feb 22 23:55:12 2011 (4D649330) fffff880`07e4d000 fffff880`07e71000 mrxsmb20 mrxsmb20.sys Tue Feb 22 23:55:12 2011 (4D649330) fffff880`01c50000 fffff880`01c5b000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`01057000 fffff880`01061000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`014a7000 fffff880`01505000 msrpc msrpc.sys Sat Nov 20 04:21:56 2010 (4CE79334) fffff880`031e8000 fffff880`031f3000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01bd5000 fffff880`01be7000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01654000 fffff880`01747000 ndis ndis.sys Sat Nov 20 04:23:30 2010 (4CE79392) fffff880`049de000 fffff880`049ea000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`071bc000 fffff880`071cf000 ndisuio ndisuio.sys Sat Nov 20 05:50:08 2010 (4CE7A7E0) fffff880`04800000 fffff880`0482f000 ndiswan ndiswan.sys Sat Nov 20 05:52:32 2010 (4CE7A870) fffff880`06502000 fffff880`06517000 NDProxy NDProxy.SYS Sat Nov 20 05:52:20 2010 (4CE7A864) fffff880`03181000 fffff880`03190000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`0313c000 fffff880`03181000 netbt netbt.sys Sat Nov 20 04:23:18 2010 (4CE79386) fffff880`01747000 fffff880`017a7000 NETIO NETIO.SYS Sat Nov 20 04:23:13 2010 (4CE79381) fffff880`01c5b000 fffff880`01c6c000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`031dc000 fffff880`031e8000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`0381f000 fffff800`03e09000 nt ntkrnlmp.exe Sat Nov 20 04:30:02 2010 (4CE7951A) fffff880`01243000 fffff880`013e6000 Ntfs Ntfs.sys Sat Nov 20 04:20:57 2010 (4CE792F9) fffff880`01dc1000 fffff880`01dca000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`04c7c000 fffff880`04c95000 nusb3hub nusb3hub.sys Thu Nov 18 20:34:24 2010 (4CE5D420) fffff880`043c7000 fffff880`043f8000 nusb3xhc nusb3xhc.sys Thu Feb 10 00:52:33 2011 (4D537D21) fffff880`0659c000 fffff880`065ef000 nwifi nwifi.sys Mon Jul 13 20:07:23 2009 (4A5BCC3B) fffff880`03092000 fffff880`030b8000 pacer pacer.sys Sat Nov 20 05:52:18 2010 (4CE7A862) fffff880`09a00000 fffff880`09a40280 PaeFireStudio PaeFireStudio.sys Fri Jan 21 00:43:08 2011 (4D391CEC) fffff880`09a41000 fffff880`09a49a80 PaeFireStudioAudio PaeFireStudioAudio.sys Fri Jan 21 00:41:38 2011 (4D391C92) fffff880`09a5b000 fffff880`09a63b00 PaeFireStudioMidi PaeFireStudioMidi.sys Fri Jan 21 00:41:33 2011 (4D391C8D) fffff880`00f98000 fffff880`00fad000 partmgr partmgr.sys Sat Nov 20 04:20:00 2010 (4CE792C0) fffff880`00f65000 fffff880`00f98000 pci pci.sys Sat Nov 20 04:19:11 2010 (4CE7928F) fffff880`0106e000 fffff880`01075000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`011ed000 fffff880`011fd000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`01592000 fffff880`015a3000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`06400000 fffff880`064a6000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`06537000 fffff880`06574000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c95000 fffff880`00ca9000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`049ba000 fffff880`049de000 rasl2tp rasl2tp.sys Sat Nov 20 05:52:34 2010 (4CE7A872) fffff880`0482f000 fffff880`0484a000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`0484a000 fffff880`0486b000 raspptp raspptp.sys Sat Nov 20 05:52:31 2010 (4CE7A86F) fffff880`0486b000 fffff880`04885000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`01c9b000 fffff880`01cec000 rdbss rdbss.sys Sat Nov 20 04:27:51 2010 (4CE79497) fffff880`04885000 fffff880`04890000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`01c35000 fffff880`01c3e000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`01c3e000 fffff880`01c47000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`01c47000 fffff880`01c50000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01b9b000 fffff880`01bd5000 rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E) fffff880`071cf000 fffff880`071e7000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04c00000 fffff880`04c6a000 Rt64win7 Rt64win7.sys Wed Feb 16 04:03:57 2011 (4D5B92FD) fffff880`06e2b000 fffff880`070c9980 RTKVHD64 RTKVHD64.sys Thu Feb 24 05:19:18 2011 (4D6630A6) fffff880`01b7e000 fffff880`01b9b000 sbp2port sbp2port.sys Sat Nov 20 04:19:21 2010 (4CE79299) fffff880`011be000 fffff880`011ed000 SCSIPORT SCSIPORT.SYS Sat Nov 20 05:34:01 2010 (4CE7A419) fffff880`07e86000 fffff880`07e91000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`0495b000 fffff880`04967000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`03190000 fffff880`031ad000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`01b76000 fffff880`01b7e000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`01081000 fffff880`011b5000 sptd sptd.sys Sun Mar 22 08:35:35 2009 (49C63097) fffff880`09b43000 fffff880`09bdb000 srv srv.sys Tue Feb 22 23:56:21 2011 (4D649375) fffff880`09ad9000 fffff880`09b43000 srv2 srv2.sys Tue Feb 22 23:56:00 2011 (4D649360) fffff880`041b8000 fffff880`041e9000 srvnet srvnet.sys Tue Feb 22 23:55:44 2011 (4D649350) fffff880`01cef000 fffff880`01d52000 storport storport.sys Sat Nov 20 05:35:02 2010 (4CE7A456) fffff880`09a4a000 fffff880`09a5ad00 STREAM STREAM.SYS Mon Jul 13 20:06:18 2009 (4A5BCBFA) fffff880`0489f000 fffff880`048a0480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`018cc000 fffff880`01ad0000 tcpip tcpip.sys Sat Nov 20 04:25:52 2010 (4CE79420) fffff880`07e91000 fffff880`07ea3000 tcpipreg tcpipreg.sys Sat Nov 20 05:51:48 2010 (4CE7A844) fffff880`01c8e000 fffff880`01c9b000 TDI TDI.SYS Sat Nov 20 04:22:06 2010 (4CE7933E) fffff880`01c6c000 fffff880`01c8e000 tdx tdx.sys Sat Nov 20 04:21:54 2010 (4CE79332) fffff880`031c8000 fffff880`031dc000 termdd termdd.sys Sat Nov 20 06:03:40 2010 (4CE7AB0C) fffff960`00450000 fffff960`0045a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`04174000 fffff880`0419a000 tunnel tunnel.sys Sat Nov 20 05:51:50 2010 (4CE7A846) fffff880`04c6a000 fffff880`04c7c000 umbus umbus.sys Sat Nov 20 05:44:37 2010 (4CE7A695) fffff880`043f8000 fffff880`043f9f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`048ff000 fffff880`04910000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04200000 fffff880`0420d000 usbfilter usbfilter.sys Tue Dec 22 03:26:22 2009 (4B3082AE) fffff880`064a8000 fffff880`06502000 usbhub usbhub.sys Sat Nov 20 05:44:30 2010 (4CE7A68E) fffff880`0420d000 fffff880`04218000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`048a9000 fffff880`048ff000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`07107000 fffff880`07113000 usbprint usbprint.sys Mon Jul 13 20:38:18 2009 (4A5BD37A) fffff880`01061000 fffff880`0106e000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`01dd1000 fffff880`01ddf000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`01c00000 fffff880`01c25000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`00fc2000 fffff880`00ffe000 vmbus vmbus.sys Sat Nov 20 04:57:29 2010 (4CE79B89) fffff880`01b1a000 fffff880`01b2a000 vmstorfl vmstorfl.sys Sat Nov 20 04:57:30 2010 (4CE79B8A) fffff880`00fad000 fffff880`00fc2000 volmgr volmgr.sys Sat Nov 20 04:19:28 2010 (4CE792A0) fffff880`00e00000 fffff880`00e5c000 volmgrx volmgrx.sys Sat Nov 20 04:20:43 2010 (4CE792EB) fffff880`01b2a000 fffff880`01b76000 volsnap volsnap.sys Sat Nov 20 04:20:08 2010 (4CE792C8) fffff880`030b8000 fffff880`030ce000 vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A) fffff880`031ad000 fffff880`031c8000 wanarp wanarp.sys Sat Nov 20 05:52:36 2010 (4CE7A874) fffff880`01c25000 fffff880`01c35000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00eb2000 fffff880`00f56000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f56000 fffff880`00f65000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`03089000 fffff880`03092000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`000b0000 fffff960`003c2000 win32k win32k.sys Wed Mar 02 22:51:40 2011 (4D6F104C) fffff880`00e97000 fffff880`00eab000 winhv winhv.sys Sat Nov 20 04:20:02 2010 (4CE792C2) fffff880`041af000 fffff880`041b8000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`011b5000 fffff880`011be000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`07186000 fffff880`071a7000 WudfPf WudfPf.sys Sat Nov 20 05:42:44 2010 (4CE7A624) Unloaded modules: fffff880`09a7c000 fffff880`09abd000 Unknown_Module_fffff880`09a7c000 Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00041000 fffff880`09ac6000 fffff880`09ad7000 STREAM.SYS Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00011000 fffff880`09abd000 fffff880`09ac6000 PaeFireStudi Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00009000 fffff880`09bdb000 fffff880`09be4000 PaeFireStudi Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00009000 fffff880`09a00000 fffff880`09a71000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00071000 fffff880`01d52000 fffff880`01d60000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000E000 fffff880`01d60000 fffff880`01d6c000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000C000 fffff880`01d6c000 fffff880`01d75000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00009000 fffff880`01d75000 fffff880`01d88000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00013000

The other day, I turned on my computer to find this error:


I rebooted the computer. As it was starting up, it ran chkdsk (I hadn't scheduled it to run). It found and corrected several errors. The error has not gone away and I'm at a lost as to how to fix it.
The Desktop Window Manager Session Manager service is started.

The computer is an HP dv8t Laptop running 64-bit Windows 7 Ultimate. Everything was fine until yesterday. The only thing that changed recently was the MS updates that went out on Tuesday, but the computer was rebooted at least twice after that without any problems.

[Windows 7 64-bit]

I have a rather odd problem. Whenever I run Windows Live Mail (my default email program) on my desktop for the first time in a session (by session I mean the period between 2 consecutive reboots), it usually runs OK. However, when I run it a second time in a session, I get the following notification in the taskbar:

Windows Live Mail: wlmail.exe - Corrupt File
The file or directory C:Temp FilesTemporary Internet FilesContent.IE5xxxxxxxx is corrupt and unreadable. Please run Chkdsk utility.
[Note 1: xxxxxxxx is a random alphanumerc value, like DAB167TE etc.
Note 2: The path that its pointing to is my chosen path for storing temp files in IE8.]

On the next reboot, the Chkdsk runs automatically and invariably finds no errors.
I have had this error for a couple months now, didn't happen before that. I am guessing here but I think the message started appearing soon after I installed Webroot Spy Sweeper on the PC (I previously had Spy Sweeper w/AntiVirus which was uninstalled when the subscription ran out and replaced by Spy Sweeper). Again, that's just a guess, its hard to find cause and effect.

I have already "Repaired" my installation of Windows Live Essentials; it hasn't helped. Does someone have any insight into why I get this redundant message and how to fix the issue?

Build 42 available at Raxco Windows Product Support - Service Packs And Upgrades or use the integrated updater.

From the Whatsnew file:

"What's new in PerfectDisk build 7.00.042
Clarified some of the boot-time defragmentation messages.
Changed PerfectDisk's boot time defragmentation code to be consistent with changes made to check disk (chkdsk.exe) in Windows XP, Service Pack 2.
Corrected a bug in the boot time defragmentation. PerfectDisk records the current time on shutdown and compares it to the system time at reboot. On Windows XP, Service Pack 2, the system time at reboot can be earlier then the system time at shutdown. Raxco was unaware that Microsoft was able to travel back in time.
Some code segments were changed to be consistent with PerfectDisk Live. "


I'm working on a used Gateway M-Series laptop, model number: W650I. The laptop runs fine, but whenever I try to boot into Windows with the hard drive that came with it, I get a BSOD! It essentially reads:

A problem has been detected and Windows has been shut down to prevent damage to your computer. Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /f to check for hard drive corruption and then restart your computer. Technical info: STOP: 0x0000007B, 0xFFFFF880009A9928, 0xFFFFFFFFC00000034

Thinking that it could be an issue with the drive, I took it out and put it a drive from a Linux machine, and the Gateway booted up normally. I also took the Gateway drive and put it in the Linux box, and the computer gave me an endless reboot cycle of "Windows is loading files." So the Linux drive works in the Gateway and in its own computer, but the Gateway drive works in neither. Simple, right? Just fix the drive; problem solved. Not so fast.

Now I know for a fact that the prior owner of the Gateway infected the machine with all kinds of malware, and a lot of it was never removed. Since Windows was compromised with so many viruses and other nasties, I simply decided to start with a clean slate. So I formatted and reinstalled Windows 7 on the drive. Knowing that formatting doesn't remove all malware, I also hooked the drive up to other computers and ran:

1.) An Microsoft Security Essentials scan. Results were clean.
2.) An AVG Internet Security version 9 scan, twice, and results were clean.
3.) Kaspersky Virus Removal Tool, which took over two hours. Results were clean.

I ran CHKDSK twice on the drive, once from another installation of Windows, and it did report that it had repaired some bad sectors. I used EASUS Partition Manager to run a surface test on the drive, and it came back with a couple of bad sectors. So it would appear that the drive may have been damaged by too many incorrect shutdowns or malware, and wouldn't work at all.

Not true. Normally I would have thought that the drive was toast, since it didn't boot up into either computer. However, I hooked it up to my own custom built computer. . . and it worked! Windows booted normally, installed updates normally, ran its programs correctly, all without error messages. So why isn't it working in the Gateway laptop?

I thought it might have something to do with the Gateway's RAM. So I ran Windows Memory Diagnostic twice, and it did not report any errors. The BIOS recognized all the RAM on its summary page, and emitted no error beep when the system started. The Linux drive also booted up with no problem. Just to be sure, I checked the RAM, each stick in a different module, while booting up from the Gateway hard drive, but still encountered the BSOD. The RAM looks fine, and the contacts were not dirty or damaged. I reseated the memory, just to be sure nothing was loose, but to no avail. Therefore I think the RAM is exonerated as a possible culprit.

Windows also would not respond to any of the F8 commands. If I told it to boot into Safe Mode or Last Known Good Config, it would still bluescreen. I ran startup repair on the drive after one such failed attempt, and I did get an error message explaining why Startup Repair couldn't fix the drive, but I don't remember what it was.

Since the Gateway drive is from Western Digital, I downloaded and ran the WD Data Lifeguard Diagnostic program. The drive passed the SMART test and the WD quick test without issue. I was going to run the extended test, but after I saw the estimated time sitting at 19 hours after running it for 120+ minutes, I decided to stop the test. For what it's worth, it didn't report any errors during the first two and a half hours I was running it.

I'm wondering if the BIOS on the Gateway is infected somehow. Sure, I can access it without issue, but maybe it has some sort of malware in it that could be interacting with the Windows 7 bootup sequence, which is causing the BSOD. Remember, the Linux drive booted fine on it, because Linux wouldn't get infected with a Windows BIOS virus. I could try resetting the motherboard, or flashing the BIOS, but since I can't actually boot into Windows, I'm not sure how I'd do that.

The one thing I don't understand is that the hard drive works in my computer, but bluescreens in the Gateway. I've checked to ensure that the drive is properly attached and secured in the laptop before I boot the computer. In fact, Windows gets as far as the startup splash graphic before the BSOD hits, so I don't think it is a bad or faulty connection with the laptop's SATA port.

Maybe there is some malware in the drive that is eluding my AV scans? Is there a really thorough virus checker that will scour deep down into the sectors, where a rootkit or something could be hiding? And can anyone recommend any effective third party disk checkup and repair utilities? Maybe the built in Windows features aren't telling me the whole story.

I've exhausted all of my tricks, so anyone else here is welcome to try their magic and find a solution to this Gateway dilemma!

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.
CPU: AMD 1800+
Mem: 256 MB
PSU: ~400 W

Any thoughts appreciated.

This afternoon when I was rebooting from Windows 8 to Windows 7 in my desktop dual boot, chkdsk wanted to check my Windows 8 boot disk. I let it run, and it finished quickly without finding anything amiss. But it did remind me that I had not run SeaTools for Windows from Seagate in quite a while.

I fired up SeaTools, and ran the short diagnostic self test on the three 1TB drives in my desktop. One of them failed the DST. I ran the Fix All - Fast tool, and it also failed about half-way through. My next to last resort when it comes to disk problems is chkdsk - slow but powerful. My last resort for disk problems is SpinRite from Gibson Research - more powerful still, but much slower.

That particular drive has 7 partitions. The problem area turned out to be the last partition (wouldn't you know it?). The problem partition is 127GB, and chkdsk ran on it for over 6 hours, but it succeeded. After chkdsk finished, I ran SeaTools again, and the drive passed. I make drive images when changes in partition contents occur, so I'll keep using this disk without worries.

Successful chkdsk.PNG

OK, it seems my W8 system is possibly in a bit of trouble...

I ran CHKDSK on my C: drive, and at the end saw this :

Errors detected in the Boot File.
Windows has checked the file system and found problems.
Please run chkdsk /scan to find the problems and queue them for repair.

Hmm, system boots just fine and I appear to have NO errors. I am on an SSD and it is quite possible that I did 'mess up' something in the boot record when I migrated a large partition that was bootable into the much smaller SSD.


At the end it asked to cue it up to check the disk on boot. I allowed it. It ran and then started a troubleshooter, which ran PC Diagnostics and then a message that it could take up to 1 hour to fix. Almost instantly the system rebooted, AND ran chkdsk again. Off it went to the troubleshooter... and it just continued in this loop.

OK, I did break the loop and got an screen with options... one was to go into W8 directly, and again, the loop started up again. Argh... broke into it and I had other options, REFRESH, RESTORE, or shutdown. OK, Shutdown.... nope, power on started the loop again...

UGLY... so I did a REFRESH basically losing installed non-MS store programs. No problem, I've got an IMAGE.

When it was restored, it was OK on CHKDSK... and the few Store apps (Live Tiles) that didn't run before did... good.

I restored my image, and poof, CHKDSK shows the error again. However, this system has been booting for months with no problem and I assume the 'corruption' was present, and will now too with the 'problem'. I just can't run CHKDSK on it?

CAN NOT find anything about this on the web?

Thinking the MBR could be 'damaged'? There are programs to fix that and the boot record, but I'm not about to try this as it could break me?

HELP and SUGGESTIONS appreciated...

Windows 8 remember. Ran CHKNTFS and the FS is OK and the disk is NOT dirty....

I ran a program to check the MBR (MBRCheck.exe), it seems OK?

.C: --> .PhysicalDrive0 at offset 0x00000000`00100000 (NTFS)
.D: --> .PhysicalDrive2 at offset 0x00000000`04700000 (NTFS)
.K: --> .PhysicalDrive2 at offset 0x0000002e`aae00000 (NTFS)
.L: --> .PhysicalDrive1 at offset 0x00000000`00100000 (NTFS)
.X: --> .PhysicalDrive2 at offset 0x00000003`c4700000 (NTFS)

PhysicalDrive0 Model Number: CorsairCSSD-F115GB2-A, Rev: 2.4
PhysicalDrive2 Model Number: WDCWD7501AALS-75J7B0, Rev: 05.00K05
PhysicalDrive1 Model Number: ST31000528AS, Rev: CC34

Size Device Name MBR Status
107 GB .PhysicalDrive0 Windows 7 MBR code detected
SHA1: 4379A3D43019B46FA357F7DD6A53B45A3CA8FB79
698 GB .PhysicalDrive2 Windows 7 MBR code detected
SHA1: 4379A3D43019B46FA357F7DD6A53B45A3CA8FB79
931 GB .PhysicalDrive1 Windows 98 MBR code detected
SHA1: 48F01D7E76A0F3C038D08611E3FDC0EE4EF9FD3E

C: is the SSD that has the problem.

Page 1 of 3.
Results 1...20 of 46