- Thread Author
- #1
Hello, I've been having BSOD and can't really figure out what is going on. I have done a bunch of googling and just get more confused, lol. Losing mind. Need help. LOL. I have a Samsung Chronos Series 7 Model NP700Z7C-S01US. I tried to link to specs, but the forum wouldn't let me.
(As I was writing up this post and doing the tests, notice the ram amount and 2 sticks in the specs, this will matter later in the tests. Windows reports 8GB of Ram so that's correct. Apparently one stick is soldered to the motherboard, one is reachable by removable panel on the back of the laptop)
I have had very long boot times for awhile. I do not reboot or turn off the machine very often, so I'm not sure when or why that could have started. The BSOD just started happening. The only thing I can think of that could have caused it are, installing a WD MyCloud into the networking system, which works fine except when I reboot the computer sometimes I get a notification that the mapped networked drives could not connect and all the mapped drives have a big red x on them until I double-click them, then they are ok. I also tried to add my new Sony HT-CT370 sound bar to bluetooth devices on my laptop so I could listen to the music through the soundbar. Windows reported the driver did not install correctly, and I could not get it to work, so I removed the soundbar. I think the soundbar thing may have been what started it, but not sure. My computer gets a lot of beating though, I install and try out software, it is three years old and never been restored to factory. So anything probably could have messed it up.
------------------------------------------------------------------------------------------------------------------------
Just some quick copy and paste from NirView:
The problem seems to be caused by the following file: aswSnx.sys
DRIVER_VERIFIER_DETECTED_VIOLATION
*** aswSnx.sys - Address 0xfffff88001ea05fb base at 0xfffff88001e77000 DateStamp
0x55364a30
-----------------------------------------------
The problem seems to be caused by the following file: aswSP.sys
MEMORY_MANAGEMENT
*** aswSP.sys - Address 0xfffff880039bb7a0 base at 0xfffff88003959000 DateStamp
0x55364d99
-----------------------------------------------
The problem seems to be caused by the following file: iaStor.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** iaStor.sys - Address 0xfffff8800124cceb base at 0xfffff8800121f000 DateStamp
0x4ed5a567
------------------------------------------------
The problem seems to be caused by the following file: ntoskrnl.exe
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
*** ntoskrnl.exe - Address 0xfffff80002679a40 base at 0xfffff80002607000 DateStamp
0x5507a73c
------------------------------------------------------
The problem seems to be caused by the following file: ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL
*** ntoskrnl.exe - Address 0xfffff80002684a40 base at 0xfffff80002612000 DateStamp
0x5507a73c
---------------------------------------------------
The problem seems to be caused by the following file: ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA
*** ntoskrnl.exe - Address 0xfffff800026c8a40 base at 0xfffff80002656000 DateStamp
0x5507a73c
---------------------------------------------------------------------------------------------------------------
I have attached the W7F Diagnostic.
I ran and attached screenshots for CPUID. (Weirdly, I have 8GB of ram and supposedly two RAM sticks. It only shows 4GB and one stick in the this program. Which led me to do a scan of my system at Crucial. It says I should have 8GB RAM and two 4GB sticks.
Does this mean one of my sticks is bad?
I could not attach the RAMMon html report because the extension is not allowed for the forum, but I attached the text report. Once again this did not report the other ram stick.
I ran a memory tester (once again forum croaked on the real program lol) quickly a week ago, and it passed, so I ruled out RAM problems. But I really didn't know what I was doing. Do you guys think this is the problem, or is there something else? Once again, one stick is soldered to motherboard and one is reachable by a panel on the back of the computer. Windows reports 8GB ram.
Thanks so much!
Gina
(As I was writing up this post and doing the tests, notice the ram amount and 2 sticks in the specs, this will matter later in the tests. Windows reports 8GB of Ram so that's correct. Apparently one stick is soldered to the motherboard, one is reachable by removable panel on the back of the laptop)
I have had very long boot times for awhile. I do not reboot or turn off the machine very often, so I'm not sure when or why that could have started. The BSOD just started happening. The only thing I can think of that could have caused it are, installing a WD MyCloud into the networking system, which works fine except when I reboot the computer sometimes I get a notification that the mapped networked drives could not connect and all the mapped drives have a big red x on them until I double-click them, then they are ok. I also tried to add my new Sony HT-CT370 sound bar to bluetooth devices on my laptop so I could listen to the music through the soundbar. Windows reported the driver did not install correctly, and I could not get it to work, so I removed the soundbar. I think the soundbar thing may have been what started it, but not sure. My computer gets a lot of beating though, I install and try out software, it is three years old and never been restored to factory. So anything probably could have messed it up.
------------------------------------------------------------------------------------------------------------------------
Just some quick copy and paste from NirView:
The problem seems to be caused by the following file: aswSnx.sys
DRIVER_VERIFIER_DETECTED_VIOLATION
*** aswSnx.sys - Address 0xfffff88001ea05fb base at 0xfffff88001e77000 DateStamp
0x55364a30
-----------------------------------------------
The problem seems to be caused by the following file: aswSP.sys
MEMORY_MANAGEMENT
*** aswSP.sys - Address 0xfffff880039bb7a0 base at 0xfffff88003959000 DateStamp
0x55364d99
-----------------------------------------------
The problem seems to be caused by the following file: iaStor.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** iaStor.sys - Address 0xfffff8800124cceb base at 0xfffff8800121f000 DateStamp
0x4ed5a567
------------------------------------------------
The problem seems to be caused by the following file: ntoskrnl.exe
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
*** ntoskrnl.exe - Address 0xfffff80002679a40 base at 0xfffff80002607000 DateStamp
0x5507a73c
------------------------------------------------------
The problem seems to be caused by the following file: ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL
*** ntoskrnl.exe - Address 0xfffff80002684a40 base at 0xfffff80002612000 DateStamp
0x5507a73c
---------------------------------------------------
The problem seems to be caused by the following file: ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA
*** ntoskrnl.exe - Address 0xfffff800026c8a40 base at 0xfffff80002656000 DateStamp
0x5507a73c
---------------------------------------------------------------------------------------------------------------
I have attached the W7F Diagnostic.
I ran and attached screenshots for CPUID. (Weirdly, I have 8GB of ram and supposedly two RAM sticks. It only shows 4GB and one stick in the this program. Which led me to do a scan of my system at Crucial. It says I should have 8GB RAM and two 4GB sticks.
Does this mean one of my sticks is bad?
I could not attach the RAMMon html report because the extension is not allowed for the forum, but I attached the text report. Once again this did not report the other ram stick.
I ran a memory tester (once again forum croaked on the real program lol) quickly a week ago, and it passed, so I ruled out RAM problems. But I really didn't know what I was doing. Do you guys think this is the problem, or is there something else? Once again, one stick is soldered to motherboard and one is reachable by a panel on the back of the computer. Windows reports 8GB ram.
Thanks so much!
Gina