Code: Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data--> Validation Code: 0 Cached Online Validation Code: N/A, hr = 0xc004f012 Windows Product Key: *****-*****-3H233-PTWTJ-YRYRV Windows Product Key Hash: iplHJdWi/M942hdv/dPc8+K1E4Y= Windows Product ID: 00346-339-0000007-85971 Windows Product ID Type: 5 Windows License Type: Retail Windows OS version: 6.1.7600.2.00010300.0.0.002 ID: {464F4DD3-ACCA-41A1-93BD-E39B31BF2D96}(1) Is Admin: Yes TestCab: 0x0 LegitcheckControl ActiveX: N/A, hr = 0x80070002 Signed By: N/A, hr = 0x80070002 Product Name: Windows 7 Home Basic Architecture: 0x00000000 Build lab: 7600.win7_rtm.090713-1255 TTS Error: Validation Diagnostic: Resolution Status: N/A Vista WgaER Data--> ThreatID(s): N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 Windows XP Notifications Data--> Cached Result: N/A, hr = 0x80070002 File Exists: No Version: N/A, hr = 0x80070002 WgaTray.exe Signed By: N/A, hr = 0x80070002 WgaLogon.dll Signed By: N/A, hr = 0x80070002 OGA Notifications Data--> Cached Result: N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 OGAExec.exe Signed By: N/A, hr = 0x80070002 OGAAddin.dll Signed By: N/A, hr = 0x80070002 OGA Data--> Office Status: 109 N/A OGA Version: N/A, 0x80070002 Signed By: N/A, hr = 0x80070002 Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3 Browser Data--> Proxy settings: N/A User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32) Default Browser: C:\Program Files\Mozilla Firefox\firefox.exe Download signed ActiveX controls: Prompt Download unsigned ActiveX controls: Disabled Run ActiveX controls and plug-ins: Allowed Initialize and script ActiveX controls not marked as safe: Disabled Allow scripting of Internet Explorer Webbrowser control: Disabled Active scripting: Allowed Script ActiveX controls marked as safe for scripting: Allowed File Scan Data--> File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003] File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003] File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003] File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003] Other data--> Office Details: <GenuineResults><MachineData><UGUID>{464F4DD3-ACCA-41A1-93BD-E39B31BF2D96}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.002</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-YRYRV</PKey><PID>00346-339-0000007-85971</PID><PIDType>5</PIDType><SID>S-1-5-21-366893658-4104581418-3215386934</SID><SYSTEM><Manufacturer>TOSHIBA</Manufacturer><Model>Satellite L510</Model></SYSTEM><BIOS><Manufacturer>INSYDE</Manufacturer><Version>1.50</Version><SMBIOSVersion major="2" minor="4"/><Date>20091215000000.000000+000</Date></BIOS><HWID>BDBB3607018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>SE Asia Standard Time(GMT+07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>TOSINV</OEMID><OEMTableID>TOSINV00</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> Spsys.log Content: 0x80070002 Licensing Data--> Software licensing service version: 6.1.7600.16385 Name: Windows(R) 7, HomeBasic edition Description: Windows Operating System - Windows(R) 7, RETAIL channel Activation ID: b1184982-a958-4643-8e66-445fa0f92832 Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f Extended PID: 00346-00170-339-000000-00-1033-7600.0000-0602014 Installation ID: 004880604hemo post t623136765412760711244325166030101760133324143 Processor Certificate URL I took these links out not sure if I am supposed to but I thought it said no links. Machine Certificate URL: Use License URL: Product Key Certificate URL: Partial Product Key: YRYRV License Status: Initial grace period Time remaining: 41220 minute(s) (28 day(s)) Remaining Windows rearm count: 3 Trusted time: 3/3/2014 10:18:18 PM Windows Activation Technologies--> HrOffline: 0x00000000 HrOnline: N/A HealthStatus: 0x0000000000000000 Event Time Stamp: N/A ActiveX: Not Registered - 0x80040154 Admin Service: Not Registered - 0x80040154 HealthStatus Bitmask Output: HWID Data--> HWID Hash Current: MgAAAAEAAQABAAIAAAACAAAAAwABAAEAJJSEy3oYMAaCOqT62iR8itRfJWtC3AxoRso= OEM Activation 1.0 Data--> N/A OEM Activation 2.0 Data--> BIOS valid for OA 2.0: no, invalid SLIC table Windows marker version: N/A OEMID and OEMTableID Consistent: N/A BIOS Information: ACPI Table Name OEMID Value OEMTableID Value APIC TOSINV TOSINV00 FACP TOSINV TOSINV00 HPET TOSINV TOSINV00 BOOT TOSINV TOSINV00 MCFG TOSINV TOSINV00 ASF! TOSINV TOSINV00 SLIC TOSINV TOSINV00 SSDT PmRef CpuPm Hi that is my MGADiag Tool report, hope I posted it won't (the attachment window won't load). My computer is kind of a long story and I am not good at this stuff. I am in my 50s and digitally challenged. Just an fyi, as I messed up my system a few months ago and here is the story (I am sorry for my ignorance btw, but I am really pretty new to this which I will explain as I go along). I have a Toshbia Sattilite 32 bit which I bought here in Bangkok in 2009. It came with windows7 ultimate installed and a bunch of products bundled (PS, Word, I tunes...etc). I am an artist who just started using computers in maybe 2000 or so. I always bought macs before this but both of my last 2 of them had bad motherboards after 2 years, so I decieded to switch (I was using a PC at work and it seemed almost as good). So I bought this machine and when I bought it I didn't ever update it or anything because, well basicly I didn't know. I had an internet problem with my router about 8 months ago and a tech came by my house and explained to me that I didn't have any anti virus or other security and I never ran an update. So I did an update. The first time I got the conterfiet screen I found Windows7 on digital river and installed it as I didn't have a product key and my stickers are all but rubbed off, plus I live in Thailand and we have termites here who ate my reciepts a while ago. I think, I used removewat to verify it (this was months ago now and I did a lot of things to fix it since then). It also probably used something when they installed the w7 in the first place which I don't know what it was. I didn't lose any programs until later, it seemed to work well for a few months. Then I started getting the occasional BSOD which I had no idea what it was. I went on some windows forums and learned a bit about PCs and how to analize the files ( or have people read my files for me anyway). I tried a bunch of different fixes and it just got worse with time. I figuared I would try reinstalling it and used wat fix and the loader. I am not totally sure if I removed the removewat program first, I thought I did but it is kind of a blur now. Again it worked for a while ( a week or so) but this time it started BSODing a lot more and faster. It also would never make a shodw copy to make a restore point, I actually have no idea if it ever did. I tried another custom install and it got interuppted by a power outage and it wouldn't rollback. So I lost my bundled programs although I still have them on the d drive if anyone knows how to fix them. I did a clean install and it behaved the same.... I saw in the Toshbia forum i should update my bios so I did. Eventually I couldn't start it. It would just bluescreen even during repair or from installing again 4xs. I tried to survive on using my GFs tablet and looking for solutions. I called Toshbia and they were the ones who confirmed that the store (now out of business btw) sold me a no os computer and had another store put windows on it (I had read on a forum for toshbia that updating the bios could make it look counterfeit, so I was never sure at first). So it sat a month (I also was having an art exhibition in Tokyo and needed to paint and photograph stuff, damned I miss PS!) and I didn't try to do anything, in fact started looking for a new used one on craigslist. Then one day I saw someone selling W7 home edition for 25$ (or so in Thai Baht 800) and I bought and installed it. It worked.... kind of and it validated which I think was good. I am using it to type this but it may BSOD anytime or the browser might crash (2xs already did). I see in my report above I have 4 wat issues. I admit I don't really know what I am doing so could you please give me simpleton instructions if you have any? I am not even sure if I am posting in a good place for this. But the only other place that looked right was modding the BIOS. Edited I also see there is a problem because a no os has no SLIC (which is something I don't understand at all, was looking at that thread before I posted here). Thanks in advance and have a nice day.
got system to start and (but it just bsod' again) I'm going to try to put the nirsoft file on here if i can. it might just be copy and paste i am affraid as i don't have the program to upload it anymore. It was abstracrion layer files and ntkma? mostly i think it, it is asking me if i want to scan the hdd tk fix it and i tried but just doing that made it bs again.
Whew, sorry to be a thread hog like this. Code: 3/4/2014 12:43:15 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x1d98e205 0x00000002 0x00000001 0x82a70b41 ntkrnlpa.exe ntkrnlpa.exe+467eb NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+467eb ntkrnlpa.exe+67b41 C:\Windows\Minidump\030414-19344-01.dmp 2 15 7600 145,856 3/4/2014 12:44:18 PM 030414-18626-01.dmp 3/4/2014 12:40:48 PM NTFS_FILE_SYSTEM 0x00000024 0x001904fb 0x8a9a05cc 0x8a9a01b0 0x8884c2cd Ntfs.sys Ntfs.sys+112cd NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+dcd10 Ntfs.sys+14221 Ntfs.sys+18bc3 ntkrnlpa.exe+3c4bc C:\Windows\Minidump\030414-18626-01.dmp 2 15 7600 145,856 3/4/2014 12:42:00 PM 030414-16738-01.dmp 3/4/2014 12:33:10 PM ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY 0x000000fc 0xa91dfbf0 0x4ac6d963 0xa91dfb44 0x00000002 ntkrnlpa.exe ntkrnlpa.exe+858e3 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+858e3 ntkrnlpa.exe+465f8 win32k.sys+cdfb7 C:\Windows\Minidump\030414-16738-01.dmp 2 15 7600 145,856 3/4/2014 12:34:15 PM 030414-16224-01.dmp 3/4/2014 12:17:53 PM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x82c7de7f 0x9359962c 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+241e7f NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+241e7f ntkrnlpa.exe+2216f4 ntkrnlpa.exe+68f60 ntkrnlpa.exe+246f72 C:\Windows\Minidump\030414-16224-01.dmp 2 15 7600 145,856 3/4/2014 12:19:48 PM 030414-22167-02.dmp 3/4/2014 11:49:11 AM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 0x0000000d 0x00000000 0x00000000 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+46f2b NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+46f2b ntkrnlpa.exe+3d95c ntkrnlpa.exe+22fd40 ntkrnlpa.exe+22fc78 C:\Windows\Minidump\030414-22167-02.dmp 2 15 7600 145,808 3/4/2014 11:57:32 AM 030414-23415-01.dmp 3/4/2014 11:45:32 AM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x82c24cd0 0x922b19f4 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+220cd0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+220cd0 ntkrnlpa.exe+23dffb ntkrnlpa.exe+23cc30 ntkrnlpa.exe+222935 C:\Windows\Minidump\030414-23415-01.dmp 2 15 7600 145,856 3/4/2014 11:46:43 AM 030414-23618-01.dmp 3/4/2014 11:43:47 AM NTFS_FILE_SYSTEM 0x00000024 0x001904fb 0x939f387c 0x939f3460 0x68a2b28e Ntfs.sys Ntfs.sys+14221 NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+dcd10 Ntfs.sys+14221 Ntfs.sys+ab51b ntkrnlpa.exe+3c4bc C:\Windows\Minidump\030414-23618-01.dmp 2 15 7600 145,856 3/4/2014 11:44:51 AM 030414-26956-01.dmp 3/4/2014 11:03:36 AM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x82c8be7e 0x938bfae4 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+288e7e NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+288e7e ntkrnlpa.exe+288fe8 ntkrnlpa.exe+288de2 ntkrnlpa.exe+b4463 C:\Windows\Minidump\030414-26956-01.dmp 2 15 7600 145,808 3/4/2014 11:43:20 AM 030414-22105-01.dmp 3/4/2014 10:42:20 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x059de1af 0x00000002 0x00000001 0x82aaea43 ntkrnlpa.exe ntkrnlpa.exe+467eb NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+467eb ntkrnlpa.exe+93a43 ntkrnlpa.exe+7505d ntkrnlpa.exe+6d567 C:\Windows\Minidump\030414-22105-01.dmp 2 15 7600 145,808 3/4/2014 11:03:30 AM 030414-26270-01.dmp 3/4/2014 10:13:26 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 0xbf2f8874 0x00000001 0x82aac857 0x00000002 ntkrnlpa.exe ntkrnlpa.exe+858e3 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+858e3 ntkrnlpa.exe+465f8 ntkrnlpa.exe+71857 ntkrnlpa.exe+221918 C:\Windows\Minidump\030414-26270-01.dmp 2 15 7600 145,856 3/4/2014 10:14:31 AM 030414-22698-01.dmp 3/4/2014 10:11:40 AM MEMORY_MANAGEMENT 0x0000001a 0x00041287 0x00000000 0x00000000 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+858e3 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+858e3 ntkrnlpa.exe+465f8 ntkrnlpa.exe+98541 ntkrnlpa.exe+90979 C:\Windows\Minidump\030414-22698-01.dmp 2 15 7600 145,808 3/4/2014 10:12:38 AM 030414-13556-01.dmp 3/4/2014 10:09:49 AM NTFS_FILE_SYSTEM 0x00000024 0x001904fb 0xab5774f0 0xab5770d0 0x6881c73d Ntfs.sys Ntfs.sys+14221 NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+dcd10 Ntfs.sys+14221 Ntfs.sys+1946d ntkrnlpa.exe+7010e C:\Windows\Minidump\030414-13556-01.dmp 2 15 7600 145,856 wheew! 3/4/2014 10:10:30 AM 030414-13774-01.dmp 3/4/2014 10:08:28 AM 0x00000124 0x00000000 0x863391e4 0xb2000040 0x00000800 halmacpi.dll halmacpi.dll+ef3f Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+dcd10 halmacpi.dll+ef3f ntkrnlpa.exe+cef04 halmacpi.dll+f1f1 C:\Windows\Minidump\030414-13774-01.dmp 2 15 7600 145,856 Thank you for editing that Tito. I see how to do that now. I reinstalled again so it should be a little bit more stable.... hopefully. I also have the Toshbia discs being sent to me so maybe I will be able to do an install with the og drivers. But I still have the question if my bios has been changed or if it would have gone back to normal. Last thing when I ran a startup repair before I loaded this install it made a recovered file in that windows is putting on a black page with win7 as an option to start from (which starts every time the cmputer does and it is almost the same size as the OS). It is also located on the D drive but the system is on the C. I am kind of confused about how to get rid of it and what that is. I wonder if it also might be causing problems, it is still having boot issues and bluesecreening. Anyone know what comes on Toshbia discs? Will it get to root drivers in the regisesty if they are corrupted? Will it wipe my D drive? Very last question (sorry) if no os machines come with out whatever SLIC could that be an issue?
The loader doesn't adjust the BIOS at all. After you reinstalled Windows the loader would of also got uninstalled. That's why your MGADiag report shows no SLIC table or OEM key. You didn't use a registry cleaner or any kind of PC tuner software, did you? Sometimes software can cause that error, but often it's due to a hard drive or memory issue. IRQL_NOT_LESS_OR_EQUAL = Normally a driver issue NTFS_FILE_SYSTEM = Disk corruption or memory issue MEMORY_MANAGEMENT = Mismatched memory or if ones slower than the other can cause this Download HD Tune. Does that health tab mention anything bad? And what if you run a full error scan with it? The errors you posted are general errors, they don't really show much. If you click on them one by one then it'll tell you what exe's or drivers were running.
hmm maybe my nirsoft thing isn't the same as the one you posted, will have to check. It doesn't seem to have drivers listed just bug checks and stuff like that, these are the same messages as I was getting but the NTFS_FILE_SYSTEM = Disk corruption or memory issue MEMORY_MANAGEMENT are new ones. I was getting a winsys32 as a problem too. Hal as well. Don't have those dumps anymore. I do think a person on the toshbia board had me run a registry cleaner I cant get in to my yahoo mail for some reason right now, will check that on the tablet in the morning. I can tell you which one, he was supposed to be an IT engineer but who knows? He also said my dumps looked like I was running 64 bit on my 32 bit system but I used the 32 bit Digital river dl. I was running the hd tune but it is taking too long at the moment, will have to do in the morn. 1/4 of the way through it said 0.1% bad sectors (2 red boxes) I will post results from that and chkdsk i ran earlier today. I didn't see those results yet either. I am 12 hours ahead of e.s.t. here in thailand so I have to sleep, is 12:30. will post things tomorrow if I can get it to boot. Thanks! oh and is it okay to do that in this thread or should I start a new post somewhere else? This isn't about the loader any more. I think the registry has some corruption because I had some infections when this all started, I thought they were removed..... Have been having issues for more than 6 months (with a month off in between.
okay here we go 1st things 1st, then some histories, the present issues: screen views of hd tune View attachment 27350 pretty View attachment 27351 looks okay? View attachment 27349 not sure it is needed. (firefox crashed #1 been doing that but less than chrome or IE which is why I am using it, glad this autosaves but should have a save button that we could use, just a suggestion ) CHKDSK results if I can remember how to do the code box lol Code: Log Name: Application Source: Microsoft-Windows-Wininit Date: 3/4/2014 7:28:57 AM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: alan-PC Description: Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 120832 file records processed. File verification completed. 122 large file records processed. 0 bad file records processed. 0 EA records processed. 104 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 166968 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 120832 file SDs/SIDs processed. Cleaning up 911 unused index entries from index $SII of file 0x9. Cleaning up 911 unused index entries from index $SDH of file 0x9. Cleaning up 911 unused security descriptors. Security descriptor verification completed. 23069 data files processed. CHKDSK is verifying Usn Journal... 34693928 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... Read failure with status 0xc0000185 at offset 0x19a108000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19a109000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x19a32a000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19a4ca000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19a4d0000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x19a581000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19a58a000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x19aa0b000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19aa0b000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x19b5ec000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19b5f3000 for 0x1000 bytes. Windows replaced bad clusters in file 63175 of name \Windows.old\Users\alan\Dropbox\SANY0004.AVI. 120816 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 35406746 free clusters processed. Free space verification is complete. Adding 6 bad clusters to the Bad Clusters File. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows has made corrections to the file system. 165474303 KB total disk space. 23554644 KB in 97134 files. 65868 KB in 23070 indexes. 24 KB in bad sectors. 226783 KB in use by the system. 65536 KB occupied by the log file. 141626984 KB available on disk. 4096 bytes in each allocation unit. 41368575 total allocation units on disk. 35406746 allocation units available on disk. Internal Info: 00 d8 01 00 98 d5 01 00 7b 8c 03 00 00 00 00 00 ........{....... 13 01 00 00 68 00 00 00 00 00 00 00 00 00 00 00 ....h........... f0 8a 28 00 50 01 27 00 f0 17 27 00 00 00 27 00 ..(.P.'...'...'. Windows has finished checking your disk. Please wait while your computer restarts. Event Xml: <Event xmlns="//schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-03-04T15:28:57.000000000Z" /> <EventRecordID>377</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>alan-PC</Computer> <Security /> </System> <EventData> <Data> Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 120832 file records processed. File verification completed. 122 large file records processed. 0 bad file records processed. 0 EA records processed. 104 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 166968 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 120832 file SDs/SIDs processed. Cleaning up 911 unused index entries from index $SII of file 0x9. Cleaning up 911 unused index entries from index $SDH of file 0x9. Cleaning up 911 unused security descriptors. Security descriptor verification completed. 23069 data files processed. CHKDSK is verifying Usn Journal... 34693928 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... Read failure with status 0xc0000185 at offset 0x19a108000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19a109000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x19a32a000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19a4ca000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19a4d0000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x19a581000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19a58a000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x19aa0b000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19aa0b000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x19b5ec000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x19b5f3000 for 0x1000 bytes. Windows replaced bad clusters in file 63175 of name \Windows.old\Users\alan\Dropbox\SANY0004.AVI. 120816 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 35406746 free clusters processed. Free space verification is complete. Adding 6 bad clusters to the Bad Clusters File. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows has made corrections to the file system. 165474303 KB total disk space. 23554644 KB in 97134 files. 65868 KB in 23070 indexes. 24 KB in bad sectors. 226783 KB in use by the system. 65536 KB occupied by the log file. 141626984 KB available on disk. 4096 bytes in each allocation unit. 41368575 total allocation units on disk. 35406746 allocation units available on disk. Internal Info: 00 d8 01 00 98 d5 01 00 7b 8c 03 00 00 00 00 00 ........{....... 13 01 00 00 68 00 00 00 00 00 00 00 00 00 00 00 ....h........... f0 8a 28 00 50 01 27 00 f0 17 27 00 00 00 27 00 ..(.P.'...'...'. Windows has finished checking your disk. Please wait while your computer restarts. </Data> </EventData> </Event> I hope that turns out right. Okay now some history I was advised by the IT guy on the Toshiba board (actually through an email not on the board itself) to try using Wise registry cleaner in October (I also used the defragmenter), this was after effing around with fixing it since august or September...I was watching American football on free streams and seemed to have picked up some kind of virus (or so I thought, now I am not as certain) anyway. I never really figured out what it was or if it was totally removed but at the time I did suspect that all my messing around with it did do something to the registry. Here is what he told me in the email " link to reg cleaner then the rest..... Here is the reason I am asking you to do this, is because the errors you are getting are: hal.dll + efcd are a shared dynamic-link library (DLL) file. Errors related to it usually occur when a program mishandles the file during use. You are also getting: ntkrnlpa.exe. This is the one causing the major problem. The process is required for your PC to work properly. These errors are causing the blue screens of death. Also it appears your registry is a bit confused?? Messy. Download and run clean your registry. I will look at the rest of your minidump and get back to you" He also told me my errors looked like I had 64 bit not 32 installed. I checked I didn't. Anyway, sometime between aug. and sept. I used driver identifier (these are still in my windows.old folder on my d drive). I know I ran some other things before that virue detectors and such stuff, had macafry? for a short time. Malwarebytes antirootkit utility and Rouge Killer (will put reports in an additional code box. I downloaded the bluescreen view and it looks like the same thing I had. So will put more code boxes in now and then finish (FF crash #2, lol, I do laugh but dont really find it funny) 2 Rouge killer logs from oct. Code: RogueKiller V8.7.6 [Oct 28 2013] by Tigzy mail : tigzyRK<at>gmail<dot>com Feedback : .adlice.com/forum/ Website : .adlice.com/softwares/roguekiller/ Blog : Operating System : Windows 7 (6.1.7601 Service Pack 1) 32 bits version Started in : Safe mode with network support User : user [Admin rights] Mode : Remove -- Date : 11/21/2013 20:35:41 | ARK || FAK || MBR | ¤¤¤ Bad processes : 0 ¤¤¤ ¤¤¤ Registry Entries : 2 ¤¤¤ [HJ DESK][PUM] HKLM\[...]\NewStartPanel : {59031a47-3f72-44a7-89c5-5595fe6b30ee} (1) -> REPLACED (0) [HJ DESK][PUM] HKLM\[...]\NewStartPanel : {20D04FE0-3AEA-1069-A2D8-08002B30309D} (1) -> REPLACED (0) ¤¤¤ Scheduled tasks : 0 ¤¤¤ ¤¤¤ Startup Entries : 0 ¤¤¤ ¤¤¤ Web browsers : 0 ¤¤¤ ¤¤¤ Particular Files / Folders: ¤¤¤ ¤¤¤ Driver : [NOT LOADED 0xc000035f] ¤¤¤ ¤¤¤ External Hives: ¤¤¤ ¤¤¤ Infection : ¤¤¤ ¤¤¤ HOSTS File: ¤¤¤ --> %SystemRoot%\System32\drivers\etc\hosts RogueKiller V8.7.6 [Oct 28 2013] by Tigzy mail : tigzyRK<at>gmail<dot>com Feedback :.adlice.com/forum/ Website : .adlice.com/softwares/roguekiller/ Blog : tigzyrk.blogspot.com/ Operating System : Windows 7 (6.1.7601 Service Pack 1) 32 bits version Started in : Safe mode with network support User : user [Admin rights] Mode : Scan -- Date : 11/21/2013 20:34:05 | ARK || FAK || MBR | ¤¤¤ Bad processes : 0 ¤¤¤ ¤¤¤ Registry Entries : 2 ¤¤¤ [HJ DESK][PUM] HKLM\[...]\NewStartPanel : {59031a47-3f72-44a7-89c5-5595fe6b30ee} (1) -> FOUND [HJ DESK][PUM] HKLM\[...]\NewStartPanel : {20D04FE0-3AEA-1069-A2D8-08002B30309D} (1) -> FOUND ¤¤¤ Scheduled tasks : 0 ¤¤¤ ¤¤¤ Startup Entries : 0 ¤¤¤ ¤¤¤ Web browsers : 0 ¤¤¤ ¤¤¤ Particular Files / Folders: ¤¤¤ ¤¤¤ Driver : [NOT LOADED 0xc000035f] ¤¤¤ ¤¤¤ External Hives: ¤¤¤ ¤¤¤ Infection : ¤¤¤ ¤¤¤ HOSTS File: ¤¤¤ --> %SystemRoot%\System32\drivers\etc\hosts ¤¤¤ MBR Check: ¤¤¤ +++++ PhysicalDrive0: (\\.\PHYSICALDRIVE0 @ IDE) TOSHIBA MK3263GSX ATA Device +++++ --- User --- [MBR] f284f910c36350892d006484287696e2 [BSP] 3083da3519465601eb2a0020a4b7edbf : Windows 7/8 MBR Code Partition table: 0 - [ACTIVE] NTFS (0x07) [VISIBLE] Offset (sectors): 2048 | Size: 161596 Mo 1 - [XXXXXX] NTFS (0x07) [VISIBLE] Offset (sectors): 330950656 | Size: 143647 Mo User = LL1 ... OK! User = LL2 ... OK! Finished : << RKreport[0]_S_11212013_203405.txt >> RogueKiller V8.7.6 [Oct 28 2013] by Tigzy mail : tigzyRK<at>gmail<dot>com Feedback : .adlice.com/forum/ Website : .adlice.com/softwares/roguekiller/ Blog : /tigzyrk.blogspot.com/ Operating System : Windows 7 (6.1.7601 Service Pack 1) 32 bits version Started in : Safe mode with network support User : user [Admin rights] Mode : Scan -- Date : 11/21/2013 20:34:05 | ARK || FAK || MBR | ¤¤¤ Bad processes : 0 ¤¤¤ ¤¤¤ Registry Entries : 2 ¤¤¤ [HJ DESK][PUM] HKLM\[...]\NewStartPanel : {59031a47-3f72-44a7-89c5-5595fe6b30ee} (1) -> FOUND [HJ DESK][PUM] HKLM\[...]\NewStartPanel : {20D04FE0-3AEA-1069-A2D8-08002B30309D} (1) -> FOUND ¤¤¤ Scheduled tasks : 0 ¤¤¤ ¤¤¤ Startup Entries : 0 ¤¤¤ ¤¤¤ Web browsers : 0 ¤¤¤ ¤¤¤ Particular Files / Folders: ¤¤¤ ¤¤¤ Driver : [NOT LOADED 0xc000035f] ¤¤¤ ¤¤¤ External Hives: ¤¤¤ ¤¤¤ Infection : ¤¤¤ ¤¤¤ HOSTS File: ¤¤¤ --> %SystemRoot%\System32\drivers\etc\hosts ¤¤¤ MBR Check: ¤¤¤ +++++ PhysicalDrive0: (\\.\PHYSICALDRIVE0 @ IDE) TOSHIBA MK3263GSX ATA Device +++++ --- User --- [MBR] f284f910c36350892d006484287696e2 [BSP] 3083da3519465601eb2a0020a4b7edbf : Windows 7/8 MBR Code Partition table: 0 - [ACTIVE] NTFS (0x07) [VISIBLE] Offset (sectors): 2048 | Size: 161596 Mo 1 - [XXXXXX] NTFS (0x07) [VISIBLE] Offset (sectors): 330950656 | Size: 143647 Mo User = LL1 ... OK! User = LL2 ... OK! Finished : << RKreport[0]_S_11212013_203405.txt >> 13 new dumps in bluesreen view Code: #1 030414-79778-01.dmp 3/4/2014 5:43:03 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 0x83260c70 0x00000008 0x83260c70 0x00000002 ntkrnlpa.exe ntkrnlpa.exe+858e3 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+858e3 ntkrnlpa.exe+465f8 ntkrnlpa.exe+224227 C:\Windows\Minidump\030414-79778-01.dmp 2 15 7600 145,384 3/4/2014 5:46:38 AM ndis.sys ndis.sys+1f0ccf0 0x88417000 0x884ce000 0x000b7000 0x4a5bbf58 7/13/2009 3:12:24 PM Microsoft® Windows® Operating System NDIS 6.20 driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\ndis.sys ntkrnlpa.exe ntkrnlpa.exe+465f8 0x82813000 0x82c23000 0x00410000 0x4a5bc007 7/13/2009 3:15:19 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe Hope that is the right way to do it on here #2 these are all mostly from trying to start up this morning, been running okay since then, sort of. Code: 030414-15288-01.dmp 3/4/2014 4:31:54 AM DRIVER_OVERRAN_STACK_BUFFER 0x000000f7 0x0360428c 0x88271b4d 0x77d8e4b2 0x00000000 Ntfs.sys Ntfs.sys+3eb4d NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+dcd10 Ntfs.sys+2f9d2 Ntfs.sys+1647f ntkrnlpa.exe+68822 C:\Windows\Minidump\030414-15288-01.dmp 2 15 7600 145,384 3/4/2014 4:33:40 AM Ntfs.sys Ntfs.sys+3eb4d 0x88233000 0x88362000 0x0012f000 0x4a5bbf45 7/13/2009 3:12:05 PM Microsoft® Windows® Operating System NT File System Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\Ntfs.sys ntkrnlpa.exe ntkrnlpa.exe+dcd10 0x82811000 0x82c21000 0x00410000 0x4a5bc007 7/13/2009 3:15:19 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe #3 030414-13197-01.dmp 3/4/2014 4:24:41 AM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x82a62f92 0x90e713b8 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+244f92 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+244f92 ntkrnlpa.exe+24021a ntkrnlpa.exe+28a031 C:\Windows\Minidump\030414-13197-01.dmp 2 15 7600 145,376 3/4/2014 4:25:37 AM fileinfo.sys fileinfo.sys+de8a8bc 0x82fe7000 0x82ff8000 0x00011000 0x4a5bc18f 7/13/2009 3:21:51 PM Microsoft® Windows® Operating System FileInfo Filter Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\fileinfo.sys fltmgr.sys fltmgr.sys+debe7dc 0x82fb3000 0x82fe7000 0x00034000 0x4a5bbf11 7/13/2009 3:11:13 PM Microsoft® Windows® Operating System Microsoft Filesystem Filter Manager 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\fltmgr.sys halmacpi.dll halmacpi.dll+5ba9 0x82c2e000 0x82c65000 0x00037000 0x4a5bbf07 7/13/2009 3:11:03 PM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\halmacpi.dll ntkrnlpa.exe ntkrnlpa.exe+244f92 0x8281e000 0x82c2e000 0x00410000 0x4a5bc007 7/13/2009 3:15:19 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe #4 030414-14898-01.dmp 3/4/2014 4:14:53 AM 0x00000124 0x00000000 0x857d9024 0xb2000040 0x00000800 halmacpi.dll halmacpi.dll+ef3f Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+dcd10 halmacpi.dll+ef3f ntkrnlpa.exe+cef04 halmacpi.dll+f1f1 C:\Windows\Minidump\030414-14898-01.dmp 2 15 7600 145,384 3/4/2014 4:18:33 AM halmacpi.dll halmacpi.dll+ef3f 0x8281d000 0x82854000 0x00037000 0x4a5bbf07 7/13/2009 3:11:03 PM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\halmacpi.dll ntkrnlpa.exe ntkrnlpa.exe+123d48 0x82854000 0x82c64000 0x00410000 0x4a5bc007 7/13/2009 3:15:19 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe #5 and 6 same as 4 #7 almost same 030414-36051-01.dmp 3/3/2014 9:55:21 PM NTFS_FILE_SYSTEM 0x00000024 0x001904fb 0xac3f57c0 0xac3f53a0 0x82ae492f halmacpi.dll halmacpi.dll+56ee Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+dcd10 Ntfs.sys+14221 Ntfs.sys+1946d ntkrnlpa.exe+7010e C:\Windows\Minidump\030414-36051-01.dmp 2 15 7600 145,856 3/4/2014 1:23:14 PM halmacpi.dll halmacpi.dll+56ee 0x82a18000 0x82a4f000 0x00037000 0x4a5bbf07 7/13/2009 3:11:03 PM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\halmacpi.dll Ntfs.sys Ntfs.sys+32f30 0x8882e000 0x8895d000 0x0012f000 0x4a5bbf45 7/13/2009 3:12:05 PM Microsoft® Windows® Operating System NT File System Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\Ntfs.sys ntkrnlpa.exe ntkrnlpa.exe+dcd10 0x82a4f000 0x82e5f000 0x00410000 0x4a5bc007 7/13/2009 3:15:19 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe hmm says 13 but only see 7 files? anyway that is this morns. start up crashes Last thing: today's issues, that I keep seeing or that have been happening for quite a long time 1. typing the letter t makes the cursuer jump around sometimes (today for instance) 2. driver for sleep button keeps ending up as an unknown device (in system aci compl... in the device manager) when I reinstall. Didn't put it in the right place yet and it is seeming more stable today. 3. Realtech installed (reinstalled a driver on start up this morning (missed the details but will look in windows messages which I have 4 of right now) 4 Clock time (I mean the clock on the rh bottom of the screen is changed and wrong today, I think it was ok last night. 5. on going issues with the 2 browsers i haave installed (FF has no flash because then it crashes even more) IE can't work long though at all. I am not using (didn't install) chrome but I would if it worked. Chrome esply was doing something that made BSOD come on faster.... 6. didn't run updates or enter the key yet, I think I should see if it can be fixed before having MS mess it up again if possible. Questions: Is there a nice CPU or motherboard test like the disc thing I ran today? I know there is some sort of plug in 4 digit number thing for a motherboard (forget the name of the device though) but I cant find one around here anyway. I used meme test in oct or so also ran for 7 or 8 hours didn't find an issue. One of the first things I did. I took it apart and cleaned it. I am pretty certain I was gental enough and put everything back together well (I was a car mechianic in the distant past, can't help doing the phsyical labor first). It was after one of my very first bsods and it ran 2 or 3 weeks before the next. But should I crack it open and check all the connections in your opinion? Last of a really long post, I know sorry and thank you again! I have Toshiba discs coming in 2 or 3 days, if this issue persists what should I do? Use them to reinstall? Do I put them in b4 the windows disc? If I use them will they root out a regisrty problem? Oh in my action center thsi mprning two more things that keep re occuring Download update for Toshiba Supervisor Password Utility and Download and install the driver for your Bluetooth device which is stupid to even have on here as I don't use bluetooth or the password utility. I usually do those things as part of the install though. Thanks again
A few more is becoming more unstable I am afraid. First one which I think is the last one happened in safemode, not good right? Code: 030514-20529-01.dmp 3/5/2014 7:37:42 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 0x8ffcc0b1 0x00000008 0x8ffcc0b1 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+858e3 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+858e3 ntkrnlpa.exe+465f8 win32k.sys+1d6090 C:\Windows\Minidump\030514-20529-01.dmp 2 15 7600 139,272 3/5/2014 7:38:39 AM halmacpi.dll halmacpi.dll+5ba9 0x82628000 0x8265f000 0x00037000 0x4a5bbf07 7/13/2009 3:11:03 PM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\halmacpi.dll ntkrnlpa.exe ntkrnlpa.exe+40875 0x82218000 0x82628000 0x00410000 0x4a5bc007 7/13/2009 3:15:19 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe win32k.sys win32k.sys+ffba3634 0x8fd30000 0x8ff7a000 0x0024a000 0x4a5bc2a2 7/13/2009 3:26:26 PM Microsoft® Windows® Operating System Multi-User Win32 Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\win32k.sys 030514-11700-01.dmp 3/5/2014 7:16:03 AM 0x00000124 0x00000000 0x85b881e4 0xb2000000 0x00000115 halmacpi.dll halmacpi.dll+ef3f Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+dcd10 halmacpi.dll+ef3f ntkrnlpa.exe+cef04 halmacpi.dll+f1f1 C:\Windows\Minidump\030514-11700-01.dmp 2 15 7600 145,376 3/5/2014 7:16:47 AM halmacpi.dll halmacpi.dll+ef3f 0x83210000 0x83247000 0x00037000 0x4a5bbf07 7/13/2009 3:11:03 PM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\halmacpi.dll ntkrnlpa.exe ntkrnlpa.exe+123d48 0x82e00000 0x83210000 0x00410000 0x4a5bc007 7/13/2009 3:15:19 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe ntkrnlpa.exe ntkrnlpa.exe+123d48 0x82e00000 0x83210000 0x00410000 0x4a5bc007 7/13/2009 3:15:19 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe 030514-11965-01.dmp 3/5/2014 7:15:16 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x00000004 0x00000002 0x00000001 0x86c613a0 rdyboost.sys rdyboost.sys+a3b5 ReadyBoost Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+467eb rdyboost.sys+ac94 rdyboost.sys+71b8 C:\Windows\Minidump\030514-11965-01.dmp 2 15 7600 145,376 3/5/2014 7:15:53 AM 030514-11965-01.dmp 3/5/2014 7:15:16 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x00000004 0x00000002 0x00000001 0x86c613a0 rdyboost.sys rdyboost.sys+a3b5 ReadyBoost Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+467eb rdyboost.sys+ac94 rdyboost.sys+71b8 C:\Windows\Minidump\030514-11965-01.dmp 2 15 7600 145,376 3/5/2014 7:15:53 AM CLASSPNP.SYS CLASSPNP.SYS+f7e3aaf0 0x889a7000 0x889cc000 0x00025000 0x4a5bbf18 7/13/2009 3:11:20 PM Microsoft® Windows® Operating System SCSI Class System Dll 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\CLASSPNP.SYS ntkrnlpa.exe ntkrnlpa.exe+467eb 0x82e46000 0x83256000 0x00410000 0x4a5bc007 7/13/2009 3:15:19 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe rdyboost.sys rdyboost.sys+a2b5 0x88c00000 0x88c2d000 0x0002d000 0x4a5bc19a 7/13/2009 3:22:02 PM Microsoft® Windows® Operating System ReadyBoost Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\rdyboost.sys There is more but am lazy to keep going and kind of losing hope here.
First things first: 1 - Back up your data to another drive or DVD. 2 - Do a clean install. 3 - Verify system is stable. "Chkdsk" for the drive. "Memtest86" for the ram. 4 - Because you've done a clean install, it is now less likely a driver issue exists. 5 - Now you can activate. No point in activating until you know your system is clean and stable. Activating can be done at anytime, and if you lose it for some reason, it can always be redone. (Daz loader is superb!) The Windows 7 Sticky's have info on obtaining source media and activating. If you don't have bad hardware, there is no reason you can't get up and running again. Good luck!
thanks Thank you, I have a chkdsk log upthread from yesterday morning. I have done that a few times recently (2 days ago for instace) and many times in the past. i have done a mem test in the past but it said it was okay after 6 or 8 hours. at the moment it isn't staying started, the windows memory danogstic just ran said it is okay (right now it wluldn't run the meme86 thing b4 crashing, i don't have time right now for another new install either, after the toshbia disc arrives i plan on it). i realize i could have put too much information in the thread already but I just wanted to be clear what i have done so far. I do plan on doing a new install when my Toshiba disc get here in a day or two.
Make sure nothing is overheating. Check that the fans are running and the heatsinks aren't clogged with termites. A flaky hard drive will cause BSODs.
Thank you, I actually cleanedvit out well when it first started Bsoding which is why I took it apart in the first place. I had a temp p3ogram on it, never saw it higher than 62 (an most of the time it was 40s and 50s) I have been living across the street from them building a building so I thought it could be kind of dusty inside the case but it was fairly clean. I also loked for any burn marks in the main board as my last Mac when they opened it at the comuter repair store had actual phsical damage that you could see. (edit oops see you said hd now, it just ested ok with the program Daz suggested although it had some errors in chkdsk). I am thinking about also installing Umbutu and seeing if that crashes, if I continue having problems when I get the Toshiba disc.
Wouldn't hurt to reseat the any memory in sockets. Just because tests say the data is ok doesn't mean the drive is not on it's last lap. I had one laptop drive that would blue screen Windows when it felt like it. I had to cool off the drive in the fridge. I was able to image it and put the image on a replacement. No more BSOD after that.
How much memory does this system have? 2GB with two 1GB sticks? I would try removing 1GB to see if it still BSOD's and if it does then try with just the other stick instead. If it then still BSOD's then I bet it'll be due to the hard drive as you mentioned that during the scan before it did say that you've got bad sectors. Other options you could try are the following. 1. Reset the BIOS to fail safe defaults 2. Format the whole drive and not just a single partition with Active@ KillDisk (free ISO version) and do the one pass zero's wipe 3. Install a digital river version of Windows 7 SP1 4. Don't install any drivers yourself If it still BSOD's after that then you'll probably need a new hard drive. If you can't get a new hard drive yet and you just want to get online and do stuff then install Ubuntu, Zorin OS 8 or Zorin OS 7.1 Lite (the Lite version would work the fastest). All of them can be run from a DVD or USB.
Thank you both. Daz did you see the post #9? you said to put the results from hd scan and I realize I put a lot more there but I had some questions and stuff for you too. There ise the latest chkdsk which has theRead failures and more bluescreen views with the drivers listed as well. If I run killdisc then where are the drivers? I have been confused about this for a while. Will they be on my toshbia disc? There are none on windows discs right? Is it possible that this is all happening because of a regitsrty error? Would killdisc and reformatting the whole drive fix that? Are there any tests for the cpu/motherboard? I probably wount be doing anything until tonight or tomorrow but, i will have to reinstall again just to get anything done at all. I have no access to anyother computer to burn cds or copy stuff i want off the d drive. do you think i should do the memory sticks out befofe reinstall or after? there 2, 1gb as you said. how do i get to the bios settings to failsafe? never saw that in there?
I think it's just called "default settings". No one seems to have yet suggested trying a cd based system, like Hiren's boot cd. or a species of Linux that runs on a cd. If that runs without bsod, for a reasonable period it should indicate the prob to be in the hd. I keep several hard drives around with os on them (leftovers from previous upgrades) which I can plug in to test. I've also got one that was giving me bsod's last summer that I haven't trusted to put back in service. never hurts to have a spare hd. ...T
Yes, I seen the info in post #9. If you run KillDisk it'll format the entire drive and zero everything out, so it's going to make the drive as clean as possible. Before doing this you should try removing the RAM and changing between each stick. Doing that would help to determine if one of the sticks is bad. When you install Windows 7 it'll come with a bunch of drives and it'll download most of the missing drivers on it's own, although you might also find some under optional Windows updates. This makes for a good test since Windows should run great on it's stock drivers. If it doesn't for you though then it's likely that the hard drive is what's at fault. You could do a CPU stress test, but the odds are you'll get a BSOD during the test due to the system becoming more unstable. Most BIOS's will have an option to reset to the fail safe settings or factory defaults. If you don't see the option though then it's not going to be a problem if you've never adjusted any of your BIOS settings anyway.
thank you Daz, don't understand how it wil be conected to the internet, if everything is out of it though, my setings forvthat wil be gone too, no? lol, i told you i am a novice (not proud of the fact but it is the truth, sorry). Everything else makes sense to me.oh and your right bios has a default option, i even used it before (and for some reason it made things worse), it was just the "fail safe" that threw me there.