Question Bsod caused by ssd chip?

[ihatemylaptop]

I've used this windows 11 for not even a year, A few months ago i recived BSOD. I asked my co-pilot (AI) and we've gotten to the conclusion that this might be caused by my ssd chip. Ive installed SSD chip readers. None can read my ssd chip, I got this laptop in walmart for 100-200 usd i can't rember, my co-pilot said its because my ssd chip is cheap or either broken. When i get the BSOD the stop code is: DRIVER DMA VIOLATION. Does anyone know if it is my chip or something? Ive run hardware scans and my laptop is completly fine. Do you recommend i take it to a repair shop?

 

[USAFRet]

I asked my co-pilot (AI)

Don't do that....


Give us the FULL parts list of this system.
And then, exactly what happened. Screenshots if possible.

 

[johnbl]

I've used this windows 11 for not even a year, A few months ago i recived BSOD. I asked my co-pilot (AI) and we've gotten to the conclusion that this might be caused by my ssd chip. Ive installed SSD chip readers. None can read my ssd chip, I got this laptop in walmart for 100-200 usd i can't rember, my co-pilot said its because my ssd chip is cheap or either broken. When i get the BSOD the stop code is: DRIVER DMA VIOLATION. Does anyone know if it is my chip or something? Ive run hardware scans and my laptop is completly fine. Do you recommend i take it to a repair shop?

pcs have a DMA (direct memory access controller) these are a limited resource. Generally, for this error I would, update the bios, update the sound drivers, then the graphics drivers.

often if you have verifier.exe flags turnned on then you see bugchecks in sound drivers due to problems with the DMA.

ie if you have verifier on then you might get
driver_verifier_dma_violation bugcheck

(run verifier.exe /reset to turn off verifier )
generally, it is best to provide the actual minidump file.
someone can look at parameter 1 and get a better idea of the cause.
note: (info on dma remapping, depending on the device)

https://learn.microsoft.com/en-us/w...enabled-for-a-specific-device-driver-instance

normally, this problem would require a kernel memory dump but , I think microsoft is now putting some of the proper info into the minidump so it can be debugged. People can get this bugcheck with verifier turned off now (i think)

 

[SteJBorchard]

It could just be that specific USB device or the USB connector your using.

does this happen when connecting ANY usb device or just specific ones.