New
#11
Is there a way that i can make it happen... coz if i wait for all updates to install, then it will take a lot of time!
Is there a way that i can make it happen... coz if i wait for all updates to install, then it will take a lot of time!
Hi genxcoders.
As per the latest BSOD happened at 5:52 PM today, the system is not Service Pack 1 installed yet.
But without SP1 installed, it will be very hard to go any deeper to the issue.Code:Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Get the updates other than the optional ones. Let the update run overnight, if needed. But that is a must.
Hi once again... I am having the problem in the same machine that i have been discussing in this thread...
Have got time today after long...
So here I go... I have finally changed the HDD also (earlier got the Mother Board, RAM changed)... And I have also finally been able to install SP1 on Windows 7 Professional... I now have two files from the SP Diagnostic Tool which I am uploading here... Please provide expert opinions on the same and help me solve this problem...
Regards,
GenXCoders
Follow post #6 now ... both the memtest86+ and Driver Verifier, one by one.
It is a memory caused BSOD. Either the RAM is malfunctioning or any driver is passing bad info to the memory.Code:BugCheck 1A, {41790, c0802198, ffff, 0} Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+41a ) Followup: MachineOwner ---------
BSoD after installing SP1 for windows 7
please advice
Versatile bugchecks.
Code:BugCheck 1A, {41790, c0802092, ffff, 0} Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+41a ) Followup: MachineOwner ---------Code:BugCheck 24, {1904fb, 827b712c, 827b6d10, 85ab5441} Probably caused by : Ntfs.sys ( Ntfs!NtfsSnapshotScbInternal+194 ) Followup: MachineOwner ---------Saying it again, Follow post #6 now ... both the memtest86+ and Driver Verifier, one by one. Let us know the results.Code:BugCheck 19, {22, 1000, 0, 0} GetPointerFromAddress: unable to read from 82d6f718 Unable to read MiSystemVaType memory at 82d4f1a0 Probably caused by : ntkrpamp.exe ( nt!ExpFindAndRemoveTagBigPages+1fd ) Followup: MachineOwner ---------
@ARC:
I have done the MemTest+ for like 48Hrs+ straight... it went on till 18 or 19 passes...
There were no errors or red lines or anything...
i had taken the snapshot through my phone to send... but i dont have it now as after that i tweaked my tab to use Lollipop and had deleted the entire stuff... I will just check the Driver Verifier thing and get back...
Dear Arc,
Sorry for the delay i posting, had a few prior commitment to take care of...
But the machine had BSoD twice, after enabling the Driver Verifier. I have attached the files here, generated through "SF_Diagnostic_Tool.exe". Please have a look!
Regards,
Aashish
GenXCoders
Unfortunately none of them are recorded. May be those took place before the computer booted to desktop?
Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus, MSC for your case.
- Apply > OK
- Accept then restart.
Then try Driver Verifier for one more time. Hopefully we will get a crash dump this time.