Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD, cant pin down, happens even while system idle


27 Dec 2011   #1

WIN 7 x64
 
 
Random BSOD, cant pin down, happens even while system idle

Having random crashes and restarts. Cant find a cause, cant figure out how to read the bsod error report, otherwise I would stop bothering you guys on here. Crashed many times last few days even while idle, and while internet browsing. Deleted the earlier dumps so I can have a smaller managable file., attached it.
Please help the monkey


My System SpecsSystem Spec
.

28 Dec 2011   #2

WIN 7 x64
 
 

look Im on top trying to see.
Just went through and did a bunch of windows rollback updates, lets see how this goes
My System SpecsSystem Spec
30 Dec 2011   #3

WIN 7 x64
 
 

*bump*
Updated everything and still receiving the crash BSOD errors.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000590
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF800034D01C6
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\123011-30482-01.dmp
C:\Users\Realism\AppData\Local\Temp\WER-66955-0.sysdata.xml
My System SpecsSystem Spec
.


01 Jan 2012   #4

WIN 7 x64
 
 

Okay, so anyone going to grace me with at least a go jump off a cliff we dont like you?
My System SpecsSystem Spec
01 Jan 2012   #5

WIN 7 x64
 
 

hal.dll hal.dll+12903 fffff800`039f5000 fffff800`03a3e000 0x00049000 0x4a5bdf08 7/13/2009 5:27:36 PM


ntoskrnl.exe ntoskrnl.exe+186293 fffff800`03419000 fffff800`039f5000 0x005dc000 0x4e02aa44 6/22/2011 6:51:48 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16841 (win7_gdr.110622-1503) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe


Used Bluescreenview to view everthing, and it flagged these two files in pink as something maybe wrong with them. THoughts?
My System SpecsSystem Spec
01 Jan 2012   #6

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by realism51 View Post
Having random crashes and restarts. Cant find a cause, cant figure out how to read the bsod error report, otherwise I would stop bothering you guys on here. Crashed many times last few days even while idle, and while internet browsing. Deleted the earlier dumps so I can have a smaller managable file., attached it.
Please help the monkey

BSV often incorrectly blames the OS. Your single crash was caused by a general hardware fault.

Please read here.



Your .dmp file shows a stop error of 0x124 which is a general hardware error .
Quote:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress
Some generic advice.

If you are overclocking STOP. Return to the default settings at least for now.
If you are running a RAID update its driver.



You can read more on this error and what to try here...
Stop 0x124 - what it means and what to try
My System SpecsSystem Spec
01 Jan 2012   #7

WIN 7 x64
 
 

Thank you for the reply ZigZag, I did come across this a while back in a search and I have tried and come up with the results below

Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.
Nope, overclocking bad. 1 passes

2) Ensure that the machine is adequately cooled. If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.4 fans and core temp sitting at 32c Vid @ 42c

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. It is good practice to run the latest drivers anyway. All drivers updates where done when I put new vid card in and mobo has been checked for bios update,

4) Update the motherboard BIOS according to the manufacturer's instructions. Their website should provide detailed instructions as to the brand and model-specific procedure. Double checked this one just to be sure

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated. So this must not apply

6) Attempt to (stress) test those hardware components which can be put through their paces artificially. The most obvious examples are the RAM and HDD(s). For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing. For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors". Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.stress tested, mem checked, disk checked till my puter begged for a break, all pass.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc. Should that fail to mitigate the 0x124 problem, jump to the next steps. Otherwise, if you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes. Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:
I fear reinstalling

8) Clean and carefully remove any dust from the inside of the machine. Reseat all connectors and memory modules. Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.all dust bunnies have been scooped up and bopped on the head, (if they had existed, you could eat off the inside of my computer, but I wouldn't recommend it

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps. Yup, spent a whole week swapping and checking, doesnt seem to be a removable component

And thats what Ive got done so far for checking problems, I fear reinstalling because of the amount of time to move files over and go through the whole pain of reinstalling everything, with most likely same result. Its apparently been an unmitigated problem for the life of windows 7 with me, Ive had other posts on here as well
My System SpecsSystem Spec
01 Jan 2012   #8

Win 8 Release candidate 8400
 
 

Nice post

Since you have done almost anything hardware related I would ask you to run driver verifer to see if it can catch the driver while it is mis-behaving.



Quote:
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Quote:


In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .


Then, here's the procedure:

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything
EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers
NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and
wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.

If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Also feel free to Pm me if needed
My System SpecsSystem Spec
01 Jan 2012   #9

WIN 7 x64
 
 

Will give this a try. Now the arduous task of backing everything up. Oh 2TB hard drive, you vex me so. WIll let you know how it goes in a day or two after doing everything you said
My System SpecsSystem Spec
01 Jan 2012   #10

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by realism51 View Post
Will give this a try. Now the arduous task of backing everything up. Oh 2TB hard drive, you vex me so. WIll let you know how it goes in a day or two after doing everything you said
Let me know if you need help.


ken

btw loved the "vex" been there myself grin
My System SpecsSystem Spec
Reply

 Random BSOD, cant pin down, happens even while system idle




Thread Tools



Similar help and support threads for2: Random BSOD, cant pin down, happens even while system idle
Thread Forum
Solved Random idle BSOD BSOD Help and Support
Random BSOD while idle. BSOD Help and Support
Random reboots when system is idle BSOD Help and Support
Random BSOD, even while idle BSOD Help and Support
BSOD - Random Crashes while idle or in use. BSOD Help and Support
BSOD on new PC very random on idle... BSOD Help and Support
Random BSODs when system is Idle. BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 06:27 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33