BSOD Help please.

August 7th, 2016

Okay so recently went to Geek Squad, and had them check out my computer because I was getting blue screens, said my hard drive was damaged blah blah blah.
Got a new hard drive installed it, installed a brand new copy of windows 7 ultimate, and have done literally nothing but ran Windows Updates, installed Norton 360, and League of Legends (well and now FireFox) and I’m still getting blue screens if anyone could help I’d appreciate it.
computer name: WOLF-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: p7-1174, Hewlett-Packard, PEGATRON CORPORATION, 2ACD
CPU: AuthenticAMD AMD A8-3800 APU with Radeon(tm) HD Graphics AMD586, level: 18
4 logical processors, active mask: 15
RAM: 8036913152 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 9/12/2014 5:28:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-70699-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took p in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 9/12/2014 5:28:26 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took p in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 9/12/2014 5:03:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-44912-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xABE2) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001458BE2, 0xFFFFF88003FDE448, 0xFFFFF88003FDDCA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took p in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Fri 9/12/2014 9:44:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-49686-01.dmp
This was probably caused by the following module: atikmdag.sys (0xFFFFF880059CDADE) Bugcheck code: 0xD1 (0xD, 0x2, 0x0, 0xFFFFF880059CDADE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.). Google query: ATI Technologies Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

Answer #1
Hi, let me be wild for a sec…
Could you verify that all of your RAM sticks are not causing this issue?
Take one out.. let it run for awhile making sure no blue screens come.. If it does rep it..
(Incase you got only 1.. let me know)
Answer #2
Hi, let me be wild for a sec...
Could you verify that all of your RAM sticks are not causing this issue?
Take one out.. let it run for awhile making sure no blue screens come.. If it does rep it..
(Incase you got only 1.. let me know)

I will attempt to locate and do so and let you know thank you for responding.
Answer #3
Geek Squad are thieving SOBs. Based on your crash dump it’s a problem with your graphics card or graphics card driver, or like not said, with a RAM stick, not with the damn hard drive. Do what suggested, take one RAM stick out one at a time and run the PC for awhile and see if it’s a RAM stick problem. But even before that, uninstall the graphics card driver and reboot the PC, Windows will just pick up and install its generic default driver for the graphics card. If the BSOD still happens after that, then you probably need to rep the graphics card.
Answer #4
I just want to add, , BSOD can be caused by hard drives and I have seen many.
It’s nothing that you can sense it but it ticks. Since he already bought a new hard drive this is not the issue anymore, and once we get it fixed, he can plug his older HD back in.
Also, if you read carefully you will see the following text:
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
But.. yea.. gotta verify some hw before.
Answer #5
The STOP 0xD1 error which appears on your BSOD originates from driver misfunction. (99% of the time from GFX or Network drivers)
A driver has inadvertently or deliberately modified critical kernel code or data.
Best thing to do is completely remove your graphics card drivers, then restart your PC. Like said, Windows will pick your graphics card up and install its generic drivers.
If the BSODs still happen, please remove your Ethernet drivers, then restart your PC as before.
If BSODs still occur, please remove your Wi-Fi drivers, then restart your PC as before.
If the BSODs still keep coming, run Memtest (make a boot disc) and keep it going for 3-4 hours. That should pick up any problems.
Answer #6
I just want to add, , BSOD can be caused by hard drives and I have seen many.
It's nothing that you can sense it but it ticks. Since he already bought a new hard drive this is not the issue anymore, and once we get it fixed, he can plug his older HD back in.
Also, if you read carefully you will see the following text:
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
But.. yea.. gotta verify some hw before.

Yeah but he repd the hard drive so that ain’t the cause.
Answer #7
Yeah, My 2nd line, I’m aware of it. heh

 

| Sitemap |