Random crashes on freshly installed Windows 7

mongo2001

New member
Local time
11:42 AM
Messages
3
In a nutshell, I had a PC with a Windows 7 install for the last two years that had a motherboard go bad. I ended up buying a Tigerdirect combo (hardware specifics below) and just decided to reuse the case with my original install drive. After taking some time to retune itself to new drivers, the computer kept freezing at random times. In some other forums on this site, I thought it driver related (even though I had updated everything including new MB bios). To make things easier, I installed a new 80GB SSD drive and put in a fresh install of Windows 7. Have updated everything to the nines and avoided adding any additional software until I had data and stuff organized from my previous install. However, the randome gremlin seems to have come back at random times.

I've tried setting memory frequency from auto to the speed in the BIOS, but found this thread and have attached the BSOD zip file for some help. Any thoughts on what is the issue? It may be a hardware problem, but I have run memtest on the memory and just can't seem to find the culprit.

Specs:
MB = MSI H61M-P23
Processor = Intel Core i3-2100
Memory = Patriot 4GB DDR3
Windows 7 Professional 64bit

Thanks
 

My Computer My Computer

At a glance

Windows 7 Pro x64
OS
Windows 7 Pro x64
Still ongoing. Latest dmp file. Any thoughts?
 

My Computer My Computer

At a glance

Windows 7 Pro x64
OS
Windows 7 Pro x64
Hello Mongo & welcome! - All apologizes for my delayed answer.

Analyses
Your dump was fairly easy to handle. It's caused by the L1C62x64.sys and the module is named Atheros NIC driver. Not sure, but I think it's coming from the Bullgard Antivirus. Are you using Bullguard? Can you see this driver listed in your Control Panel?

Uninstall
If you're using Bullguard download this tool, and instead of it, use MSSE.

Bugcheck
Code:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff9801b82ae80, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880048819e6, address which referenced memory

Fred.
 

My Computer My Computer

At a glance

Microsoft Windows 7 Ultimate: x64 (SP1)Intel® Core™ i5-2500K ProcessorKingston DDR3 HyperX 1600MHz 8GBASUS GTX 560 TI DirectCU II 900MHz
Computer Manufacturer/Model Number
Brewed
OS
Microsoft Windows 7 Ultimate: x64 (SP1)
CPU
Intel® Core™ i5-2500K Processor
Motherboard
ASUS P8Z68-V PRO
Memory
Kingston DDR3 HyperX 1600MHz 8GB
Graphics Card(s)
ASUS GTX 560 TI DirectCU II 900MHz
Sound Card
Realtek® ALC892 8-Channel High Definition Audio CODEC
Monitor(s) Displays
ACER LCD P246HBD 1920x1080 (24") - Dell 1280x800
Screen Resolution
ACER LCD P246HBD ~ [1920X1080] - DELL ~ [1280x800]
Hard Drives
500 GB WD Caviar SE116 7200rpm SATA2
PSU
Corsair 750W Power Supply
Case
Coolermaster CM Scout
Cooling
Zalman FS-C77 Fatal1ty CPU Cooler
Keyboard
Logitech G15
Mouse
Coolermaster Sentinel Advanced
Internet Speed
[↓ 10 MB/s DL] [↑ 1 MB/s UL]
Other Info
- ROCCAT™ Kave – Solid 5.1 Surround Sound Gaming Headset
- Not overclocking
Hello Fred,

Thanks for reply. Odd thing is that I have the latest driver from MSI and I'm already using MSSE.

I have to say that I have not always gotten BSOD. That was one instance. Usually, the thing with just lock up at random times during random events. Usually when left on for a while. I have disabled the sleep modes, but could that be the culprit?
 

My Computer My Computer

At a glance

Windows 7 Pro x64
OS
Windows 7 Pro x64
Back
Top