New
#1
Recent Bsods happening at random
Hey,
Been having BSODs at random moments, sometimes it goes good for a longer period, sometimes it goes good for a short period. Hope u can help!
Robert
Hey,
Been having BSODs at random moments, sometimes it goes good for a longer period, sometimes it goes good for a short period. Hope u can help!
Robert
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
NotePay close attention to part 3 of the tutorial in order to rule out the faulty stick.
InformationErrors are sometimes found after 8 passes.
TipDo this test overnight, before going to bed.
If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:
Upload a screenshot of your hard disk using CrystalDiskInfo:
Make a hard drive test from the hard drive manufacturers website:
Run Disk Check on your hard disk for file system errors and bad sectors on it:
Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.
Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.
Hey,
i did everything except the memory diagnostic tool and the hard drive test from the manufacturers website. I will still do those, but I will provide u already with the things u asked for. I didn't find any errors in the other tests by the way.
Thanks I will wait for the results.
If you are overclocking any hardware please stop and revert to factory settings till the system is stable.
Also do the following:
1. Update the BIOS to latest version available:
2. Uninstall Magic Disc:Code:BIOS-versie/datum American Megatrends Inc. 0802, 24-8-2010
3. Scan your System with Microsoft Security Essentials and Malwarebytes (separately).Code:Start Menu\Programs\MagicDisc Public:Start Menu\Programs\MagicDisc Public
- Microsoft Security Essentials, Free antivirus for windows
- Malwarebytes Anti-Malware Free
- Good and Free system security combination
WarningDo not start the free trial of Malware Bytes; remember to deselect that option when prompted.
4. Driver Verifier enable to see if it catches any misbehaving drivers:
Hey, I have tried to update my Bios true the site of ami.com with their AMI firmware update utility(AMI | American Megatrends Inc. : Product Support). As soon as i press ok, when it says it is going to install it now, my Pc crashes and gives me the screen u get before a bsod and it stucks on that. I tried this several times and everytime the same effect. The utility doesn't work in safe mode, so that is not an option.
I uninstalled Magicdisc and activated driver verifier. I had like 2 bsods in 24 hours with driver verifier, I am not sure what to conclude out of this? I furthermore attached the dump files of some recent bsods to this post. I will do the memory diagnostic tool tonight.
I hope you can help with this!
Does not seem like verifier was enabled and the BSOD's are of 17 - 18th of March.
First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.
Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.
Sorry, I didn't gain a notification on my mail that you had reacted, thus my late reaction.
I do have it enabled such that my pc saves minifump files. The problem is that since I have enabled verifier, my pc doesn't finish the bsod. It stucks at the crashing phase, I never get to the blue screen. It is the same crashing phase as when I have bsods, so we are talking about a bsod, but it just doesn't get to the blue screen, so it doesn't save the dump files. I am gonna disable verifier now and see if I do can get to the blue screen, as it was before. Also will try to update bios with verifier disabled, it might help?
I updated my bios, but it is the same as the other one; both version 0802. There is no newer version for my BIOS I believe. (ASUSTeK Computer Inc. -Support- Drivers and Download M4A78LT-M)
Had some BSODs before I updated Bios, i attached them. I didn't had much problems with them when using verifier, but as soons as I stopped that service there came more BSODs, very strange.
If you are overclocking any hardware, STOP. Reset any changed values back to default.
Reseat all your hardware components.
Check your hard drive(s) for errors by running chkdsk:
Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file.
To do this, follow these steps:
- Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
- At the command prompt, type the following command, and then press ENTER: sfc /scannow
The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.
SFC /SCANNOW Command - System File Checker
Outdated and Problematic Drivers:
You should update/replace/remove the following drivers. Any drivers that are known to cause BSODs, please remove the software or remove the drivers and then remove the device; steps to do so are given after the list of outdated drivers. If you have ASACPI.sys installed, make sure it is updated and not pre-2009; pre-2009 versions are known to cause BSODs:
The following is for information purposes only. Any drivers in red should be updated/replaced/removed.
AsIO.sys Mon Apr 6 13:21:08 2009 (49D9AD64)
Asus PCProbe Utility
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
ASACPI.sys Thu Jul 16 09:31:29 2009 (4A5E9F11)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
AODDriver2.sys Thu Apr 5 15:23:37 2012 (4F7D6499)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
Code:Debug session time: Tue Mar 26 22:26:33.874 2013 (UTC + 6:00) Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\032613-20872-01.dmp] Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime: 0 days 0:21:30.451 Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 ) BugCheck A, {28, 2, 0, fffff800030c6e40} BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a) Bugcheck code 0000000A Arguments: Arg1: 0000000000000028, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800030c6e40, address which referenced memory BUGCHECK_STR: 0xA DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0xA_nt!MiFindNodeOrParent+0 BiosVersion = 0802 BiosReleaseDate = 08/24/2010 SystemManufacturer = System manufacturer SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Debug session time: Tue Mar 26 22:04:12.264 2013 (UTC + 6:00) Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\032613-19234-01.dmp] Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431 System Uptime: 0 days 0:13:39.840 Probably caused by : memory_corruption ( nt!MiAddViewsForSection+122 ) BugCheck 24, {1904fb, fffff88008347068, fffff880083468c0, fffff80003090612} BugCheck Info: NTFS_FILE_SYSTEM (24) Bugcheck code 00000024 Arguments: Arg1: 00000000001904fb Arg2: fffff88008347068 Arg3: fffff880083468c0 Arg4: fffff80003090612 PROCESS_NAME: rundll32.exe BUGCHECK_STR: 0x24 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT FAILURE_BUCKET_ID: X64_0x24_nt!MiAddViewsForSection+122 BiosVersion = 0802 BiosReleaseDate = 08/24/2010 SystemManufacturer = System manufacturer SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``