New
#1
Random BSOD on Newly Installed Win10
Hi, I recently just did a clean install of Windows 10 and I have gotten a few BSOD. Ive attached the minidumps as requested. Please help me out. Thanks in advance!
Hi, I recently just did a clean install of Windows 10 and I have gotten a few BSOD. Ive attached the minidumps as requested. Please help me out. Thanks in advance!
Hi Seanyiap,
Welcome to the 10forums :)
Please check Lenovo for BIOS & network driver updates + remove 1 of the 2 sticks and let us know how it goes.
Code:[Memory Device (Type 17) - Length 34 - Handle 002bh] Physical Memory Array Handle 002ah Memory Error Info Handle 002fh Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 0dh - SODIMM Device Set [None] Device Locator DIMM0 Bank Locator BANK 0 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1600MHz Manufacturer Kingston Serial Number Asset Tag Number Part Number 9905417-082.A00G [Memory Device (Type 17) - Length 34 - Handle 002dh] Physical Memory Array Handle 002ah Memory Error Info Handle 0030h Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 0dh - SODIMM Device Set [None] Device Locator DIMM2 Bank Locator BANK 2 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1600MHz Manufacturer Unknown Serial Number Asset Tag Number Part Number RMT3170EB68F9W1600
Thanks for the reply Axe0. I just downgraded my laptop to windows 8.1 hoping that the problem will go away but I am still getting BSOD even in safeboot. Should I make a thread in the eightforums or will you be able to help? I will update the BIOS and network drivers as soon as I get to my computer. About the ram, I have 3 sticks. Two 2gb that came with the laptop and a 4gb ram that I upgraded few years ago. Which should I remove? I have ran memtest and no errors we found.
Normally it is suggested to create a new thread at the eightforums yes, but as you say that you've had a BSOD too in safe mode I think it wouldn't matter a lot :)
Remove the 4GB memory that you added, it is not adviced to add memory to the current memory for some reasons.
I find this post a wonderful explanation about using mixed memory by @essenbe from My Norton AV tells me: dm_log_collector.exe is not safe and has been - Page 13 - Windows 10 Forums
Arc is also correct that a 16 GB kit is always preferable to 2 different sets of ram. Even if they are the same manufacturer and model. There are minor differences from the manufacturing process which can cause problems. A kit of ram is tested to work together where individual sticks are not. many motherboards are very picky when it comes to ram.
my mistake axe0, my laptop only has 2 4gb sticks. I removed the newer one and I couldn't even boot into windows. So I removed the old one and put in the new and I was able to boot into windows without any BSOD. Will update you as soon as I receive a BSOD
I got a BSOD after an hour of removing my ram.
It seems driver verifier has caused the crash but it hasn't flagged any drivers what usually relates to hardware problems.
Unfortunately with the provided information there isn't much to go from to give suggestions for a next step, so I would like you to run the DM Log Collector again and upload a new zip file.
Please fill in your system specsCode:6: kd> !verifier Verify Flags Level 0x01acefbb STANDARD FLAGS: [X] (0x00000000) Automatic Checks [X] (0x00000001) Special pool [X] (0x00000002) Force IRQL checking [X] (0x00000008) Pool tracking [X] (0x00000010) I/O verification [X] (0x00000020) Deadlock detection [X] (0x00000080) DMA checking [X] (0x00000100) Security checks [X] (0x00000800) Miscellaneous checks [ ] (0x00020000) DDI compliance checking ADDITIONAL FLAGS: [ ] (0x00000004) Randomized low resources simulation [X] (0x00000200) Force pending I/O requests [X] (0x00000400) IRP logging [X] (0x00002000) Invariant MDL checking for stack [X] (0x00004000) Invariant MDL checking for driver [X] (0x00008000) Power framework delay fuzzing [ ] (0x00010000) Port/miniport interface checking [X] (0x00040000) Systematic low resources simulation [X] (0x00080000) DDI compliance checking (additional) [X] (0x00200000) NDIS/WIFI verification [X] (0x00800000) Kernel synchronization delay fuzzing [X] (0x01000000) VM switch verification [ ] (0x02000000) Code integrity checks [X] Indicates flag is enabled Summary of All Verifier Statistics RaiseIrqls 0xa66e8 AcquireSpinLocks 0x1610ec Synch Executions 0xd7fd Trims 0x120797 Pool Allocations Attempted 0xa0fdff Pool Allocations Succeeded 0xa0fdff Pool Allocations Succeeded SpecialPool 0xa0fdff Pool Allocations With NO TAG 0x0 Pool Allocations Failed 0x0 Current paged pool allocations 0x83 for 000025BA bytes Peak paged pool allocations 0x85 for 00002852 bytes Current nonpaged pool allocations 0xf36 for 00351746 bytes Peak nonpaged pool allocations 0x136a for 003AD426 bytes GetPointerFromAddress: unable to read from fffff80206769138 Unable to get MmSystemRangeStartPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:
I have attached the zip file as requested. I have also updated my system specs.
Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.
Forum rulesCode:<ActivePartialProductKey>9D6T9</ActivePartialProductKey> <ActiveProductKeyPid2>00261-50000-00000-AA052</ActiveProductKeyPid2> <OSVersion>6.3.9600.2.00010100.0.0.048</OSVersion> <ProductName>Windows 8.1 Pro</ProductName> <ProcessorArchitecture>x64</ProcessorArchitecture> <EditionId>Professional</EditionId> <BuildLab>9600.winblue_r4.141028-1500</BuildLab> <TimeZone>Malay Peninsula Standard Time(GMT+08:00)</TimeZone> <ActiveSkuId>c06b6981-d7fd-4a35-b7b4-054742b7af67</ActiveSkuId> <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription> <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups> <ActiveProductKeyPKeyId>ace182fe-75fe-ee4b-31e7-9fb20a237002</ActiveProductKeyPKeyId> <ActiveProductKeyPidEx>06401-02615-000-000000-03-17417-9600.0000-1412016</ActiveProductKeyPidEx> <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel> <ActiveVolumeCustomerPid>03612-00168-271-708455-03-1033-10240.0000-1412016</ActiveVolumeCustomerPid> <OfflineInstallationId>079541472431308297801925825477008959669696325327657990746060881</OfflineInstallationId> <DomainJoined>false</DomainJoined>
4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).
Thanks anyway axe0! I haven't gotten any BSOD except the driver verifier BSOD after I removed my ram. If I were to upgrade my memory should I buy one extra stick or do I have to buy a kit?